I have 2 time based automations, one which should trigger at 9am and one which should trigger at 5pm, both these automations trigger late.
The 9am automation triggers at 9.53
alias: Stephs Bedroom Blind Open
description: ''
trigger:
- platform: time
at: '09:00:00'
condition: []
action:
- device_id: 45a6d3fb36ae42b7a69fbe8c73422317
domain: number
entity_id: number.lumi_lumi_curtain_acn002_61192e00_analog_output
type: set_value
value: 100
- type: turn_off
device_id: 1d11b3e90014fd066d56635c265bcb2d
entity_id: light.tz3000_9hpxg80k_ts0011_96bbc3fe_on_off
domain: light
mode: single
The 5pm automation triggers at 5.54?
alias: Stephs Bedroom Blind Close
description: ''
trigger:
- platform: time
at: '17:00:00'
condition: []
action:
- device_id: 45a6d3fb36ae42b7a69fbe8c73422317
domain: number
entity_id: number.lumi_lumi_curtain_acn002_61192e00_analog_output
type: set_value
value: 0
mode: single
Home assistant runs in a VM on ESXi, I have the NTP service synced to the uk ntp pool, running on ESXi and the VM is using the host NTP service as its time source.
The log times and the time component all show the correct time, but the timers trigger late.
Does anyone have any idea on other items to check, so I can understand wh there is a 53/54 minute delay?
Have you checked the trace to see the timeline of the nodes in the automation? Maybe there’s a clue there. Or could something else than the time trigger have called these automations too?
If the time was off, I guess it would have said it ran at the right time even if it was late.
This is indeed weird. It looks like the time event is either triggered way too late (and not because the clock is off) or the event is picked up way too late. Without knowledge on how this is handled internally it is mostly wild conjecture what would be amiss. The only guess I can still come up with: if the events go through the recorder before being picked up from the database, could it be the recorder database is in trouble? Are you using Mariadb or other storage and is that in good health and running with the right system time?
I remember a thread (that I can’t find) about a VM that was incorrectly configured and a minute in the VM was not the same duration as a minute in real life. This cause time triggers (and other things) to occur much later than expected. I can’t remember much else about the thread. I know it was solved in the end.
I just use the standard recorder function, I use the Ingress database with Graphana for visualisation but I haven’t modified the HA settings. Interestingly the automations which are triggered by sunrise and sunset are also 50ish minutes out as well.
Hi, I have a similar same problem.
I press a switch and it instantly tells me “pressed 35 minutes ago.” HA runs always 35 minutes behind.
Any way to solve? Thank you!
