Skip to content

Hourly consumption is registered 1 hour late in Home Assistant #86

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

Open
mloraas opened this issue Mar 20, 2025 · 0 comments
Open

Hourly consumption is registered 1 hour late in Home Assistant #86

mloraas opened this issue Mar 20, 2025 · 0 comments

Comments

@mloraas
Copy link

mloraas commented Mar 20, 2025

Due to the fact that current hours consumption is sent 10 seconds past the next hour, when this is registered in Home Assistant, it gets registered as consumption in the same hour as the value is received. This leads to a one hour delay of the consumption values.

This is problematic when calculating hourly tariffs, and makes the energy dashboard fail when comparing consumption with "individual devices".

It would be very nice if it is possible to modify the timestamps of the values that is registered with Home Assistant, so that the value is interpreted as belonging to the previous hour.

I have done some googleing, and came accross this thread:
https://community.home-assistant.io/t/batch-receive-time-series-data/171915/12

I don't know if it relevant or possible for this problem, though.

This seems to be an issue for a lot of people:

https://community.home-assistant.io/t/energy-dashboard-is-shifted-one-hour/685596

https://community.home-assistant.io/t/energy-usage-is-delayed-or-shifted-in-time-in-the-graphs/362875

home-assistant/core#84996

https://www.hjemmeautomasjon.no/forums/topic/12082-energi-dashboard-i-home-assistant/

A solution that is mentioned, is using an integral sensor with the power report from the meter. This surely works, but is not as accurate and more susceptible to downtime/disruptions.

The accumulated energy reading from the meter itself is considered the correct value, and it would be nice to have this value correctly interpreted.

Best regards,
-mLoraas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant