#Why is my automation delayed ~2+ hours?

1 messages · Page 1 of 1 (latest)

sly lotus
#

My trigger is for 06:00:00 but it fired at 08:13:29?

image.png
#

here's the full config:

id: '1733239738385'
alias: Holiday Lights On (Morning)
description: ''
trigger:
  - platform: time
    at: '06:00:00'
condition: []
action:
  - type: turn_on
    device_id: 74364f5b5aba232773ff5ffad4021800
    entity_id: 04eadf3fa333b5741676761197c365fb
    domain: switch
  - type: turn_on
    device_id: ff87cabaaaef8c3fb3d7a2c2250fec54
    entity_id: 5c8c2374491ff21f8b5b57e8eeedfdf5
    domain: switch
  - type: turn_on
    device_id: b83676eb14172c01898e4b19a1d9e184
    entity_id: 6cc4f288a80b64420c9eb04492e0481d
    domain: switch
mode: single
#

Additionally, it didn't fire today, and I don't see any lots/warnings

sly lotus
#

here's a similar automation with a similar outcome:

image.png
ivory raven
#

I think when I've heard of this occuring it's usually due to something screwed up with the clock inside a VM.

#

I can't say if that is your case though.

sly lotus
#

How would I identify that; it's a docker container. Host machine clock is correct. docker exec homeassistant date is right

#

{{ now() }} in template editor is correct too

ivory raven
#

Sorry don't have any more than that. Maybe someone else knows.