Smart home technician helping fix a SmartThings hub boot loop

Steve H.

Reviewed for technical accuracy

Specialities: SmartThings hubs (v2/v3/Aeotec/SmartThings Wifi), Zigbee/Z-Wave pairing, hub firmware recovery, LED status patterns, power adapter issues, Ethernet/Wi-Fi/DNS, router ports & firewalls, Alexa/Google Home/Apple Home

SmartThings hub boot loop troubleshooting — power, firmware update, LED colors, and network fixes

Technician avatar Technician
Hey! We’ll fix your SmartThings stuck on a boot loop so the hub stops rebooting and shows up online again. To avoid guessing, tell me:
• Which hub is it: SmartThings Hub v3, older v2, Aeotec Smart Home Hub, SmartThings Wifi/Connect Home?
• What’s the LED doing during the loop: blinking green, solid magenta, blinking red, solid blue, or red/green blinking?
• Did this start after a firmware update, a router/ISP change, power outage, or moving the hub to a new room?
• Connection type: Ethernet cable to the router or Wi-Fi? Any mesh system, VLAN, guest network, or firewall rules?

With those details we can choose the right quick fix: clean power cycle, stable network path to the SmartThings cloud, or a safe reset pinhole procedure if it’s truly stuck.
Customer
It’s a SmartThings Hub v3 (I think) and it started rebooting over and over last night. The light goes green, then kind of purple/magenta, then it restarts again. It never becomes solid green and the SmartThings app shows the hub as offline. I didn’t change anything except my router updated a few days ago.
Technician avatar Technician
That pattern (boot → magenta → reboot) often points to one of three root causes for a SmartThings hub boot loop:
1) Power instability (weak/aging adapter, loose barrel connector, power strip issues) — the hub draws more current during boot/firmware checks and resets.
2) Can’t reach SmartThings services — DNS or firewall/ports block the hub during initialization, so it keeps trying and restarting.
3) Firmware update stuck/corrupted — especially after a power cut during an update, the hub can get stuck in a “boot loop after firmware update”.

We’ll start with the fastest low-risk steps (no data loss): a real power cycle + network sanity checks. Only if it refuses to stabilize do we go to a safe factory reset (pinhole reset).
Customer
I’m using Ethernet to my router. I tried unplugging it and plugging back in quickly, but it still loops. I’m worried if I factory reset the SmartThings hub I’ll lose my Zigbee and Z-Wave devices and routines.
Technician avatar Technician
Totally fair — we’ll avoid a reset until we’ve proven the hub can’t recover. Let’s do a true clean reboot first (this fixes a lot of “SmartThings keeps restarting” cases).

Step 1 — Clean power cycle (don’t skip the wait)
1) Unplug the power from the hub.
2) Unplug the Ethernet cable too (we’ll reseat it cleanly).
3) Wait 2 full minutes — this clears lingering states and lets capacitors drain (a 5-second unplug often does nothing).
4) Plug Ethernet back in (router side and hub side), then plug power back in directly to a wall outlet (skip power strips for this test).
5) Now do the hard part: leave it alone for 7–10 minutes. During boot/firmware checks the LED can cycle and look “stuck” but it may still recover.

Step 2 — Quick power sanity check
• If you have the original power adapter, inspect for looseness/heat.
• If you have access to a known-good compatible adapter (same voltage, equal or higher amperage, correct barrel size), testing it can instantly confirm a power issue. A borderline adapter is a top cause of random hub reboots and boot loops.

After this, tell me the exact LED behavior sequence and whether the hub ever becomes solid green or stays looping.
Customer
I did the 2 minute unplug and waited about 10 minutes after plugging back in. It still goes green blinking for a bit, then magenta/purple, then restarts. It never stays solid green. Ethernet cable seems fine but I can try another one. Could my router update cause this boot loop?
Technician avatar Technician
Yes — router changes can absolutely trigger a SmartThings hub boot loop, especially if the hub can’t complete its online checks. Here’s the quick network checklist that catches the common “router update broke my SmartThings hub” scenarios.

Step 3 — Prove the hub can reach the internet cleanly
1) Try a different Ethernet cable and a different LAN port on the router (bad port negotiation can look like a firmware problem).
2) In the router settings, confirm the hub is not on a guest network, VLAN-isolated segment, or behind “client isolation”. The hub needs normal LAN-to-internet access.
3) Check if your router enabled aggressive security features after update (examples: “IoT isolation”, “DoS protection”, “block unknown devices”, “parental controls”, “firewall high”). Temporarily relax them for testing.
4) DNS matters: if you use custom DNS (ad-block DNS, Pi-hole, “family filter”), temporarily switch router DNS to a standard provider or ISP default. A blocked domain can keep the hub stuck on initialization and rebooting.
5) Make sure the hub is getting an IP address (DHCP). If your router shows the hub connecting/disconnecting repeatedly, that matches the boot loop behavior you’re seeing.

