core: Atome Linky missing sensors and login issues
The problem
I have many errors.
The first one is a “wrong password or login” (nothing changed and I still use these to login in the official website). It’s probably caused by the second error.
The second error in the logs is this:
Logger: homeassistant.components.atome.sensor
Source: components/atome/sensor.py:275
Integration: atome ([documentation](https://www.home-assistant.io/integrations/atome), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+atome%22))
First occurred: 21:53:29 (4 occurrences)
Last logged: 21:53:58
day : Missing last value in values: {'isConnected': True, 'time': '2022-09-27T21:53:28+02:00', 'total': 0, 'logTargetStd': 0.0, 'goal': 100, 'startPeriod': '2022-09-27T00:00:00+02:00', 'endPeriod': '2022-09-27T21:53:28+02:00', 'pricingChange': 0, 'filteredPower': 0.0, 'impactCo2': 0, 'impactVehicleType': 'BIKE', 'impactVehicleKm': 0}
week : Missing last value in values: {'isConnected': True, 'time': '2022-09-27T21:53:34+02:00', 'total': 0, 'logTargetStd': 0.0, 'goal': 100, 'startPeriod': '2022-09-26T00:00:00+02:00', 'endPeriod': '2022-09-27T21:53:34+02:00', 'pricingChange': 0, 'filteredPower': 0.0, 'impactCo2': 0, 'impactVehicleType': 'BIKE', 'impactVehicleKm': 0}
month : Missing last value in values: {'isConnected': True, 'time': '2022-09-27T21:53:38+02:00', 'total': 0, 'logTargetStd': 0.0, 'goal': 100, 'startPeriod': '2022-09-01T00:00:00+02:00', 'endPeriod': '2022-09-27T21:53:38+02:00', 'pricingChange': 0, 'filteredPower': 0.0, 'impactCo2': 0, 'impactVehicleType': 'BIKE', 'impactVehicleKm': 0}
year : Missing last value in values: {'isConnected': True, 'time': '2022-09-27T21:53:43+02:00', 'total': 0, 'logTargetStd': 0.0, 'goal': 100, 'startPeriod': '2022-01-01T00:00:00+01:00', 'endPeriod': '2022-09-27T21:53:43+02:00', 'pricingChange': 0, 'filteredPower': 0.0, 'impactCo2': 594298, 'impactVehicleType': 'PLANE', 'impactVehicleKm': 37}
@BaQs I saw that you updated the pyAtome lib. Is updating the dependencie of this integration to 0.1.2 would fix the issue ?
What version of Home Assistant Core has the issue?
2022.9.7
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
atome
Link to integration documentation on our website
https://www.home-assistant.io/integrations/atome
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 22 (19 by maintainers)
@coolkeve thanks ! The “official” integration was still maintained 2 months ago though: https://github.com/home-assistant/core/pull/76986
@epenet do you have these issues too ?
@BaQs already said in previous tickets about this integration that someone else should be labeled as codeowner for this atome integration (if I remember good). I think that all people tagged here think that this integration is really important. Energy tracking is a core feature.
Should the keyatome by @jugla become the official integration ?
Also, if @renaiku wants to get involved I suggest that you add both as code-owners on the HA integration…
I had a very quick scan of your PR, and I think it is too big. You should try to make it “as small as possible”:
@jugla np ! Don’t hesitate to tag me on further issues or pull requests if you need a code review or something.
You opened a pr ? I suggest you go all out and make a pr on the atome existing integration and overwrite everything. We can also discuss about it on discord in French or English on how to handle this. I can test almost everything and I can setup a home assistant dev environment if needed.
Thanks for the enlightenment!
Keep this ticket opened, I’ll wait for @jugla 's answer, or maybe work myself on it then 😃
@renaiku I found this integration more recent [(https://github.com/jugla/keyatome)]