Start with the trace, not the guess
It matters whether the trigger never fired, a condition blocked the run, or an action failed at the last step.
Why your Home Assistant automation did not run
This page is for the moment when an automation should have fired, but did not. The goal is to separate trigger failure, condition failure, action failure, and unavailable entities before the logic gets rewritten or the whole setup gets blamed.
Recent changes usually matter
Entity renames, helper edits, schedule changes, and unavailable devices often explain more than the automation name alone.
Do not rewrite everything at once
One clear failure stage is easier to fix than a full rebuild of the automation path.
Keep the automation check small
- Open the trace first and identify whether the trigger, condition, or action stage failed.
- Check whether any related entity was unavailable or stale when the automation should have run.
- Notice whether the issue started after a rename, schedule edit, helper change, restart, or integration update.
- Isolate one failing action instead of editing every trigger and condition at the same time.
Open the next page that matches what the trace shows
Start with device-offline recovery if the action failed because entities were unavailable. Start with the beginner automation guide if the whole logic still feels too complex.
If the symptom stays active