Time is offset by 1 hour

[theilgaard]

I believe reported charge in the time bucket is offset by 1 hour.

I recently installed a Pow K from amsleser.no to monitor my power usage, and can see the individual tracking from the Zaptec charger is arriving 1 hour later than the pulse reading from the amsleser Pow K.

Is there a way to offset this?

[sveinse]

Unfortunately there is no way in HA to register data for the past, so a measurement happens when it happen. When Zaptec reports the hourly usage, it updates it too late and thus the data gets offset with one hour.

Its a common issue if you google it. https://community.home-assistant.io/t/energy-dashboard-is-shifted-one-hour/685596

[theilgaard]

Ouch, so data is stored at the time of receiving, with no separate column/field in the messages for datetime? That seems like a massive blunder when working with time sensitive data.

[sveinse]

It is, but it is a design decision made by HA. I recommend pursuing HA channels to get it changed.

In control engineering it is very common that when a data sample is made it takes some time before the sample is available and communicated, so I do agree that this is a weakness.

[falver]

This is an issue of the Zaptec cloud platform combined with the lacking ability of HA to backdate data. The Zaptec platform is only updating a few values on a realtime basis to reduce the necessary processing power. All other values are "slow changing" and it might take minutes or up to an hour to process the data from the charger.

The solution (for now) is to use the "current charging session" entity. This sensor is updated realtime instead of on an hourly basis and in this way it maps the consumption to the correct time.

It does reset to 0 after every charging session but the energy dashboard can handle this correctly.

[theilgaard]

Thanks @falver, that did the trick!

[sveinse]

There haven't been any updates to this issue, so I assume the issue is fixed. Closing the issue. If this is not the case, please reopen the issue.