Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Data @ 11pm-12am is lost every night
See original GitHub issueEach night at the end of the day, the accumulating value of kWh consumed is reset to zero and begins increasing again for the next day from after midnight. This value (for electricity) is sensor.electric_consumption_today
However, if you use a HistoryGraph (see attached image) to graph sensor.electric_consumption_today it’s apparent that there is no data from 11pm until 12.30am every night (the consumption data is zero for at least 1.5hrs). This means that there is at least 1.5hrs of consumption not being accounted for every night.
Expected behaviour would be for consumption data to continue until 12.00am when it would reset to 0kWh and begin accumulating again from 12.01am.
HomeAssistant v2021.10.6 Hildebrand Glow (DCC) integration v0.3.3
Issue Analytics
- State:
- Created 2 years ago
- Comments:16 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’ve clarified that the last 30 minutes of the day will be lost on the daily sensors, the bug in the calculation of DST has been fixed and cumulative sensors have been added. Please reopen if you are still losing more than 30 minutes of data!
I now have the cumulative (Usage since Jan 1 in current year) sensors implemented in my test system. Need to let it run for a few days to make sure the Energy integration works OK with it. If all goes well, I’ll make a PR.