ha-emporia-vue icon indicating copy to clipboard operation
ha-emporia-vue copied to clipboard

Minute entity for all devices keep dropping

Open rhaymg opened this issue 2 years ago • 15 comments

Since first install the integration keeps dropping the minute entity. The only way to restore them is to reload the integration but they will eventually drop again. This is problematic as I have notifications that rely on the minute entity to function properly.

rhaymg avatar Sep 05 '21 01:09 rhaymg

Related/duplicate of #33 and #68. If you can get me logs so I can see what error if causing it I can hopefully do something about it but I'm unable to reproduce it locally. My sensors stay up even through intermittent API failures.

magico13 avatar Sep 05 '21 01:09 magico13

Logger: homeassistant.components.sensor.recorder Source: components/sensor/recorder.py:258 Integration: Sensor (documentation, issues) First occurred: 1:04:20 AM (6 occurrences) Last logged: 5:12:00 PM

Entity sensor.power_balance_balance_1d from integration emporia_vue has state class total_increasing, but its state is not strictly increasing. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+recorder%22 Entity sensor.power_maple_123_1d from integration emporia_vue has state class total_increasing, but its state is not strictly increasing. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+recorder%22 Entity sensor.power_washer_6_1d from integration emporia_vue has state class total_increasing, but its state is not strictly increasing. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+recorder%22 Entity sensor.power_fridge_5_1d from integration emporia_vue has state class total_increasing, but its state is not strictly increasing. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+recorder%22 Entity sensor.power_heat_pump_9_1d from integration emporia_vue has state class total_increasing, but its state is not strictly increasing. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+recorder%22

2021-09-06 01:04:20 WARNING (Recorder) [homeassistant.components.sensor.recorder] Entity sensor.power_maple_123_1min from integration emporia_vue has state class total_increasing, but its state is not strictly increasing. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+recorder%22

rhaymg avatar Sep 06 '21 22:09 rhaymg

Those shouldn't cause loss of the sensor but I was afraid they might happen. The 1min sensors shouldn't be that class, definitely need to fix that, since those can and do fluctuate up and down but the 1D sensors should ideally only decrease when they reset at midnight.

magico13 avatar Sep 07 '21 03:09 magico13

experiencing same issue here. seems to have started after version 7.0. is that when the total_increasing was added? since only day and mon are recognized by energy monitoring, perhaps min can return to the old state while the other 2 remain on increasing.

-edit- Just had a look at the state attributes for my energy monitoring plugs from different vendors which dont have this issue the WK energy sensors have state class of total_increasing however the W Power sensors have no state class at all

so it should be safe to remove the state class from only the W power sensors (min) since they are not used by the energy monitoring

charettepa avatar Sep 09 '21 00:09 charettepa

I've had success with a custom override of the state class for the minute sensor (in Watts). I've changed it to "measurement" in the customizations section of configurations. Now they also show up again properly in my statistics graph cards.

wvriem avatar Sep 10 '21 15:09 wvriem

changing to measurement does resolve the issue, however as soon as you perform a HA update the values revert to total_increasing

hopefully this change can be made to the integration

charettepa avatar Sep 11 '21 23:09 charettepa

Also having the issue. Need to manually reload the integration at midnight. I see you seem to have set them to measurement in e3fc9df6d3993765e576b9bddc30c2f9213d3085 Can we get a release on this? Willing to test with a reinstall on another branch.

Gunsmithy avatar Sep 23 '21 04:09 Gunsmithy

You can reinstall from master as the version in HACS and it should pull that change in.

magico13 avatar Sep 23 '21 15:09 magico13

while this change is working, any time there is a HA update and restart, the minute entities are still measurement but are unavailable. doing nothing more than an additional restart after it has settled in does correct the issue and the minute entities are available again. could this have something to do with timing on when the integration tries to start?

charettepa avatar Sep 26 '21 17:09 charettepa

I just installed HACS and this tonight. I have no minute sensors except for the main 1,2,3 unit.

***Update: I had version 7 installed, I reinstalled the master now.

mciaio avatar Sep 29 '21 00:09 mciaio

Reinstalled with master as suggested above. Was fine for days until today when Home Assistant froze and I rebooted my Pi. When it came back up, all my minute sensors were Unavailable. Had to reload the integration to fix it. Here is what was in my logs.

Logger: homeassistant.components.sensor.recorder
Source: components/sensor/recorder.py:325
Integration: Sensor (documentation, issues)
First occurred: 21:00:56 (3 occurrences)
Last logged: 21:00:56

Entity sensor.left_vue_balance_1mon from integration emporia_vue has state class total_increasing, but its state is negative. Please report it to the custom component author.
Entity sensor.left_vue_balance_1d from integration emporia_vue has state class total_increasing, but its state is negative. Please report it to the custom component author.
Entity sensor.left_vue_balance_1min has state class total_increasing, but its state is negative. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue



Logger: homeassistant.components.sensor.recorder
Source: components/sensor/recorder.py:309
Integration: Sensor (documentation, issues)
First occurred: 21:05:10 (2 occurrences)
Last logged: 21:05:10

Entity sensor.left_vue_123_1min from integration emporia_vue has state class total_increasing, but its state is not strictly increasing. Please report it to the custom component author.
Entity sensor.right_vue_123_1min from integration emporia_vue has state class total_increasing, but its state is not strictly increasing. Please report it to the custom component author.

Gunsmithy avatar Oct 28 '21 01:10 Gunsmithy

I've noticed after every single reboot of home assistant, the minute entities are "unavailable". Once I reload the integration, they appear again and work as expected. It has become part of the routine when rebooting to also reload the integration once the gui is available. I wonder if a delayed start of the integration may help? If thats even possible.

zztopgtb avatar Nov 16 '21 23:11 zztopgtb

+1 have the same here. Various minute sensors are showing as 'Unavailable'. I do not see errors in the logs. Attached a portion of the screen (note 2 hour update is after reboot). Note I am on same HA (2021.9.2) and EmporiaVue integration (0.7.0) for a while without any issues. No changes were made...

Ugh -- Ignore - Updated to 0.7.2 and issue went away. Don't get why it just stopped working, but happy update fixed it.

image

happydutch avatar Dec 08 '21 16:12 happydutch

+1 have the same here. Various minute sensors are showing as 'Unavailable'. I do not see errors in the logs. Attached a portion of the screen (note 2 hour update is after reboot). Note I am on same HA (2021.9.2) and EmporiaVue integration (0.7.0) for a while without any issues. No changes were made...

Ugh -- Ignore - Updated to 0.7.2 and issue went away. Don't get why it just stopped working, but happy update fixed it.

image

This is the same issue I reported in September Reinstalling is not what fixed it This issue happens after every ha update Simply rebooting fixes the issue I think it has to do with the order things load in Might just need a delayed load

charettepa avatar Dec 08 '21 18:12 charettepa

Thanks. Added an automation that reloads integration in case it happens again

happydutch avatar Dec 08 '21 20:12 happydutch