-
-
Notifications
You must be signed in to change notification settings - Fork 164
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
Daily Energy steps up massively every time consumption resumes from 0 #598
Comments
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
This issue continues, and renders the Glow useless for daily power consumption, and only useful for instantaneous power monitoring. This issue shouldn't be closed off, even if there is no solution, because people need to be able to find that it as a serious limitation of the platform. |
I think the best solution at this point is to put a note somewhere in the documentation that it is best not to use glow if you also have solar panels. What you also can try is using a different method: ./Klaas |
Happy to try this out - is there a way I can make this change onboard the Glow itself, rather than making a Template sensor in HA - would be good to still get the advantage of the 'always recording' glow, even during a system reboot, etc. |
After having stabilised the instantaneous consumption data errors I was getting by adding the
internal filter:
as well as ensuring no feedback from flashing LEDs, this has revealed a different issue, where the Daily Energy increases by huge numbers every time the unit starts to detect consumption again, after a period of 0 flashes due to adequate solar generation:As you can see, this not the result of an incorrect reading of the Consumption - only momentary modest pulling from the grid is accompanied by massive instantaneous jumps in the daily total.
Has anyone experienced this? My only thought it is somehow connected to the 4-5 minute lag the unit has to changing power consumption to 0 once the flashing has stopped. And somehow when it kicks back in, it's assuming a value across the time that should be 0?
The text was updated successfully, but these errors were encountered: