Timestamp off by 170 seconds

12:24:49 vs 10:21:54 (+2)

12:24:49 is the time the screenshot was taken according to my two other PC's synced by NTP.

But don't waste your time. If it occurs just here and is not a general issue i can easily live with it. It looked weird to me (and still does) so i wanted to report.

Proxmox, right?

What's the proxmox server time vs the HA time?



that 1/2 second is due to my slow fingers :wink:

Hmm, but that 1782902732 seem to be correct now matching 12:45:31 ?????

So is maybe something wrong with my Proxmox installation ?

The timestamp you show is also 12:45 :wink:

YES i have just noticed. Seems it is NO LONGER shifted but WHY ?

Was opening Proxmox making the difference ?

THANK YOU SO MUCH for helping. My BMS is now 170 seconds ahead :slight_smile: and i can drop the workaround !

No clue. Maybe the HA VM is frozen for 170 sec at some point?
HA itself relies on the VM clock, I assume, so if that one gets desynchonized at some point...

Yes but how could/did the time displayed not rely on the same tic-value ? Seems there are two of them :wink: One used for time-card, another one ....
Now they are corresponding again. Still a small miracle :wink:

IDK what this "BMS" is, but hardcoding the diff is probably just a workaround

Which time card are you using, exactly?

BMS is my ESP32 home battery controller. Can not use sntp or ntp client there as network is blocking then. So i rather subscribe an MQTT topic to sync ....

Oh just the "standard" digital clock card.

I think for a developer it must a nice challenge to find out HOW utcraw and the display of that card can differ (by 170 seconds or other) :slight_smile:

rawtics are probably running independent (and missed some tics over the time) and the clock card and internal timebase is accessing the "root" tics. just my assumption !

ESPHome? You know you can sync time via HA API, do you?

AFAICT, that one takes the time from the browser, so unrelated to HA date/time.