-
Notifications
You must be signed in to change notification settings - Fork 15
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
reporting 0 values #91
Comments
This is actually a bug in the Comfoconnect LAN (or even the ventilation unit). During connection, it seems to emit 0 values while there should be a real value. 0 values can't simply be avoided, since this could happen with temperature sensors, and those could very well report 0 degreees celcius. Since I noticed these issues only when reconnecting (due to restarting home assistant, or due to restarting the bridge), I've worked around this in the aiocomfoconnect library to hold initial sensor updates for a few seconds during startup. You could look at using helper template sensors to filter out 0 values if needed, although I don't notice this issue on my setup. When keeping track of the energy usage, i recommend to look at #88. |
Couldn't it be filtered by only allowing 0 values only if multiple zero values are consecutively reported? |
I don't remember the details, but I think sensors don't update when the value doesn't change, so there won't be 2nd 0-value. This would cause all 0 values to be filtered out, what could be problematic for some sensors (like the 0-10V sensors). |
But feel free to play with the code, and check if the behaviour is different and another way to filter only the incorrect 0 values can be used. |
It seems that sometimes all variables are reported as 0 for a very short time. My guess is that there was some communication problem. Can it be avoided that those values are added to the history.
At least the total energy usage doesn't properly handle that. If you add a 0 value, it assumes it reseted the value, and if you than get a non 0 value again it will than think you used all the energy it has used ever in that day.
The total energy usage also stays 0 until an extra kWh has been used. That is it was at 100, was than 0 for about 14 hours and than changed to 111, resulting in claiming having used 111 kWh that day while it uses less than 1 a day.
The text was updated successfully, but these errors were encountered: