search

nordicopen / easee_hass

Custom component for Easee EV charger integration with Home Assistant
207 stars 34 forks source link

Missing energy bar randomly #139

Open rhoddan opened 2 years ago

rhoddan commented 2 years ago

Randomly (not too often) there are missing bars. Not sure if this is related to the Easee integration or HA core. See attached Screenshot 2021-09-10 095809

rhoddan commented 2 years ago

Can it be related to https://github.com/fondberg/easee_hass/issues/140 ?

olalid commented 2 years ago

A guess is that there was an interrupt in the communication with the equalizer for some reason and the energy used during that hour was accumulated on the following hour instead because the meter did not update. Hard to tell what the issue might have been, in my setup there are for sure smaller interrupts now and then, not often, but it does happen. Can you see the history of the equalizer online sensor during this same hour?

rhoddan commented 2 years ago 
    Not sure. I have 2 different HA connected to same equalizer. It was randomly missed between them
    Hämta Outlook för iOS

 Från: Ola Lidholm @.***>Skickat: måndag, september 27, 2021 4:54 emTill: fondberg/easee_hassKopia: rhoddan; AuthorÄmne: Re: [fondberg/easee_hass] Missing energy bar randomly (#139)  A guess is that there was an interrupt in the communication with the equalizer for some reason and the energy used during that hour was accumulated on the following hour instead because the meter did not update. Hard to tell what the issue might have been, in my setup there are for sure smaller interrupts now and then, not often, but it does happen. Can you see the history of the equalizer online sensor during this same hour?

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.

olalid commented 2 years ago

If the problem is on the server side I think the timing of when data is missing or when a client disconnects can differ between the clients. But, anyway, there is a lot of speculation here. If you see this happening again it would be good to see how the sensor behaved during the same time period.