ha-hildebrandglow-dcc: Data @ 11pm-12am is lost every night
Each 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
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 16 (11 by maintainers)
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.
We are agreeing. The data is all there in the Glow API / DCC. It just how you get at it and manage the 30 minute delay. The Home Assistant model assumes real time data, not historic (30 minute old) data. I have a proposed solution in my summary post above, let’s wait and see if that works.
Let’s summarise… You are seeing a gap of 1.5 hours. I believe this is caused by two issues.
I’ll work on point 2. When this is added the documentation can be updated.
I think this may be related to a time zone calculation error I have spotted. I am about to make a PR this might fix it.