SmartThings not discovering devices — quick fixes

Hey! We’ll fix why SmartThings is not discovering devices and get your gear to pair reliably. Discovery failures usually fall into one of these buckets: the hub is offline or on the wrong network, the device isn’t actually in pairing mode, the device is still joined to another hub, or the app is scanning the wrong way (phone Bluetooth vs hub Zigbee/Z-Wave).

Quick questions so we don’t waste time:
• What are you trying to add: Zigbee sensor/bulb, Z-Wave switch/lock, Wi-Fi device, or Matter (QR code / pairing code)?
• Which hub do you have (SmartThings v2/v3, Aeotec Smart Home Hub, SmartThings Station, or a Samsung TV/Appliance acting as a controller)?
• In the SmartThings app, are you using Add device → Scan nearby, searching by brand/model, or entering a QR/pairing code?
• What happens: “Couldn’t add device”, “No devices found”, “Scanning…” forever, or it finds it but fails at “connecting/initializing”?

Share those details and I’ll give you the fastest path to get SmartThings device discovery working again.

Got it — since it’s both Zigbee and Z-Wave, we want to check hub readiness + the “already paired somewhere else” problem.

Here are the top reasons SmartThings can’t discover new devices:
• The hub is “online” but not fully ready for pairing (needs a reboot, stuck after a firmware update, or temporarily lost its Zigbee/Z-Wave radio).
• The Z-Wave device is still joined to a previous network; in that case you must run Z-Wave exclusion before it will include again.
• The Zigbee device isn’t in true pairing mode (some sensors require a long press / battery pull / reset sequence).
• Range/interference: pairing works only when the device is very close to the hub, especially with Z-Wave locks and some Zigbee sensors.

Let’s do a quick, high-success sequence: reboot hub, then Zigbee pair close-by, then Z-Wave exclusion + include. This usually resolves “SmartThings not finding devices” without a factory reset.

Perfect — the used Z-Wave plug almost certainly needs exclusion first. But let’s start with hub readiness so discovery isn’t fighting a stale state.

Step 1 — Power-cycle the SmartThings hub (quick reset of radios)
1) Unplug the Aeotec hub power for 30 seconds.
2) Plug it back in and wait 2–3 minutes until it’s fully online in SmartThings.
3) Open SmartThings app → confirm the hub shows Online and you can open its device card without errors.

Step 2 — Add the Zigbee device the “hub way” (not phone-Bluetooth scanning)
1) SmartThings app → + → Add device.
2) If you know the brand/model, choose it. If not, use Scan nearby (this should instruct the hub to join Zigbee/Z-Wave).
3) Put the Zigbee sensor into pairing mode (usually hold the reset/pair button 5–10 seconds until LED blinks).
4) Keep the sensor within a few feet of the hub for the first pairing attempt.

If Zigbee pairs now, we know the hub is fine and the Z-Wave plug just needs proper exclusion. If Zigbee still won’t pair after reboot, we’ll check app permissions/network next.

Great diagnostic result: Zigbee pairing works, so the hub radios are alive. Now for the classic fix: Z-Wave exclusion (even if you “removed” it from the old hub, Z-Wave often needs exclusion to truly forget the network).

Step 3 — Run General Z-Wave Device Exclusion (fastest way to make used devices pair)
1) SmartThings app → open your Hub device card.
2) Tap the three dots menu → Z-Wave utilities (or “Z-Wave” section).
3) Choose Z-Wave exclusion / General device exclusion.
4) When SmartThings says it’s ready, follow the plug’s exclusion action (commonly: tap the button once, or tap 3 times quickly, or hold until LED changes).
5) Wait for the confirmation that a device was removed/excluded.

Step 4 — Include/pair the Z-Wave plug again
• Go back → Add device → choose Z-Wave plug brand/model if available, or use Scan nearby.
• Put the plug into inclusion mode (often the same button pattern as pairing).

This resolves most “SmartThings not discovering Z-Wave devices” cases in minutes.

Different category, yes — Wi-Fi/LAN devices are discovered either by cloud account linking (brand login) or local network discovery, and both can fail even when Zigbee/Z-Wave is fine.

Here’s the quick split:
• Zigbee/Z-Wave = hub radio pairing (range + pairing mode + exclusion/reset).
• Wi-Fi devices = usually vendor app + account linking (SmartThings “Works with SmartThings”), or LAN discovery requiring the phone and device to be on the same network.
• Some cameras/thermostats will never appear via “Scan nearby” and must be added by Brand (login/authorization).

Step 5 — Fast Wi-Fi device discovery checklist
1) Put your phone on the same home Wi-Fi as the device (avoid guest Wi-Fi, avoid VPN).
2) Confirm the device is on 2.4 GHz if it’s an older smart device (many cameras/thermostats don’t support 5 GHz).
3) In SmartThings → Add device → search the exact brand (Nest / Ecobee / Ring / etc.) and follow the account-link steps if prompted.
4) If it’s supposed to do local discovery: allow app permissions (Location/Nearby devices/Bluetooth depending on Android version) and make sure your router isn’t isolating clients (AP isolation).

If you tell me the thermostat/camera brand, I can point you to the correct “Add by brand vs scan” path so you’re not stuck watching “Scan nearby” forever.

Yes — “already added to another controller” is the Matter version of Z-Wave “still joined somewhere else.” It usually means the device was commissioned previously (even during a failed setup) and must be reset before SmartThings can claim it again.

Step 6 — Quick fixes for Matter QR / pairing code failures
1) Factory reset the Matter device using the manufacturer’s reset procedure (often a long button hold, or power-cycle pattern). This clears the previous commissioning data.
2) Make sure you’re using the correct SmartThings controller path: SmartThings app → Add device → Matter → scan QR / enter pairing code.
3) Keep your phone close to the device during onboarding (Bluetooth is often used to bootstrap the pairing).
4) If it’s Thread-based Matter, confirm you have a Thread Border Router / compatible controller in your ecosystem (some SmartThings setups depend on specific hubs/controllers for Thread).

If SmartThings still can’t claim it after a reset, it’s usually one of two things: the device isn’t fully reset, or the controller environment isn’t compatible for that particular Matter/Thread device. We can pinpoint which in chat if you share the device brand/model.

Totally fair — pairing should be boring, not a project. Here are the highest-impact habits to reduce “SmartThings not discovering devices” events for Zigbee, Z-Wave, and Wi-Fi gear:

Preventive setup for reliable SmartThings device discovery
• Keep the hub stable: use Ethernet if you can, or strong Wi-Fi signal if not. If the hub goes half-online, discovery often fails first.
• Pair devices close to the hub, then move them to their final location after they’re included. This is especially important for Z-Wave locks/switches and some Zigbee sensors.
• Build a mesh: add a few mains-powered Zigbee/Z-Wave repeaters (plugs/switches) so you don’t have “dead zones” that make pairing flaky.
• For used Z-Wave devices: run general exclusion before you try to include. It saves a ton of time.
• For Matter devices: if onboarding fails once, do a full reset before trying again (prevents “already added” loops).
• Keep the SmartThings app updated, and after major hub firmware updates, reboot the hub once to clear radio hiccups.

With those, most people go from “scan nearby never works” to “pairs on the first try” consistently.

Great question — here’s the fastest “don’t nuke everything” recovery sequence for SmartThings device discovery not working:

Emergency pairing recovery (in order)
1) Reboot the hub (power off 30 seconds) and wait until it’s fully online.
2) Try pairing within 3–6 feet of the hub.
3) For Z-Wave: run General device exclusion once, even for “new” devices (some are tested/paired at the factory or returned). Then include again.
4) For Zigbee: do the manufacturer’s reset (battery pull + long press) and retry pairing close to the hub.
5) For Wi-Fi devices: add by brand and relink the vendor account; verify phone is on the same network and no VPN/guest Wi-Fi is used.
6) For Matter: factory reset the device and re-scan the QR code.

When to consider a hub reset
Only if the hub repeatedly fails pairing across multiple Zigbee and Z-Wave devices even after reboots/exclusion/resets, or the hub becomes unstable/offline frequently. A full reset is effective, but it’s last resort because rebuilding devices, rooms, and automations takes time. If you want, we can diagnose whether the hub is actually the culprit before you go that far.

Summary: When SmartThings is not discovering devices, start by rebooting the hub and pairing close by. If Zigbee won’t pair, confirm true pairing mode and reset the device. If Z-Wave won’t pair (especially used gear), run general Z-Wave exclusion first, then include again. For Wi-Fi devices, add by brand/account linking and keep everything on the same network (no guest Wi-Fi/VPN). For Matter QR issues, reset the device to clear “already added to another controller.” Need help with a specific brand/model or error screen? Open the chat and we’ll fix it step by step.