core: Data cannot be updated continuously

Perhaps it is scheduled for 1rst release of the year (beginning of february)

Hi @jugla, I tried also the fork, I confirm what @cmaile said, keyatome looks fine for me.

Hello, If someone can test pull request #60955 to see how much is the benefit respect to this issue #58473. Thanks in advance

looks good. Data has been stored for over 24 hours.

I have same issue since couple of week. Tried to downgrade but it doesn’t help not sure there is a relation between both. remove the the database go from scratch but nothing help

The issue seems to be happening after some changes Total Energies/Atome made on their side. So downgrading HA or flushing your DB wont change anything. Only a reboot works for me and only for 2 hours after each reboot and then it stops updating… There are 2 other opened issues for this same matter too 😦 Hopefully atome integration in HA can be fixed to match the changes Total made… @BaQs did you have the time to look into it?

thanks @jugla i replaced atome by keyatome in my config and it works fine for a few days now. Since it works fine I did not take the risk to remove the manual config and do it over the UI because i feared if it may create a new set of sensors or if I would loose my current sensors and their history by doing so

Hello, If someone can test pull request #60955 to see how much is the benefit respect to this issue #58473. Thanks in advance

Yeah, how to test, just replace pyatom with pykeyatome ? 😃

You can either look at the commits on the PR or clone the branch of jugla.

Manually you can download the zio and replace the components/atome

Hello, I’m writting pykeyatome to avoid exception. https://github.com/home-assistant/core/pull/60955

same problem for me I can’t logged here https://esoftlink.esoftthings.com/login

refer https://github.com/home-assistant/core/issues/58253#issuecomment-952648024

Hello, It has taken some times to make environnement of pykeyatome to work. The fork of keyatome has gone quiet fast. So unfortunately, this PR is no more relevant. All patches and improvments are available within keyatome (cf. Github or HACS).

I will see how to integrate keyatome’s evolution in home assistant. Not yet plan . Sorry

Thank you very much for your contribution, looking forward to the new version! 😃

So if install the custom keyatome will it keep the history of the sensors since they will keep same name?

Yes

Before installing the custom keyatome do I need to remove the configuration of the current one? Or I just keep the config and once the custom repo is installed it will take over the configuration?

It’s wise to not have both integration working at same time. In your current configuration, replace atome by keyatome

##configuration.yaml example
sensor:
  - platform: atome
    username: YOUR_ATOME_USERNAME
    password: YOUR_ATOME_PASSWORD

##configuration.yaml example
sensor:
  - platform: keyatome
    username: YOUR_ATOME_USERNAME
    password: YOUR_ATOME_PASSWORD

Thanks for your work on this

Thanks a lot

@jugla you are now one of the owner of the official integration repo no ? Is your fork merged into the main ? Is a PR has been made to HA from this merge ?

I would like also to say thank you for fixing this !

I have same issue since couple of week. Tried to downgrade but it doesn’t help not sure there is a relation between both. remove the the database go from scratch but nothing help

Indeed, I tried to log in to this address but failed. But I use the mobile application * (atome), he can log in and get data