Closed kevindbeard closed 2 years ago
I suggest this is casued by different sampling methods.
The Bright app is likely (a guess on my part) to show the a measurement from the meter by asing for a reading of a specific time slot e.g., 07:00 to 08:00.
Whereas the way HA and thus this integration work is by polling and taking the current meter reading. It then calcuates usage based on the difference between now and the previous reading.. Thus where HA shows 07:00 to 08:00, it could actually mean 07:10 to 08:10.
This is then further confused by the fact updates from DCC come every 30 minutes, depending on how this aligns with the hour, the results will be different.
So not really a "bug", but a "feature" of the way it all works.
Ahh that makes sense thank you :-)
And thanks for the integration, it's much better than calling the Octopus API directly from HA.
Describe the bug I've been running the integration for about a week and I've noticed that the numbers displayed in the energy dashboard never quite match what's shown in the Bright app
To Reproduce Steps to reproduce the behaviour: Add "Energy Consumption (year) to the HA energy dashboard and let it run for a few days Compare the chart with what is shown in the Bright app
Expected behaviour Beginning and end of day will be wrong by half an hour, but other timeslots during the day should match
Screenshots
Version What version of the integration and what version of Home Assistant are you running? 0.5.2
Debug log Enable debug logging by following the instructions here
Additional context Add any other context about the problem here.