Time-based automations stopped working with 2026.3, does anyone else have this?

Configuration
1

I just noticed all my time based automations (e.g. 10am each day) stopped working three days ago, I guess this matches with my upgrade to 2026.3.

Does anyone else have this problem, or is it just me?

2

Timed automations still working here.

3

Does it have the right time?

4

Every time this comes up, it’s always the automation condition that’s stopping the trigger.

5

Yes, the system is on right time.
Both time based and sunrise/sunset based automations have stopped working totally for me during recent updates.

6

Not in this case. There are no conditions, just a simple trigger.
E.g. “when time is 10 pm”, or “when sun sets”…nothing like this works anymore.

7

Show you system time matching the current time. Also, make a time based automation and wait 24 hours and see when it triggers.

8

System time is right. The time / sun based automations stopped working at the same moment with the latest Core update and the automations have not been triggering at all since.

Daily automations are not firing for 6 days already.

9

Then your system time is not right.

Please tell us the time in your tz and then paste the result of {{ now() }} in developer tools template editor.

Post an automation that’s not working as well.

10

Thank you for trying to help me here.
I checked the result in the template editor and the given response matched my system time.

I then decided to not only restart HA, but also reboot the host machine, and since that time, automations seem to work again.

11

I confirm the same behavior. Time-triggered automation is not firing after a reboot after a scheduled power outage. Trace of automation shows that the condition stage was never reached. Time and time zone are properly configured in the base machine and in the container (verified via the template editor). Sure, I can restart and hope it gets “fixed”, but this is clearly a bug that needs to be squashed.

12

Traces aren’t generated if conditions aren’t met. Double check your condition again.

13

@NateRobinson

Time will always work on home assistant or home assistant will be in a boot loop. There’s no way around this. Time may be incorrect, but it will always work at the incorrect time.

There are 4 common scenarios that users run into when they are blaming “time not working”.

  1. The user has a raspberry pi and the rasberry pi failed to reach the ntp server when it booted up. Rpi’s do not have a cmos battery, meaning they get their time from NTP servers. When they can’t reach the ntp server, the time defaults to january 1st 1970 at midnight. In this situation, your time triggers will still occur but they will occur in relation to January 1st 1970. Rebooting the host will fix this problem assuming the pi can reach an NTP server after reboot.
  2. The user has a system where the cmos battery is dead and the system failed to reach an NTP server. Rebooting the host will fix this problem assuming the pi can reach an NTP server after reboot.
  3. The user is running on a VM and the VM is in an error state or the time settings for the VM are wrong. This typically results in time triggers occuring minutes before or after the actual time. The VM has the correct time once a day, but it slowly creeps to the wrong time throughout the day. Fixing the vm time settings and rebooting the vm solve this problem.
  4. A condition is blocking the only automation the user is checking from storing a trace. Fixing this requires the user to look at each condition in the automation and verify that it’s passing.

Secondly, when users check to see if there system time is correct, they typically look in the wrong spot. The only way to properly check system time is to use the time integration and to view sensor.time entity. Or to use {{ now() }} in settings → developer tools → template editor. If you viewed your time in any other way you are not looking at the system time, you are looking at your browser time

So, before anyone else replies with “Me too” or some derivation of that. You need to prove that your system time is actually correct.

  1. Place {{ now() }} into settings → developer tools → template editor. Take a screenshot on your mobile device of this result ensuring that your mobile device time is in the screenshot.
  2. Create the following automation and wait 48 hours for it to trigger.
    alias: Verify Time
triggers:
- trigger: time
  at: "10:00:00"
actions:
- action: persistent_notification.create
  data:
    title: "{{ now() }}"
    message: "{{ now() }}"
    Then, when the message appears in notifications, take a screenshot of the notification. You’ll also have an automation trace. You need to go to the trace, click the overflow menu (3 dots) and download the trace. Paste that here as well.
1 Like