Technician helping fix SmartThings Hub automations not triggering and routine issues

Steve H.

Reviewed for technical accuracy

Specialities: SmartThings Hub (Aeotec / SmartThings v2/v3), SmartThings app & Samsung account troubleshooting, automations & routines not triggering, local vs cloud execution, Zigbee & Z-Wave mesh reliability

SmartThings automations not running — hub offline checks, device status updates, Zigbee/Z-Wave fixes & routine troubleshooting

Technician avatar Technician
Hey! We’ll fix your SmartThings Hub automation not triggering issue. When a SmartThings routine doesn’t run, it’s almost always one of these: (1) the hub is offline/updating, (2) the trigger device isn’t sending events (device status not updating), (3) the automation is blocked by conditions (time window, mode, location, “only when”), or (4) it’s a cloud routine and the platform is having a hiccup.

Quick questions so we check the right thing first (and avoid factory resets):
• What’s the trigger type: motion sensor, contact sensor, button, switch state, power/energy change, schedule, sunrise/sunset, or geofence (arrive/leave)?
• What hub do you have (Aeotec Smart Home Hub / SmartThings v2/v3)? Is the hub showing Disconnected in the SmartThings app?
• Do you see the device event happen (e.g., motion turns “active” in the app) but the automation still doesn’t fire, or does the device itself not update?
• Is this a new automation or one that “worked before and suddenly stopped” (after a firmware update, Edge driver change, router change, or moving devices)?
• Any conditions: “only between 10pm–6am,” “only when Mode is Home,” “stays this status for X minutes,” or multiple conditions combined?

Reply with that and I’ll give you the fastest step-by-step plan to get your SmartThings automation working again.
Customer
I have an Aeotec Smart Home Hub. My main issue is a motion sensor automation not triggering: when motion is detected, it should turn on a light for 5 minutes. It used to work, now it doesn’t. Sometimes the sensor shows motion in the app, sometimes it’s delayed. I also have a schedule automation that should turn off lights at midnight and it missed twice this week. Hub sometimes shows “online” but a few devices look “offline.”
Technician avatar Technician
Perfect description — the giveaway is “device status sometimes delayed” plus a missed schedule. That points to either:
• the hub briefly losing connectivity (or updating),
• a flaky Zigbee/Z-Wave mesh path (sensor events don’t reach the hub reliably),
• or a platform-side issue where cloud automations and scheduling get inconsistent.

The best “check first” order is:
1) confirm there isn’t a SmartThings platform outage affecting automations/schedules,
2) confirm the hub isn’t updating / half-offline,
3) confirm the sensor’s events are solid and the hub can “hear” them consistently,
4) then clean up automation conditions (time windows/modes) and refresh the routine.

We’ll do quick tests that take minutes and tell us exactly which bucket you’re in.
Customer
Okay. The motion sensor is Zigbee. The automation is: “If motion detected, turn on kitchen light. Turn off after 5 minutes.” It also has a condition “Only between sunset and sunrise.” The midnight schedule automation is separate. Where do I start right now?
Technician avatar Technician
Start with two checks that prevent a ton of wasted troubleshooting.

Step 1 — Check SmartThings platform status (rules out an outage)
Open the SmartThings Status page and look for incidents impacting Device Control, Hub Connectivity, or the Mobile App. If SmartThings is having an incident, routines can appear “broken” even when your devices are fine.

Step 2 — Look at the hub LED + “updating” behavior
If your hub LED is showing an update state (or the app shows the hub as disconnected during an update), don’t reboot it mid-update. A hub update can temporarily break routine triggers and make devices look offline until it finishes.

Step 3 — Quick reboot ladder (safe + fast)
1) Close and reopen the SmartThings app (force-close helps if the app is stuck on old device state).
2) Reboot your router (yes, really — brief packet loss can cause missed triggers).
3) Reboot the hub (power unplug 30–60 seconds, then plug back in) only if it’s not updating.

After this, we’ll confirm whether the Zigbee motion sensor is sending clean events and whether the routine condition (“sunset to sunrise”) is blocking it.
Customer
I checked status and it says everything operational. Hub LED is solid blue. I rebooted router and hub. The sensor updates faster now, but the routine still doesn’t run every time. Also, sometimes it triggers in the daytime even though it says “only between sunset and sunrise,” which is weird.
Technician avatar Technician
That “daytime trigger” detail is gold — it screams location/time logic rather than a bad sensor.

Step 4 — Verify the SmartThings Location settings (sunset/sunrise depends on this)
In the SmartThings app, confirm you’re in the correct Location (some people have multiple), and verify the address/time zone is right. Sunrise/sunset automations depend on the hub’s location data and the location you created the routine in.

Step 5 — Confirm the condition isn’t “sticking” and blocking future triggers
If a routine has multiple conditions, SmartThings evaluates them together. If a condition becomes true before your time window starts, it can behave like it “already happened” and not fire again until it becomes false and then true again. For motion routines, this can show up as “works sometimes” or “stops triggering.”

Fast isolation test (takes 2 minutes)
Duplicate the routine and temporarily remove the “sunset to sunrise” condition. Test motion 5–10 times. If it becomes 100% reliable, we know the trigger path is fine and the issue is the time/condition logic.
Customer
I duplicated the routine and removed the sunset/sunrise condition. The motion automation triggers every single time now. So it’s definitely the condition/time part. How do I keep the “night only” behavior without it breaking?
Technician avatar Technician
Great — now we fix it in a way that’s reliable and still SEO-friendly in real life: simplify the condition so the routine can’t get “stuck.” Here are the best patterns for “night only” SmartThings routines.

Option A (most reliable): use a Mode or virtual “Night” switch
1) Create a routine: At sunset → set Mode to Night (or turn ON a virtual switch called “Night”).
2) Create a routine: At sunrise → set Mode to Day (or turn OFF “Night”).
3) Your motion routine becomes: “If motion detected AND Mode is Night (or Night switch is ON) → turn on light.”

Why this works: the motion routine no longer depends on sunrise/sunset calculations at the exact moment it triggers. It just checks a simple state (Mode / switch) that’s already correct.

Option B: keep the time window, but remove extra complexity
If you keep “only between sunset and sunrise,” avoid stacking too many extra conditions like “stays this status for” or multiple sensors + time windows, because that’s when routines can appear inconsistent.

If you want, tell me whether you already use SmartThings Modes (Home/Away/Night) — I’ll tailor the cleanest setup.
Customer
I don’t really use Modes right now, but I can. That makes sense. What about the other issue — the schedule automation missed (lights off at midnight). Is that related, or a separate problem with the hub?
Technician avatar Technician
It can be related — but we’ll verify instead of guessing.

A SmartThings schedule automation can miss when either (a) the hub/app loses connectivity at the scheduled time, (b) the platform has a brief issue, or (c) the target device is unreachable (shows offline / wrong status).

Step 6 — Quick “midnight miss” checks
1) Look at the hub’s connectivity around that time: any ISP drops, router reboots, or Wi-Fi channel changes? Even a short blip can cause a missed scheduled action.
2) Check if the target devices are Zigbee/Z-Wave and sometimes show Disconnected. If the hub can’t reach the device, the schedule can “run” but the light won’t actually change state.
3) Hub placement matters: don’t stack the hub right next to a Wi-Fi router (interference can affect Zigbee), and avoid putting the hub behind metal or inside cabinets.
4) Confirm the SmartThings app is updated. App glitches can make it look like a routine didn’t run when the device actually changed state later (delayed status refresh).

If you tell me what kind of lights those are (Zigbee bulbs, Z-Wave switch, Wi-Fi bulbs, Matter), I can give the most likely culprit and the best “first fix.”
Customer
The lights are a Zigbee smart plug and a Zigbee bulb. The hub is literally sitting right next to my Wi-Fi router on the same shelf. Also, the missed schedule happened on a night when my internet was a bit unstable (streaming was buffering).
Technician avatar Technician
That’s a classic combo: unstable internet + hub next to router + Zigbee devices. Here’s the practical fix path that improves both routine reliability and device status updates.

Step 7 — Move the hub to reduce interference (big win)
Move the hub a few feet away from the Wi-Fi router (even 1–2 meters helps). Wi-Fi can interfere with Zigbee depending on channels and proximity, and interference shows up as delayed events and “offline” devices.

Step 8 — Strengthen the Zigbee mesh for consistent triggers
Zigbee works best when you have solid “repeaters” (many mains-powered Zigbee plugs/switches act as routers). If the motion sensor is far away, make sure there’s a powered Zigbee device between it and the hub. This reduces dropped events so your motion sensor automation stays consistent.

Step 9 — Make schedules resilient
If your internet is unstable, some actions (especially cloud-dependent ones) can behave inconsistently. Keeping devices reachable locally (good Zigbee mesh) and keeping the hub stable reduces misses. Also, after moving the hub, give it a bit of time to settle and re-route the mesh (you should see fewer “offline” blips).

Next, we’ll lock in your “night only” motion logic using Modes so you get the behavior you want without the sunset/sunrise condition getting weird.
Customer
I moved the hub away from the router and already the sensor updates faster. I created Mode routines at sunset and sunrise like you said, and now the motion routine works perfectly at night. If this breaks again, what should I try first — recreate the routine, reboot the hub, or remove/re-add devices?
Technician avatar Technician
Love that — here’s the “do the least destructive thing first” ladder for SmartThings automation troubleshooting.

Do this first (2–5 minutes)
• Check status.smartthings.com (rules out platform incidents).
• Confirm hub is online and not updating.
• Toggle the trigger device and confirm its status changes in the app quickly (if the event is late, the automation will be late).
• Force-close SmartThings app and reopen (fixes stale status).

Next step
• Reboot router, then hub (only if not updating).
• If the routine uses complex conditions, simplify (Modes / virtual switch pattern) or recreate the routine cleanly.

Only if the device itself is unreliable
• For Zigbee/Z-Wave devices that keep going offline: move hub away from router, improve mesh, then consider removing and re-adding the device (last-resort before a full reset).

