Automation Time Pattern Lag

1

For the life of me I can’t figure out why these announcements are coming 30 seconds - 1 min late.

  • Running on a Mac mini, 16gb ram, in Docker, Docker allocated with more than enough resources. Time is correct.
  • Running just the announcement action runs immediately.
  • An Automation with an exact time runs immediately, yes with a little lag on the cloud notify, understandable.
  • I’ve adjusted the Minutes, Seconds, Hours in the time pattern.
alias: Hourly Chimes
description: ""
trigger:
  - platform: time_pattern
    minutes: "0"
    seconds: "1"
    hours: /1
condition:
  - condition: state
    entity_id: input_boolean.chime_announce
    state: "on"
  - condition: time
    after: "08:00:00"
    before: "22:00:00"
action:
  - service: notify.alexa_media
    data:
      message: >-
        <speak><voice name='{{ ['Brian', 'Amy', 'Joey', 'Salli', 'Aditi',
        'Nicole', 'Kimberly', 'Justin'] | random }}'>It is now, {{
        now().strftime('%-I') }} a clock.</voice><audio
        src="soundbank://soundlibrary/bell/chimes/chimes_07"/></speak>
      target:
        - media_player.catherine
        - media_player.craft_room_echo
        - media_player.dining_room
        - media_player.garage
        - media_player.guest_room
        - media_player.kitchen
        - media_player.living_room_basement
        - media_player.living_room_echo
        - media_player.master
        - media_player.scott_s_ecobee_smartthermostat_with_voice_control
        - media_player.scott_s_office
        - media_player.screen_porch
        - media_player.shop
        - media_player.squirrel
        - media_player.groggy_gym_echo
mode: queued
max: 18
2

Have a read of this topic: Automation time not working correctly - #18 by pnbruckner

1 Like
3

I sure didn’t see that one in my search. While reading this particular one and the rest of the thread, I fully understand what he is saying, and it makes perfect sense, however, unfortunately I was unable to detect any resolution throughout the thread. It seemed like the problem at hand was it the machine was a little old, whereas mine is not. It was a little over my head.

4

Ah ok, I just remembered that it was a Mac mini too.

Might be worthwhile trying the clock drift integration in that topic though.

5

I’ll give it a go.

1 Like