You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can see below, I have the consumption of my wiser heater energy sensors which randomly return to 0. (Here the consumption of my bathroom heater)
And the problem is that It detects a new cycle for my energy dashboard :
It can be seen below that a behavior has changed (around April. While consumption was continuously increasing before April) :
Many Thanks for your help
The text was updated successfully, but these errors were encountered:
I think this was caused by a change in HA. I am reworking some of the inegration to hopefullyprevent this. I think it happens when the update from the hub fails due to hub dropping off wifi.
There should be an updated version today or tomorrow to see if this resolves.
Hi @msp1974
Thanks for your work
It seems to be ok now with the v 3.4.7. Energy sensors are not set to 0 anymore, even if there is an hub unavailability :
👍
tipp for those of you who use nodered:
i fetch the sensor from wiser there and filter it for unknown / 0 etc by using a switch node.
then the value is being sent to HA as a new sensor using a "sensor" node, which can be allocated to a virtual device nodered creates.
Hi @msp1974,
For an easier following, I document here the problem I have with my energy sensors which return to 0 randomly and broke my energy dashboard filtered by device (Cf discussion in the blog here : https://community.home-assistant.io/t/drayton-wiser-home-assistant-integration/80965/3625)
As you can see below, I have the consumption of my wiser heater energy sensors which randomly return to 0. (Here the consumption of my bathroom heater)
And the problem is that It detects a new cycle for my energy dashboard :
It can be seen below that a behavior has changed (around April. While consumption was continuously increasing before April) :
Many Thanks for your help
The text was updated successfully, but these errors were encountered: