Skip to content

provide fix for utc offset in energy consumption - #639

Closed
s5zone wants to merge 1 commit into
nordicopen:masterfrom
s5zone:master
Closed

provide fix for utc offset in energy consumption#639
s5zone wants to merge 1 commit into
nordicopen:masterfrom
s5zone:master

Conversation

@s5zone

@s5zone s5zone commented Sep 12, 2025

Copy link
Copy Markdown

The energy consumption is being recorded with an 1-hour offset for me, similar to the issue related here:
#151

this should fix it.

@olalid

olalid commented Sep 12, 2025

Copy link
Copy Markdown
Collaborator

Well, as i have expressed many times in the discussion here the issue you are referring to is not a time zone problem...

It is HAs internal date and time at the time when data is updated that matters, the integration does not provide a timestamp to HA in any shape or form when a value is updated. HA just does not provide a way to add a timestamp together with a data update that would tell HA that the change happened at a specific time, you can only insert data at the current point in time.
And since we can not control when data is updated there is no way to fix this. (Only Easee and the energy meter controls this). There are also workarounds mentioned in the wiki.

Anyway, there could of course be some bug in time zone handling, but the 1 hour shift in energy meter would not be one of the symptoms of that.
Things that could be affected would be related to data which includes actual time and date, like schedules. But given that what you point to that is unrelated to this, it becomes difficult to actually know what problem you are trying to solve? Have you seen a date being displayed incorrectly somewhere in some sensor/attribute?

@s5zone s5zone closed this by deleting the head repository Jan 28, 2026
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

Successfully merging this pull request may close these issues.

2 participants