Time-based automations start late | Home Assistant | Page 1

somber kraken Jan 9, 2025, 4:26 PM

#

In late December I updated Home Assistant Core to 24.12.5, at which point most time-based automations on my system began to trigger ~53 minutes late. I say most automations, as I have one that runs every ten minutes, and it runs only 2 minutes late.

This past Tuesday I updated Core again to 25.1.1, and now automations run only ~35 minutes late - which is an improvement!

My HA runs in a VM, but as far as I can tell, the time in the VM is correct: issuing "date" within the Terminal cli returns the correct date&time, matching that of the host server.

Anyone experiencing this? I've found similar posts in the Community Forum, but none are recent. Any recommendations?

lapis forge Jan 9, 2025, 5:10 PM

#

What VM platform?

#

I've seen this kind of problem a lot over the years when the VM software forces the guest time to change

#

Best practice is to disable that feature and let the guest handle time sync

somber kraken Jan 9, 2025, 5:18 PM

#

VirtualBox.
So the HA Terminal cli's time might not agree with the HA core time? If not, how can I check the HA core time?

lapis forge Jan 9, 2025, 5:19 PM

#

Nah

#

The problem is that the guest thinks it's time X, and then the host comes along and changes that time

#

That fucks things over, big time, it's far from just HA that suffers when that happens

#

https://forums.virtualbox.org/viewtopic.php?t=97014 amongst other guides

#Time-based automations start late