If you’ve ever asked yourself why did my home assistant automation stop working, you already know the particular frustration of it: everything was fine yesterday, you changed nothing (or so you think), and now the lights stay on all night or the morning routine never fires. HA is powerful precisely because it runs locally without depending on someone else’s cloud — but that power comes with real diagnostic responsibility when something breaks.
This guide runs through six checks in a specific order. Order matters. Jumping straight to YAML when the real culprit is an unavailable entity wastes an hour. Work top to bottom and you’ll almost always hit the cause before you reach the bottom.
Check 1 and 2: The Entity and the Trigger — Start Here Every Time
Open your automation in the HA editor and look at every entity it references. An entity that has gone unavailable — shown as grey or explicitly labelled — will silently kill an automation without logging an obvious error. This is the single most common cause of home assistant automation not triggering after an integration update or a device reboot.
The fastest way to confirm this is to navigate to Developer Tools → States and search for the entity ID. If it shows unavailable or unknown, the trigger or condition depending on it will never fire correctly. Fix the device or integration first, then retest the automation.
If the entities all look healthy, move to the trigger itself. A time-based trigger that used to fire at sunset can drift if your home’s coordinates are wrong in Settings. A state trigger set to fire when a sensor goes on will silently fail if the sensor now reports true instead — a small vocabulary shift that happens when you swap integrations. These mismatches are a classic home assistant automation common problem that the community calls the “it just works until it doesn’t” moment.
Check 3 and 4: Conditions and the Automation Toggle
Conditions are evaluated after the trigger fires. They are also the most quietly limiting part of any automation. A condition checking whether someone is home will block the automation every single time presence detection disagrees with reality — and presence detection fails more often than most tutorials admit.
To isolate the condition, temporarily disable every condition block and trigger the automation manually from the UI. If it runs cleanly, one of your conditions is the culprit. Add them back one at a time until the failure reappears — that is your problem condition.
The toggle check sounds too obvious to mention, but it trips up experienced users after a restore or migration: confirm the automation itself is enabled. A migrated automation, a duplicated automation, or one touched during a Home Assistant update can land in a disabled state with no visible warning on the dashboard. Check the automations list and look for the small toggle next to the name.
Check 5: Broken YAML and What a Recent Update Actually Changed
If you write automations in YAML — and many HA users do once they outgrow the visual editor — a single indentation error is enough to break the entire automation file silently. HA will load, nothing will crash visibly, and your automation simply will not exist in memory.
Run Developer Tools → YAML → Check Configuration and read the output carefully. If you see an error referencing your automations file, that is your answer. Common YAML mistakes include mixing tabs and spaces, forgetting a colon after a key, or pasting a block that assumed a different indentation level than your file uses.
Home assistant automation broken after update is its own category of problem. HA releases deprecate services and rename entities over time. An automation calling a service like light.turn_on with a parameter that no longer exists in that form will fail after an update even though the YAML itself is syntactically valid. Check the HA release notes for the version you just installed — the breaking changes section is short and specific, and it will tell you exactly which service names changed.
The table below summarises the six checks with what to look at and roughly how long each one should take a beginner:
| Check | Where to Look | Time Estimate |
|---|---|---|
| 1. Entity availability | Developer Tools → States | 2–5 minutes |
| 2. Trigger accuracy | Automation editor, trigger block | 5–10 minutes |
| 3. Conditions blocking | Automation editor, condition block (disable and re-enable) | 5–10 minutes |
| 4. Automation toggle | Settings → Automations list | Under 1 minute |
| 5. YAML errors | Developer Tools → YAML → Check Configuration | 5 minutes |
| 6. Trace log | Automation → Traces (three-dot menu) | 5–15 minutes |
Check 6: Reading the Automation Trace — Your Best Debugging Tool
If you have worked through checks one through five and the automation is still broken, the trace log is where the answer lives. Open your automation, click the three-dot menu, and select Traces. HA records the last several runs and shows you exactly which step succeeded, which step failed, and why.
The trace view colour-codes each node: green means it passed, red means it stopped there. A red condition node with the value it actually evaluated tells you far more than any amount of guessing. This is the home assistant automation debugging step that most beginners skip because they do not know it exists — and it is the one that resolves the trickiest home assistant automation fails to execute situations in minutes rather than hours.
If the trace shows zero recent runs, the trigger never fired. Go back to check two. If the trace shows the trigger fired but action was skipped, a condition blocked it — go back to check three. The trace is not just a fix; it is a map of your automation’s actual behaviour versus what you intended.
For a structured walkthrough of building and troubleshooting automations from the very beginning — covering entities, integrations, helpers, and YAML in plain language — the Home Assistant Smart Home for Beginners guide from The Skill Mill walks through each concept in the order you actually need it. It is written for people who are done watching three-hour YouTube walkthroughs and want something they can read at their own pace.
You might also find these related posts useful as you build out your setup: building your first automation in one evening and why the backup you have never restored is not really a backup.
For deeper reading on smart home standards and how local control fits into the broader ecosystem, the Home Assistant project homepage and the Connectivity Standards Alliance (the body behind the Matter standard) are reliable starting points.
Frequently Asked Questions
- Why did my Home Assistant automation stop working after an update?
- HA updates occasionally deprecate service calls or rename entity attributes. Check the release notes for breaking changes, then use Developer Tools → YAML → Check Configuration to confirm your YAML is still valid. The automation trace will show exactly where the failure occurs.
- What does it mean when an entity shows as unavailable in HA?
- An unavailable entity means HA cannot currently communicate with that device or integration. Any automation trigger or condition that depends on an unavailable entity will silently fail. Fix the underlying integration or device first, then retest your automation.
- How do I know if my automation trigger is even firing?
- Open the automation, click the three-dot menu, and select Traces. If there are no recent trace entries, the trigger never fired. This is the fastest way to separate a trigger problem from a condition or action problem.
- Can a condition block an automation without any error message?
- Yes — this is one of the most common home assistant automation issues. A condition that evaluates to false stops execution silently. Use the trace view to see the exact value each condition evaluated, and temporarily disable conditions to isolate the one causing the block.
- Is YAML required to write Home Assistant automations?
- No. The visual automation editor handles most common use cases without any YAML. YAML becomes useful for complex logic, templates, or automations copied from the community. If you do use YAML, indentation errors are the most frequent cause of automations failing to load at all.
- What is the fastest single check to run first when an automation breaks?
- Go to Developer Tools → States and confirm every entity the automation references is available and reporting a sensible value. An unavailable entity is the most common cause of home assistant automation not triggering, and this check takes under five minutes.
Have you worked through all six checks and still have a broken automation? Drop the trace output or a description of your trigger setup in the comments — the HA community is remarkably good at spotting the one line that everyone else misses.
{“@context”:”https://schema.org”,”@type”:”BlogPosting”,”headline”:”Why Did My Home Assistant Automation Stop Working: Six Checks in Order”,”description”:”Why did my Home Assistant automation stop working? Follow these six diagnostic checks in order to find and fix the problem fast in HA.”,”keywords”:[“home assistant automation not triggering”,”home assistant automation troubleshooting guide”,”why did my home assistant automation stop working”,”home assistant automation debugging steps”,”home assistant automation broken after update”,”fix home assistant automation not running”,”home assistant smart home automation issues”,”home assistant automation checklist troubleshooting”,”home assistant automation fails to execute”,”home assistant automation common problems and fixes”],”datePublished”:”2026-08-27T12:25:37.695Z”,”dateModified”:”2026-08-27T12:25:37.695Z”,”author”:{“@type”:”Organization”,”name”:”The Skill Mill”},”mainEntityOfPage”:”https://blog.theskillmillbooks.com/why-your-home-assistant-automation-stopped-working-six-check/?utm_source=skillmillblog&utm_medium=blog&utm_campaign=home-assistant-smart-home&utm_content=why-your-home-assistant-automation-stopped-working-six-check”}
Tools that help: our Vault & Press spreadsheet · MineStock Pro.
Leave a Reply