If we stabilize the network path and it still loops, that pushes us toward firmware stuck or power adapter as the culprit.
Customer
I changed the Ethernet cable and port. Router shows the hub briefly, then it disappears and comes back as it reboots. I do use a Pi-hole DNS on my network. Also the hub power brick feels pretty warm. Should I disable the Pi-hole or is this a firmware update stuck situation?
Technician avatar Technician
Great clues. Let’s isolate two high-probability causes fast: DNS blocking and overheating / power instability (warm power brick + rebooting is suspicious).

Step 4 — Test without Pi-hole / ad-block DNS
• Fastest: temporarily set your router WAN DNS to ISP default or a standard public DNS, then reboot the router (just for testing).
• Alternative: create a DHCP reservation for the hub and assign it a different DNS (if your router supports per-device DNS), bypassing Pi-hole for the hub only.
• If the hub suddenly finishes booting and becomes solid green, you’ve confirmed “SmartThings boot loop caused by DNS/filtering”. Then we can whitelist required domains in Pi-hole safely.

Step 5 — Heat & power checks (quick, safe)
• Move the hub to open air (not inside a TV cabinet). Heat buildup can cause errors and repeated restarts.
• Plug the hub power directly into a wall outlet (no extension/power strip).
• If the adapter is unusually hot or intermittent, test a compatible known-good adapter. A weak adapter can cause a loop right when the hub checks firmware or starts the Zigbee/Z-Wave radio.

Do those two tests and watch the LED: does it keep looping or does it finally hold solid green (internet available / normal operation)?
Customer
I bypassed Pi-hole by switching router DNS to normal and moved the hub out of the cabinet. It still loops. LED goes blinking green, then magenta, then reboot. If I end up factory resetting, what’s the safest way on SmartThings v3 or Aeotec hub? I’ve heard of holding the reset button until yellow.
Technician avatar Technician
Yep — if power + network are clean and it still reboots endlessly, the next step is a controlled reset/recovery attempt. Quick warning: a factory reset can require re-adding devices (especially Zigbee/Z-Wave), so we treat it as “last resort”.

Step 6 — “Safe” factory reset (typical SmartThings v3 / Aeotec sequence)
1) Keep the hub connected via Ethernet if possible (most stable for recovery).
2) Unplug the hub power.
3) Use a paperclip to press and hold the RESET pinhole on the back.
4) While still holding RESET, plug the power back in.
5) Continue holding until the LED reaches the documented reset state (often flashing yellow then solid yellow for a few seconds).
6) Release the button and do not touch it for 10–15 minutes. The hub may cycle colors while it downloads firmware and re-initializes. Eventually it should land on a stable state (commonly solid green when online).

Step 7 — After reset: get it “claimable” in the SmartThings app
• When the hub is ready for setup, you may see patterns like red/green blinking (ready to connect) depending on model.
• Open the SmartThings app and add the hub again. Keep phone on the same network, avoid guest Wi-Fi, and ensure Bluetooth/location permissions are allowed if the app requires them.

If you tell me your exact hub model label (SmartThings v3 vs Aeotec), I can align the reset timing precisely to your LED behavior so you don’t release too early.
Customer
Mine says SmartThings on the bottom (not Aeotec). If I reset it and it comes back, will my devices reconnect automatically? Also, could the boot loop be caused by my internet blocking ports or something like double NAT?
Technician avatar Technician
Good questions — this is where most people get surprised with a SmartThings hub factory reset.

Will devices reconnect after a hub reset?
• Cloud stuff (account, locations) stays with your SmartThings account, but the hub’s radios (Zigbee/Z-Wave) often behave like a new controller after a full reset.
• Many Zigbee devices may need to be re-paired; Z-Wave devices can be more sensitive because the hub is the controller. Routines/scenes may need cleanup if devices come back as new entries.
That’s why we only reset when the hub is truly bricked or stuck in a boot loop that won’t resolve.

Yes — network edge cases can contribute (double NAT / firewall)
• If your ISP modem is also a router and your own router is behind it, you can end up with double NAT. Usually SmartThings still works, but some strict firewalls or “security gateway” setups can block outbound traffic the hub needs during boot.
• If your router has “block unknown outbound”, “country blocking”, or extremely strict firewall rules, temporarily set it to standard mode for testing.
• If you can, test the hub on a simple network path: modem/router → hub via Ethernet, no VLAN, no guest network, no heavy filtering.

Preventing future boot loops
• Keep the hub well-ventilated (overheating can show as errors and repeated restarts).
• Use a stable power source and a healthy adapter.
• Avoid isolating the hub on an IoT VLAN unless you’ve confirmed it can still reach the internet properly (DNS + outbound access).

If you’re ready, do Step 6 reset carefully. If it still returns to a boot loop even after reset, we’re likely dealing with hardware/power failure — and that changes the best next move.
Customer
I did the reset (held the pinhole until yellow, then released). It sat blinking for a while and now it’s solid green! The hub is discoverable again in the SmartThings app. I’m going to re-add devices slowly. Anything else I should do so it doesn’t get stuck on a boot loop again?
Technician avatar Technician
Perfect — solid green is what we want. Now the goal is to keep it stable while rebuilding your smart home so you don’t trigger another “hub keeps rebooting” situation.