Factory reset (last resort)
• Only if the hub is unstable across everything (devices constantly offline, automations and manual controls fail, repeated disconnects) after updates and clean reboots.
Customer
Got it. After moving the hub away from the router, switching the “night only” condition to Modes, and confirming the sensor status updates fast, my SmartThings routines are triggering reliably again. Thanks!
Technician avatar Technician
Summary: when a SmartThings Hub automation is not triggering, check in order: (1) platform status/outage, (2) hub connectivity/updating, (3) whether the trigger device’s status updates quickly, and (4) whether automation conditions (sunset/sunrise, modes, time windows) are blocking or “sticking.”
Biggest wins here: move the hub away from Wi-Fi interference, strengthen the Zigbee mesh, and use Modes (or a virtual Night switch) for reliable “night only” behavior. Want me to optimize your setup for your exact hub model, Zigbee channel/Wi-Fi congestion, and device types (Z-Wave/Matter/Wi-Fi)? Open the chat and an expert will guide you in real time.

Quick answer: the accepted fix

Accepted first fix for SmartThings Hub automation not triggering: verify there’s no platform incident, confirm the hub is online (and not updating), then make sure your trigger device shows fast, consistent status updates in the app. If the automation uses sunrise/sunset or complex conditions, simplify by using Modes (or a virtual “Night” switch) set at sunset/sunrise, and trigger motion based on that state. For Zigbee/Z-Wave reliability, move the hub away from the Wi-Fi router and strengthen the mesh with mains-powered repeaters so events don’t get dropped.

Why SmartThings automations stop triggering

Most SmartThings routines not running problems come from one of four causes: a brief SmartThings platform outage, the hub going offline/updating, the trigger device failing to send events (you’ll see device status not updating or “offline”), or conditions that block the routine (time windows, Modes, sunrise/sunset, location). Zigbee/Z-Wave interference (especially when the hub sits next to a Wi-Fi router) can cause dropped events that look like “random” automation failures.

How to test if your SmartThings routine is fixed

Test in a controlled way: (1) open the trigger device tile and verify the event changes instantly (motion active/inactive, contact open/closed); (2) run a “no-condition” test routine (no sunset/sunrise, no Modes) to confirm the trigger path; (3) re-add conditions one at a time (Mode/Night switch first, then any time window); (4) confirm the action device responds instantly. If the event is fast and the action is consistent after a router/hub reboot, your SmartThings automation is stable again.

SmartThings Hub automation not triggering — quick troubleshooting tips

Most cases are fixed by checking platform status, stabilizing hub connectivity, and simplifying routine conditions.

Quick path: check SmartThings platform status, confirm the hub isn’t updating, and verify your trigger device’s status updates quickly in the app. If your routine uses sunset/sunrise, switch to a Mode or virtual “Night” switch set at sunset/sunrise, then trigger motion based on that state. For Zigbee reliability, move the hub away from the Wi-Fi router and ensure there’s a good mesh path via mains-powered repeaters.

Disclaimer: This information is AI-generated and intended for general guidance only. Do not open devices or attempt unsafe electrical work. For advice specific to your SmartThings Hub, device types, and automation logic, please consult a verified expert on Whizz-Tech or the manufacturer’s support before making decisions.

Understand what these prompts mean

Getting Started Is Easy

Ask for help, 24/7

Members enjoy round-the-clock access to 12,000+ verified Experts, including SmartThings Hub troubleshooting, Zigbee/Z-Wave reliability, and routine/automation fixes.

Expert will respond in minutes

We match you with an Expert who understands SmartThings routines, hub connectivity, device status events, and Zigbee/Z-Wave mesh troubleshooting. Chat step-by-step.

Save time & money

No guessing, no unnecessary resets. Fixing a SmartThings automation not triggering issue remotely can save hours of trial-and-error.

FAQ

Why is my SmartThings automation not triggering?

SmartThings automation not triggering is usually caused by a platform incident, the hub going offline/updating, a trigger device not sending events (device status not updating), or conditions blocking the routine (Modes, time windows, sunrise/sunset, location). Start by checking platform status, hub connectivity, and trigger device events.

How do I fix a SmartThings motion sensor automation not working at night?

Instead of relying on “only between sunset and sunrise” inside the motion routine, create separate routines that set a Night Mode (or a virtual Night switch) at sunset and reset it at sunrise. Then make the motion routine depend on Night Mode. This keeps SmartThings routines reliable even when time/condition logic gets finicky.

Why do SmartThings devices show offline and routines stop working?

If devices show offline, the hub may be updating, too close to Wi-Fi interference, or the Zigbee/Z-Wave mesh is weak. Move the hub away from the router, ensure powered repeaters are available, and confirm devices update quickly in the app. If there’s a SmartThings platform incident, routines can also appear broken temporarily.

Should I factory reset my SmartThings Hub when automations fail?

Factory reset is the last resort. First check SmartThings status, confirm the hub isn’t updating, reboot router/hub, verify trigger device events, and simplify/recreate the routine. Only remove/re-add devices or reset the hub if the system remains unstable across manual controls and multiple automations.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant
5 Tech Support Specialists are online right now.