I have made an automation that is to trigger at a certain hour each day but it will never trigger. I tried putting multiple triggers if it could be a daylight savings problem but it doesn’t help. If I trigger it manually it shows the correct time in the “trace timeline”. Time zone is
(GMT+01:00) Stockholm in general settings. Any tips on what to check?
alias: Test
description: test
trigger:
- platform: time
at: "14:38:00"
- platform: time
at: "15:38:00"
- platform: time
at: "16:38:00"
- platform: time
at: "13:38:00"
- platform: time
at: "12:38:00"
condition: []
action:
- service: notify.mobile_app_iphone
data:
message: Test
title: "Test "
mode: single
Might be worth looking at resource usage because if a simple automation like that is not triggering, it sounds like the system is extremely busy.
As for why an automation becomes unavailable briefly, that’s normal, when you create any automation or edit one, and press save - all the automations are reloaded, so briefly they become unavailable until they are loaded back in.
I tried adding the time date platform and when I create a card to show the time its very often of by 5-10 minutes. For example, now the time is 21:43 but the sensor.time says 21:36.
In the history the time sensor gets updated every 2-10 minutes (16:00, 16:01, 16:06, 16:12) Could it be that if I have an automation to trigger at 16:04 it doesn’t because the sensor never becomes 16:04?
Yes, but that is resource usage from INSIDE the Virtual Machine. The actual host is a Macbook - and if that becomes bogged down, then the CPU cycles aren’t there to keep the VM running smoothly. But from inside the Virtual Machine it won’t show you any issues, because it has no idea about the system resources on the host itself.
If you go to the VM and type login on the command line, and then dmesg there is a good chance you will see messages complaining about the hard drive being busy or the CPU frequency or something similar, because when the VM wants to do something, but the host CPU isn’t able to allocate CPU time to the VM, then the VM will misbehave.
Scrolled through it manually and can’t find anything about any killed processes. The system runs quite smooth. Shouldn’t it be very bogged down if it should miss a simple time trigger?
