-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1min sensors not updating (but not all?) #219
Comments
There are a few issues tracking this. The live data from the API is unstable, which is what the integration pulls from. The history in the Emporia app is compiled from past data when requested and has the benefit of being able to work with delayed data. The only thing that's a fair comparison to make between the two is the main page in the app, set to the 1 minute level, and the "now" option. If the data is messed up when viewing the app with those settings, the integration will be too. Unfortunately that data is often bad in the app. |
I can confirm that the 1 min view on the web and android app versions of Emporia are both showing power data whereas the 1min on the HA has not updated in 5 hours. |
All of the 1M sensors become unavailable after some time for me.. and a reload of the plugin seems to resolve it. |
Same here. Reload fixes it. Reboot makes it fail again. So a workaround is to remember to reload after rebooting, I have not seen if reboot is the only trigger. The message in Logfile is: Strangely, one sensor is not reported in the logfile but, like the others in the list of entities it is marked as unavailable and does not update. The Day and Month sensors are all OK. Mine was only set up 2 days ago I can only speak for the current 2023.09.2 version of HA. |
What I see that a reload does not necessarily fix ALL the sensors.
1m sensors for the major devices (the hubs) are always reliable but the
circuit sensors are intermittent.
I usually have to redownload to try to get it back up, but even then, it's
not reliable for long.
I have two emporias - one on the main panel and a second installed on a sub
panel. (It's configure as such in the tool as well)
…On Sat, Sep 23, 2023, 08:00 dabbler68 ***@***.***> wrote:
Same here. Reload fixes it. Reboot makes it fail again. So a workaround is
to remember to reload after rebooting, I have not seen if reboot is the
only trigger. Mine was only set up 2 days ago I can only speak for the
current 2023.09.2 version of HA.
—
Reply to this email directly, view it on GitHub
<#219 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3ZC4G4LLPRG6P2BS63WCFTX33FNZANCNFSM6AAAAAA3E3CQYU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Today I had a look at the logfile and there was a difference. I am guessing it may be related to Daylight Savings time in some country and was fixed by Emporia. (DST has not started here yet ... Australia). As for all sensors or not I am seeing some consistency, I have 8 sensors. Sensor 6 has never reported the "Unable ..." message while sensors 4 and 5 always report twice in the same group of warnings. All sensors are reporting their energy usage. When the integration is reloaded, the 1 day sensors also report the "Unable .. " message. But for these sensors 4 and 5 do not duplicate, Maybe as there is somce consistency in these messages there is something in these notes that will be meaningful when looking for a solution. |
I'm losing all of my 1Min sensors after a reboot. And occasionally just randomly when it's been running fine for a while. |
It appears that 1min devices are not being updated consistently. Some of them look like they track well, others only update infrequently leading to very sporadic information.
First, a picture of what HA is seeing:
What Emporia is seeing:
Reloading the integration does not solve the issue.
The text was updated successfully, but these errors were encountered: