Why My Home Assistant Timer Never Fires—and How to Fix It

If you’ve ever set a timer in Home Assistant and then stared at the clock wondering why nothing happened, you’re not alone.
The culprit is almost always one of three things:

  1. Time‑zone or daylight‑saving mis‑configurations
  2. Timer entity state or YAML syntax errors
  3. System clock drift or NTP hiccups

Below is a practical walk‑through that keeps the technical meat intact while sounding like a coffee‑shop chat between two sysadmins.


1. Verify the System Clock and Time Zone

Home Assistant piggybacks on the host’s clock. If that’s off, timers will be mis‑aligned or never fire.

1.1 Check the host time

timedatectl status

Typical output:

      Local time: Tue 2026-11-21 10:12:34 CET
  Universal time: Tue 2026-11-21 09:12:34 UTC
        RTC time: Tue 2026-11-21 09:12:34
       Time zone: Europe/Paris (CET, +0100)
       NTP enabled: yes
NTP synchronized: yes
 RTC in local TZ: no
      DST active: no
  • If NTP is disabled or synchronization is “no”, enable it:
sudo timedatectl set-ntp true
  • If the time zone is wrong, set it to your local zone:
sudo timedatectl set-timezone Europe/Paris
  • For Docker‑based HA, the container inherits the host’s time zone unless you override it. Add TZ=Europe/Paris to the container’s environment variables.

1.2 Test time‑zone‑aware timers

Create a quick timer that fires every minute:

timer:
  test_minute:
    duration: "00:01:00"

If it fires at 10:13:34 instead of 10:12:34, the clock is mis‑aligned.


2. Inspect the Timer Entity

A timer can live in configuration.yaml or a separate config/timers.yaml. YAML is unforgiving; a stray space can break the whole thing.

2.1 Common YAML pitfalls

Problem Symptom Fix
Missing indentation Timer not listed in Developer Tools → “Entity not found” Ensure two spaces per level
Wrong key name (duration vs time) HA reload fails with “unknown key” Use the correct key
Duplicate timer names One timer silently overrides the other Rename one of them

2.2 Example of a correctly defined timer

timer:
  morning_routine:
    duration: "00:30:00"
    trigger:
      - platform: time
        at: "07:00:00"

Tip: Open Developer Tools → States and look for timer.morning_routine. It should be in idle before 07:00:00.

2.3 Reloading configuration

After editing, reload timers without rebooting HA:

Configuration → Server Controls → Reload Core

If HA complains “Error loading configuration”, dive into the logs:

journalctl -u home-assistant.service -f

Search for YAML parsing errors or missing keys.


3. Understand Timer Lifecycle

A timer has three states: idle, active, and finished. It only starts when its trigger fires. If the trigger never fires, the timer stays idle.

3.1 Verify the trigger

With a time trigger, double‑check that the time is 24‑hour format and matches the host’s zone:

trigger:
  - platform: time
    at: "07:00:00"

If you’re using a numeric state trigger, confirm the sensor’s state in Developer Tools.

3.2 Test the trigger manually

automation:
  - alias: "Test Timer Trigger"
    trigger:
      - platform: event
        event_type: timer_started
        event_data:
          entity_id: timer.morning_routine
    action:
      service: notify.notify
      data:
        message: "Timer started!"

Fire the event from the command line:

hass-cli event timer_started --data '{"entity_id":"timer.morning_routine"}'

If you get the notification, the timer entity is fine; the problem is the trigger itself.


4. Check for Conflicting Automations

Sometimes another automation stops or resets the timer before it gets a chance to run.

automation:
  - alias: "Reset Timer on Motion"
    trigger:
      - platform: state
        entity_id: binary_sensor.motion_living_room
        to: "on"
    action:
      service: timer.cancel
      target:
        entity_id: timer.morning_routine

If this fires before 07:00:00, the timer never reaches active. Comment it out or adjust its logic.


5. Examine Home Assistant Logs

Logs are your best friend. Filter for timer activity:

journalctl -u home-assistant.service -o short-precise -f | grep timer

Typical entries:

2026-11-21T09:00:00.123456+00:00  INFO  (homeassistant.core) [timer.morning_routine] Started
2026-11-21T09:30:00.654321+00:00  INFO  (homeassistant.core) [timer.morning_routine] Finished

If you only see “Started” and never “Finished”, the timer never actually ran.


6. Use the timer.start Service for Debugging

You can fire a timer manually to see if it behaves.

automation:
  - alias: "Debug Timer Start"
    trigger:
      - platform: time
        at: "08:00:00"
    action:
      service: timer.start
      target:
        entity_id: timer.morning_routine

After 30 minutes, check the state:

hass-cli state get timer.morning_routine

If it shows active, the logic is sound; the issue is timing.


7. Consider Daylight‑Saving Time (DST) Edge Cases

In 2026, many regions switched to DST on the last Sunday of March and back on the last Sunday of October. If your timer lands on a DST transition, HA can mis‑calculate.

7.1 Use offset instead of absolute time

trigger:
  - platform: time
    at: "07:00:00"
    offset: "-01:00"

7.2 Verify with the time_date sensor

Add a sensor that shows local time:

sensor:
  - platform: time_date
    display_options:
      - local_time

Check its state in Developer Tools to confirm the clock during DST changes.


8. Keep Home Assistant Updated

Older releases had timer bugs. Stay on a recent LTS (2026‑02‑01 or later).

# Home Assistant OS
ha core update
# Docker
docker pull ghcr.io/home-assistant/home-assistant:stable
docker compose down
docker compose up -d

9. Practical Example: A Full Timer Setup

Below is a minimal, reproducible example that works on a fresh HA install.

# configuration.yaml
timer:
  coffee_maker:
    duration: "00:05:00"

automation:
  - alias: "Start Coffee Timer"
    trigger:
      - platform: time
        at: "07:15:00"
    action:
      service: timer.start
      target:
        entity_id: timer.coffee_maker

  - alias: "Notify When Coffee Is Ready"
    trigger:
      - platform: state
        entity_id: timer.coffee_maker
        to: "finished"
    action:
      service: notify.notify
      data:
        message: "Your coffee is ready!"

Deploy, reload HA, and watch the logs. If the timer still doesn’t fire, run through the troubleshooting steps above.


10. Security Note: Restricting Timer Access

If you expose HA to the internet, limit who can trigger timers. Use Long‑Lived Access Tokens and Role‑Based Access Control (RBAC).

automation:
  - alias: "Secure Timer Start"
    trigger:
      - platform: event
        event_type: timer_start_request
    condition:
      - condition: state
        entity_id: input_boolean.allow_timer_start
        state: "on"
    action:
      service: timer.start
      target:
        entity_id: timer.morning_routine

The input_boolean.allow_timer_start gate must be toggled before the timer can start.


11. Quick Checklist

✅ Item
System clock correct (timedatectl status)
NTP enabled (timedatectl set-ntp true)
Time zone matches your locale
YAML syntax correct (indentation, keys)
Timer entity exists (timer.morning_routine)
Trigger time in 24‑hour format
No conflicting automations canceling the timer
Logs show “Started” and “Finished” events
HA updated to latest LTS
Optional: security controls in place

Timers are a lightweight way to schedule actions in Home Assistant, but they’re only as reliable as the host clock, the YAML you write, and the triggers you set. By checking the clock, validating YAML, and inspecting logs, you’ll usually find that a mis‑configured time zone or a stray indentation is the culprit. Fix that, and the timer will fire on schedule, letting your smart home run like clockwork.

See also