Smart-Home Automations Not Triggering? How to Fix Them
When a smart-home automation stops triggering, the cause is almost always one of four things: the trigger condition never actually fires, a sensor or presence signal is delayed or stale, the hub or controller that runs the logic is offline, or a hidden condition (time window, device state, or "only when home") is quietly blocking it. The fastest path to a fix is to isolate which of those four is failing rather than rebuilding the routine from scratch. This guide walks through that process in order, from the quickest checks to the deeper ones.
Step 1: Confirm whether the action works at all
Before assuming the trigger is broken, find out whether the actions still work. Most platforms let you run a routine on demand—look for a "play" or "run" control next to the automation in the Alexa app, the Google Home app, or your platform of choice.
- If it runs manually but not automatically: the problem is the trigger or a condition. Continue to Step 2.
- If it fails even when run manually: the problem is a device or the action itself—one of the target devices is offline, was renamed, or was removed. Check that every device in the action still appears and responds in the app.
This single test saves the most time, because "my automation isn't triggering" and "my automation triggers but nothing happens" have completely different causes.
- 1Run the automation manually
- 2Re-read every trigger and condition
- 3Verify the trigger sensor reports state changes
- 4Confirm the hub or controller is online
- 5Rebuild the trigger if it’s stale
Step 2: Re-read the trigger and every condition
Open the automation and read it literally, the way the platform executes it. A surprising number of "broken" automations are working exactly as written—just not as intended. Watch for these common traps:
- Time windows: A routine set to run "at sunset" or "between 6 PM and 11 PM" will never fire outside that window, even if its trigger condition is met.
- Presence / "only when home": If the automation requires someone to be home and presence detection is wrong, it silently skips. Phone-based presence is notoriously unreliable when location permissions are set to "While Using" instead of "Always."
- Device-state conditions: "Turn on the fan when temperature rises above 78°—only if the AC is off" won't fire if the AC reports "on."
- One-time vs. repeating: Some platforms treat a trigger as edge-based (fires once when state changes) rather than level-based (fires the whole time a state is true). A motion automation fires on the transition to "motion detected," not continuously.
Step 3: Check that the trigger sensor actually reports
An automation can only fire if its trigger device is sending fresh state updates. Open the trigger device's history or activity view in your app and confirm it has logged recent changes.
| Trigger type | What to verify | Common failure |
|---|---|---|
| Motion / contact sensor | Recent open/close or motion events in history | Dead battery, or sensor dropped off the mesh |
| Temperature / humidity | Values updating over time | Reporting interval too long to cross the threshold cleanly |
| Phone presence / geofence | Location permission set to "Always" | Background location disabled by the OS |
| Voice / button | Device shows online and responds | Renamed device breaks the link to the routine |
| Time / sunset | Correct time zone and home location | Wrong location pushes sunset hours off |
A dead sensor battery is the single most common cause of a motion or contact automation that "used to work." If the sensor's last-seen timestamp is old, replace the battery and re-pair if needed before touching the automation itself. Sensors that keep dropping off point to a connectivity problem—see our guide on a device that keeps going offline.
Step 4: Confirm the hub or controller is online
Where the automation logic runs matters. Cloud routines (most Alexa and Google Home routines) depend on the platform's servers and your internet connection. Local automations—those run by a SmartThings hub, a Home Assistant instance, or Apple Home with a home hub—keep working during an internet outage but fail if the controller itself is unreachable.
- If the hub is offline or rebooting, time-based and sensor-based automations queue up or skip entirely.
- A hub that drops off intermittently produces automations that fire "sometimes." That symptom usually traces to power or network instability—our guide on stabilizing a hub that keeps disconnecting covers the fixes.
- For Thread-based devices, a missing or overloaded border router can stop sensor events from reaching the controller. See Thread border routers you may already own.
Step 5: Rebuild the trigger (not the whole routine)
If everything checks out but the automation still won't fire, the link between the trigger device and the routine may have gone stale—common after a device is renamed, re-added, or migrated to Matter. Rather than rebuilding the entire automation, delete just the trigger and re-add it by re-selecting the device. This forces the platform to re-bind to the current device ID.
If you're recreating routines in Google Home, our walkthrough on creating Google Home routines and automations shows where each trigger and condition lives in the current app.
Step 6: Rule out network and timing issues
Sluggish or unreliable triggering often comes down to the network underneath. A sensor on a congested 2.4 GHz band, a router that's hit its device limit, or Wi-Fi devices fighting Zigbee/Thread interference can all delay the state changes automations depend on.
- Keep smart-home devices on a stable 2.4 GHz network—see 2.4 GHz vs 5 GHz for smart-home devices.
- If responses lag well after a trigger fires, our guide on fixing smart-home lag covers the network-side causes.
Frequently asked questions
Why did my automation stop working after I added a Matter device?
Migrating a device to Matter or re-adding it usually changes its underlying identifier. Any automation that referenced the old device keeps pointing at something that no longer exists. Re-select the device inside the automation's trigger and action steps so the routine binds to the new identity.
Why does my automation fire sometimes but not always?
Intermittent triggering almost always points to connectivity, not logic. A sensor dropping off the mesh, a hub that disconnects under load, or presence detection that's slow to update will all produce "works sometimes" behavior. Check the device and hub history for gaps that line up with the misses.
Will my automations still run if my internet is down?
It depends where the logic runs. Cloud routines (most Alexa and Google Home routines) need internet access. Locally processed automations—SmartThings hub, Home Assistant, or Apple Home with a home hub—continue running during an outage, though anything that depends on a cloud service or voice assistant won't.
Do I need a hub for reliable automations?
Not always, but a local hub makes automations faster and more resilient to internet hiccups. Our guide to whether you still need a hub walks through when it's worth it for your setup.
