You just screwed in a brand-new smart bulb, plugged in a smart plug, said the magic words — “Alexa, discover my devices” — and she cheerfully replies: “No new devices found.” The device is right there, powered on, blinking at you. Alexa just can’t see it.
This is one of the most common smart home frustrations, and the cause is almost never a broken Echo. Discovery fails in a predictable chain: the device isn’t ready, the WiFi bands don’t match, or the brand skill was never linked. Work through these 7 fixes in order — most devices get discovered by Fix #3.
Fix #1: Set the Device Up in Its Own App First (Pairing Mode On)
This is the step people skip, and it causes more failed discoveries than everything else on this list combined: Alexa cannot discover a device that isn’t already online in its own brand app.
- Install the manufacturer’s app (Kasa, Hue, Smart Life, Leviton — whatever brand you bought) and create your account.
- Add the device in that app first and connect it to your WiFi.
- Test it there — turn the bulb or plug on and off from the brand app. It must respond.
- Now check the device is in pairing/setup mode when Alexa goes looking: most bulbs blink or pulse, most plugs show a blinking LED. If the light is steady, check the manual for how to re-enter pairing mode (usually holding a button for about 5 seconds).
If the device doesn’t work in its own app, stop here and fix that first — Alexa will never find a device that isn’t online yet.
Fix #2: Put the Echo and the Device on the Same WiFi — on 2.4GHz
Almost all smart bulbs, plugs, and switches speak 2.4GHz WiFi only, while your Echo happily uses both bands and your phone probably sits on 5GHz. When everything isn’t on the same network, discovery comes back empty:
- Check which network your Echo is on: Alexa app → Devices → your Echo → gear icon → WiFi Network.
- Make sure the new device joined the same router and network name — not a guest network, which blocks devices from seeing each other.
- If your router shows separate 2.4GHz and 5GHz names, connect your phone to the 2.4GHz one during setup — a phone on 5GHz is a classic reason the brand app and Alexa both fail to find the device.
- If your router merges both bands under one name and the device still won’t appear, temporarily split the bands in your router settings, join the device to 2.4GHz, then merge them back if you prefer.
If your Echo itself keeps dropping off the network, sort that out first — our Alexa won’t connect to WiFi after a power outage guide covers the reconnect steps.
Fix #3: Enable the Brand’s Alexa Skill and Link the Account
For most brands, Alexa doesn’t talk to the device directly — she talks to the brand’s cloud through a Skill. No skill, no discovery:
- Open the Alexa app → tap More (bottom right) → Skills & Games.
- Search for the brand name of your device.
- Tap Enable to Use.
- Sign in with the same account and email you used in the brand’s own app. This matters: if the brand app account and the skill account don’t match, Alexa looks at an empty account and finds nothing.
- The skill may ask to discover devices right away — allow it, or run discovery again as in Fix #4.
Once the skill is linked, the devices already working in the brand app usually appear within one discovery scan.
Fix #4: Run Discovery Again — and Wait the Full 45 Seconds
Discovery is not instant, and cancelling early is a silent failure:
- Say “Alexa, discover my devices” — or in the app: Devices → + → Add Device → pick the device type or brand → Discover Devices.
- Wait the full 45 seconds the scan takes. Put the phone down and let it finish — backing out early stops the search midway.
- Make sure the device is powered on and still in pairing mode while the scan runs (see Fix #1 — some devices leave pairing mode after a few minutes).
- When the scan ends, check the Devices list in the app — newly found devices appear there even if the voice announcement is easy to miss.
Fix #5: Check If the Device Is Already Added — Under Another Name or Profile
Sometimes “no new devices found” simply means the device is already on your account — Alexa found it on an earlier scan and filed it under a name you don’t recognize:
- Open the Alexa app → Devices and scroll the full list, including the Lights, Plugs, and Switches groups.
- Look for generic or auto-generated names like “First light”, the brand name plus a number, or the device’s model name.
- Check you’re on the right Amazon Household profile: ask “Alexa, which profile is this?” — devices added under another household member’s profile won’t show up in yours. Switch profiles in the app or by voice and check again.
- Found it? Tap the device → gear icon → Edit Name and rename it to something you’ll actually say out loud.
Fix #6: Restart Everything — Device, Echo, Then Router
If the device is online in its app, the skill is linked, and discovery still fails, a stuck connection somewhere in the chain is likely:
- Unplug the smart device (or switch it off at the wall) for 10 seconds, plug it back in, and confirm it reconnects in its brand app.
- Unplug your Echo for 10 seconds and plug it back in — wait for the light ring to settle and Alexa to announce she’s ready.
- Restart the router: unplug it (and the modem, if separate) for a full 30 seconds, plug the modem back in first, wait 2 minutes, then the router.
- Once everything is back online, run discovery one more time (Fix #4).
Confirm your phone loads pages on the same WiFi too — if nothing is online, the problem is your internet connection, not Alexa.
Fix #7: Check Compatibility, Factory-Reset the Device, and Re-Add in Order
If nothing above worked, verify the device can actually join Alexa — and then rebuild it cleanly:
- Check the box or listing for “Works with Alexa.” Some devices are Google-only, and some Zigbee bulbs and locks need a hub — either the brand’s hub or an Echo model with a built-in smart home hub. No hub, no discovery.
- Factory-reset the device using the brand’s instructions (for many bulbs it’s a power on/off sequence; for plugs, holding the side button until the LED changes).
- Re-add it in the brand app first and confirm it works there — same rule as Fix #1.
- Make sure the skill is still enabled (Fix #3), then run discovery again.
- Still nothing? Contact the device brand’s support with your model number and firmware version — at this point it’s either a compatibility limit or a faulty device, not an Alexa setting.
Frequently Asked Questions
Why does Alexa say “No new devices found”?
Because one link in the discovery chain is broken: the device isn’t set up in its own app yet (Fix #1), it’s on a different network or band than the Echo (Fix #2), the brand’s skill was never enabled or was linked to a different account (Fix #3) — or the device is already added under a name you didn’t recognize (Fix #5). Work through them in order.
Does Alexa need 2.4GHz WiFi to discover devices?
Your Echo works on both 2.4GHz and 5GHz — but most smart bulbs, plugs, and switches are 2.4GHz only, and everything must be on the same network for setup. If your phone is on 5GHz while the device joins 2.4GHz, discovery often fails; connect the phone to 2.4GHz during setup (Fix #2).
Do I need the brand’s skill enabled for Alexa to find my device?
For most WiFi devices, yes. The skill is how Alexa connects to the brand’s cloud account where your device lives — without it, Alexa has nothing to discover. Enable it via More → Skills & Games and sign in with the same account you used in the brand’s app (Fix #3). A few devices (Matter, or Zigbee devices paired directly to an Echo with a built-in hub) are the exception.
Alexa found my device but it shows “unresponsive” — why?
Discovery worked — the connection after it is the problem. The device has usually dropped off WiFi (weak signal, or it rejoined a different band after a router restart), lost power, or the brand’s cloud is having a bad moment. Check it in the brand app first: if it’s unresponsive there too, it’s the device’s WiFi connection; if it works there, disable and re-enable the skill (Fix #3) to refresh the link.
The Bottom Line
When Alexa can’t discover a smart device, the Echo is almost never at fault — the chain is broken at the device, the network, or the skill. Set the device up in its own app first, get everything on the same 2.4GHz network, link the brand skill with the matching account, and give the scan its full 45 seconds. Follow that order and the “no new devices found” message usually disappears on the next try.