Time triggers running randomly

Configuration
1

Running HA OS 2021.6.6 and since a couple of updates my automations no longer run at the correct time.
I have the following automation that I want to run at 22:00 to turn on my outdoor lights:

alias: Solnedgång
description: ''
trigger:
  - platform: time
    at: '22:00:00'
condition: []
action:
  - scene: scene.utebel_on
mode: single

Lights won’t turn on. Checking the history I see that the automation was invoked 00:32 (wrongly reported as 24:32) more than three hours later:

2021-07-05_09-31-26
2021-07-05_09-31-262004×900 90.3 KB

2021-07-05_09-33-13
2021-07-05_09-33-131134×814 67.3 KB

Why? What I am missing?
I have checked timezone and date at the command prompt and it reports the correct time and CEST timezone.

2

What does this return in the developer tools template editor:

{{ utcnow() }}
{{ now() }}
{{ utcnow().astimezone() }}
{{ now().astimezone() }}
{{ utcnow().tzinfo }}
{{ now().tzinfo }}
{{ now().astimezone().tzinfo }}

And how does the second one, {{ now() }} compare to your current time?

3 
2021-07-05 07:54:42.352888+00:00
2021-07-05 09:54:42.352899+02:00
2021-07-05 09:54:42.352907+02:00
2021-07-05 09:54:42.352929+02:00
UTC
Europe/Stockholm
CEST

All looks good to me.

4

did you ever find a solution? I have the same problem, my automation ran 22min 24sec late. All my time and date configurations appear okay to me.

Here is the trace timeline (was supposed to trigger at 00:35:00)

Screen Shot 2021-08-07 at 1.44.51 PM
Screen Shot 2021-08-07 at 1.44.51 PM1418×800 74.3 KB

I also found a discrepancy between the system UTC time and the actual time when I checked ha host info

b17ab47fd068aa3f5466aa654fb6eaefdf74f94e
b17ab47fd068aa3f5466aa654fb6eaefdf74f94e1584×1172 161 KB

5

Don’t know if you are running HAOS on vSphere ESX 7.0, but I have managed to get it working by the following steps:

  1. Updated the VM to use VM version 18 compatibility (when importing the OVA, version was set to 13)
  2. Disabled synchronize time periodically and relying on HAOS own ntp-client to keep the clock in sync
  3. Re-configured my automations to only have a single sunset/sunrise automation kicking off multiple scripts (previously I had multiple triggers for sunset/sunrise)

I think step 3 was the key to success.