Platform:time automation triggered too late

Configuration
1

I got the Amazon echo dot speaking HA notifications, a Sonoff Panel display my entities, but I can’t get a simple automation triggered in time. :frowning:
Running out of ideas here …

The automation below scheduled for a specific time gets triggered about 20 mins late. Anyone seen this before and knows how to solve this?

Trace:
Triggered by the time at 10. Oktober 2022 um 07:22:39
Test if any of 2 conditions matches
Benachrichtigung: Send a notification via alexa_media_stefans_echo_dot
Finished at 10. Oktober 2022 um 07:22:39 (runtime: 0.03 seconds)

Automation:

alias: "Kind: Morgens um 7 aus dem Haus"
description: ""
trigger:
  - platform: time
    at: "07:00:00"
condition:
  - condition: or
    conditions:
      - condition: state
        entity_id: sensor.dayoftheweek
        state: Monday
      - condition: state
        entity_id: sensor.dayoftheweek
        state: Friday
action:
  - service: notify.alexa_media_stefans_echo_dot
    data:
      message: >-
        Hey ... es ist 7 Uhr. Es wird langsam Zeit, wenn Du den Bus
        erwischen möchtest... 
      data:
        type: tts
mode: single

As you can see from the trace, the automation gets executed and I can hear the message. Just way too late…

2

This is a relatively common occurence with a couple different types of VM software. If you are using a VM, you will need to check that the system time of you VM is correct, check the setup of your machine’s NTP server connection, or disable paravirtualization…

1 Like
3

VirtualBox system time is correct, NTP server up and running, but disabling paravirtualization did the job.

Thanks a lot! :slight_smile:

1 Like