Step 8 — Stabilize before re-adding everything
1) Leave the hub running for 30–60 minutes with Ethernet connected. If it stays solid green without random restarts, you’ve confirmed the boot loop is resolved.
2) Add devices in batches: start with 1–2 nearby Zigbee devices, then wait a few minutes. This helps the Zigbee mesh build cleanly.
3) If you use Z-Wave, add those next, but avoid trying to include 20 devices at once — stagger the process so troubleshooting is easier.
4) Keep your router simple during setup: no guest network, no device isolation, no DNS filtering for the hub until everything is stable.
5) Place the hub centrally and ventilated — avoid stacking it on top of a router or inside a hot cabinet.

If you hit a snag (stuck on blinking blue, can’t claim the hub, devices won’t pair, or the SmartThings app hangs on “updating”), open the chat and we’ll walk through the exact LED state and recovery steps with you.
Customer
Awesome. After the reset, it’s stable and no more constant restarts. I’ll keep it ventilated and avoid messing with DNS for now. Thanks for the SmartThings boot loop help!
Technician avatar Technician
Summary: For a SmartThings hub stuck on a boot loop, start with a clean power cycle and stable Ethernet/DNS. If the hub keeps rebooting (green → magenta → restart), isolate power and network, then use the pinhole reset only as a last resort (hold reset while powering on until the proper LED reset state, then wait 10–15 minutes). Once it’s back to solid green, re-add devices in batches and keep the hub cool and on a clean network path. If you’re unsure which LED pattern you’re seeing, Open the chat and an expert will guide you step by step.

Quick answer: the accepted fix

Accepted fix for SmartThings stuck on boot loop: do a true power cycle (unplug power + Ethernet, wait 2 minutes, reconnect, then wait 7–10 minutes). If it still reboots (green → magenta → restart), confirm DNS/firewall isn’t blocking the hub, try a known-good power adapter, then perform a controlled pinhole reset (hold reset while plugging power in until the LED reaches the reset state, release, and wait 10–15 minutes for recovery).


Why a SmartThings hub gets stuck in a boot loop

Most SmartThings hub boot loop cases come from unstable power, overheating, network/DNS blocking, or a firmware update stuck after an outage. A weak adapter can reset the hub mid-boot. DNS filters (Pi-hole/ad-block DNS) or strict firewalls can prevent the hub from reaching SmartThings services, causing repeated restarts. If power cut during an update, the hub may loop on startup until it completes recovery or is reset safely.

How to confirm the boot loop is really fixed

After recovery, watch the hub for at least 30 minutes. A stable hub should hold a normal LED state (commonly solid green when online). In the SmartThings app, confirm the hub shows online, and test adding a couple of Zigbee devices nearby. If the hub reboots when adding devices, revisit power (adapter/heat) and network path (Ethernet, DHCP, DNS, isolation). If the hub stays stable and devices pair consistently, the boot loop is resolved.

SmartThings boot loop — quick troubleshooting tips

Most hubs recover with clean power + stable Ethernet/DNS. Reset is last resort.

Quick path: unplug hub power + Ethernet for 2 minutes, reconnect, and wait 7–10 minutes without touching it. If it keeps restarting, bypass DNS filtering, disable isolation/guest VLAN rules, try another Ethernet cable/port, and keep the hub cool and ventilated. Only then use the reset pinhole method and allow 10–15 minutes for firmware recovery and re-initialization.

Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your SmartThings hub model, firmware version, and network setup, please consult a verified expert on Whizz-Tech 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 smart home support, techs, mechanics, vets, and more.

Expert will respond in minutes

We match you with an Expert who specialises in SmartThings hub boot loops, firmware recovery, and Zigbee/Z-Wave pairing. Talk, text, or chat — whichever you prefer.

Save time & money

Skip guesswork and avoid unnecessary resets. Fixing a SmartThings hub boot loop online can save time and prevent smart home downtime.

FAQ

Why is my SmartThings hub stuck in a boot loop?

Most boot loops are caused by unstable power, overheating, blocked internet/DNS access, or a firmware update that didn’t complete. Start with a real power cycle and network checks before doing a factory reset.

What do SmartThings hub LED colors mean during boot?

LED patterns vary by model, but green blinking often indicates booting or processing. Solid green usually indicates normal online operation. Red blinking can indicate an error (sometimes overheating). Use the LED pattern along with app status to decide the next step.

Will a factory reset delete my Zigbee and Z-Wave devices?

A full hub reset can require re-pairing devices, especially Zigbee/Z-Wave. That’s why it’s best to try power, Ethernet, DNS, and cooling steps first, and only reset if the hub can’t recover.

How long should I wait after resetting a SmartThings hub?

After a pinhole reset, wait 10–15 minutes without unplugging it. The hub may cycle LED colors while it downloads firmware and re-initializes. Interrupting it too soon can keep it stuck.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant