Network troubleshooting technician providing live chat help

Joe B.

Reviewed for technical accuracy

Specialities: Home networking, Wi-Fi routers, smart home & IoT devices, Windows/macOS internet issues, DNS & IP configuration, ISP setup

Fix IoT devices not discoverable — smart home device not found, Alexa/Google discovery issues

Technician avatar Technician
Hi! We’ll get your IoT devices not discoverable issue sorted so your smart home shows up again. I just need a quick picture of your setup so we can target the right steps.

Which smart home platforms are you using — Alexa, Google Home, Apple HomeKit, or a mix? And what types of devices are “not found”: smart bulbs, plugs, cameras, sensors, or something else?

When you run discovery (for example “Alexa, discover devices” or “Set up device” in the Google Home app), do you get a specific message like “No new devices found” or “device not found, make sure it’s powered on and connected to the same Wi-Fi”? Finally, are your phone, hub, and the IoT devices all on the same 2.4 GHz Wi-Fi network, or do you have guest networks or multiple SSIDs?
Customer
I’m using Alexa and a few Google Nest speakers. The main problem is that my new smart plugs and a couple of smart bulbs are not discoverable. The Alexa app just keeps saying “No new devices found” and in the Google Home app I get “can’t find device”.

Everything is on the same home Wi-Fi as far as I know. Other stuff like phones and laptops are fine. I’ve installed the manufacturer apps and put the devices in pairing mode, but the hubs still can’t see them.
Technician avatar Technician
Got it, that’s a classic smart home device not discoverable situation. When Alexa can’t detect devices or the Google Home app can’t find Wi-Fi devices, it’s usually one of a few things:

• The IoT devices only support 2.4 GHz Wi-Fi, but your phone or hub is connected on 5 GHz or a different SSID.
• The devices and your phone are on a guest network or “AP isolation” mode that blocks device discovery, mDNS, or multicast traffic.
• The required cloud skill / action (for example a vendor skill in the Alexa app) isn’t linked to your account, or it needs to be disabled and re-enabled.
• Security software, VPN, ad-blockers, or router firewall settings are blocking IoT discovery requests.

We’ll first prove that everything is truly on the same LAN, then make sure the smart devices are in the right pairing mode and that your Alexa / Google Home skills are correctly linked.
Customer
The router has one Wi-Fi name for everything, but I know it supports both 2.4 and 5 GHz. My phone is definitely on that Wi-Fi. The smart plugs blink like they’re in pairing mode, and the manufacturer app often finds them, but Alexa and Google still say the IoT devices are not discoverable or “no compatible devices were found”.
Technician avatar Technician
Perfect, thanks. Many IoT discovery problems happen when the phone and device bounce between 2.4 and 5 GHz on that combined SSID, or when the device lives only in the vendor app and never gets exposed to Alexa/Google.

Step A — Confirm same 2.4 GHz network and complete vendor setup
1) On your phone, go into Wi-Fi settings and make sure you’re connected directly to your main home network, not a guest SSID or a work VPN.
2) If your router lets you, temporarily force your phone onto 2.4 GHz (some routers call this “band steering off” or let you create a separate 2.4 GHz network). Many IoT devices refuse to join if the phone is on 5 GHz during pairing.
3) In each manufacturer’s app, complete setup so that the smart plug or bulb is online and controllable there first. If the vendor app can’t control it reliably, Alexa or Google won’t either.
4) Once the device works in the vendor app, look for the “Works with Alexa” / “Works with Google Home” section and ensure your smart home accounts are linked from that side as well, not just from Alexa/Google.

After that, we’ll refresh your Alexa skills / Google Home linked services and re-run device discovery.
Customer
The plugs and bulbs work fine in their own apps; I can turn them on and off there. I also linked the Alexa skill for that brand already. Still, when I click “Discover devices” in Alexa it doesn’t find anything new. Google Home behaves the same way: the integration shows as linked but says there are no devices in the account.
Technician avatar Technician
That’s helpful — it tells us the local Wi-Fi connection is fine and we’re dealing with a cloud/account or discovery issue.

Step B — Refresh smart home skills and linked accounts
• In the Alexa app, go to Settings → Devices → your brand skill, tap it, and Disable the skill. Then re-enable it and re-link using the same login you use in the device vendor app.
• In Google Home, remove the linked service for that brand, then add it again via “Works with Google”. Make sure you pick the correct region/brand (some vendors have multiple entries for different countries).
• After relinking, immediately run “Discover devices” in Alexa or “Scan for devices”/“Sync devices” in Google Home and wait the full 45–60 seconds.
• If you also use Apple HomeKit for some devices, check that they’re added there with the correct HomeKit pairing code and that your iPhone is on the same home network.

If after this the IoT devices are still not discoverable, we’ll look at router-side issues: things like AP isolation, client isolation, VLANs, or firewall rules that block smart home discovery protocols such as mDNS and UPnP.
Customer
I disabled and re-enabled the Alexa skill and re-linked in Google Home. Still nothing. Alexa goes through the “discovering devices” screen but finds zero smart plugs. Google says “no compatible devices found in your account”. The plugs are online in the vendor app. I do see that my router has a separate guest Wi-Fi and some security options like client isolation, but I didn’t touch those before.
Technician avatar Technician
Great detail — this is almost certainly where the IoT devices not discoverable issue lives now.

Step C — Turn off isolation and allow discovery traffic
1) Log in to your router’s admin page (often something like 192.168.0.1). Under Wi-Fi settings, confirm that your IoT devices and your phone are on the same SSID, not the guest network.
2) If there’s an option like AP isolation, client isolation, “block LAN to LAN”, or “guest devices cannot see each other”, turn that off for the main network. This setting stops devices from seeing each other, which breaks smart home discovery.
3) Under firewall / advanced, allow multicast and mDNS on the LAN (sometimes called “enable IGMP snooping” or “allow streaming / smart home devices”).
4) Temporarily disable any VPN, DNS-filtering, or network-wide ad-blocker (Pi-hole, AdGuard Home, etc.) while you re-run discovery. These often block the cloud endpoints IoT devices use during pairing.
5) Once done, reboot the router, then power-cycle one of the smart plugs and ask Alexa/Google to discover devices again.

If discovery suddenly starts working for one plug after these changes, we’ll replicate the fix across all your smart home devices.
Customer
I checked and the smart plugs were on the main Wi-Fi, not guest. But “AP isolation” was enabled on the router. I turned that off, rebooted the router, then unplugged and re-plugged one smart plug. After that, Alexa finally said “1 device discovered” and it showed up as a plug. Google Home also sees that same plug now. The other plugs are still missing though.
Technician avatar Technician
Perfect — that confirms isolation was blocking discovery. Now we’re just cleaning up the remaining IoT devices that are still not discoverable.

Step D — Reset and standardize the remaining devices
• On each missing plug or bulb, put it into pairing mode again (usually by holding the power button or toggling it several times until the LED blinks rapidly).
• In the vendor app, remove the device if it’s half-added, then add it again so it shows as online and controllable. Give it a simple name like “Living Room Plug” — avoid emojis or special characters that confuse some hubs.
• Once it works locally, run “Sync devices” in Google Home or “Discover devices” in Alexa again. This time, the cloud account should push all the devices through.
• If some still don’t appear in Alexa but do in Google (or vice versa), double-check that you’re using the same third-party account in both integrations — mismatched logins are a sneaky cause of devices not found.

For stubborn devices like cameras or door locks, the vendor may require an extra step (PIN code, QR scan, or a specific smart home action), but simple plugs and bulbs should now be discoverable.
Customer
I reset the remaining plugs and bulbs and re-added them with simple names. After running discovery again, Alexa found all of them, and Google Home synced them too. The only things still missing are two older Wi-Fi bulbs from another brand — their app works, but they never show up in Alexa or Google as compatible devices.
Technician avatar Technician
Nice work — we’ve solved the main IoT devices not discoverable on Alexa/Google problem. Those two remaining bulbs are likely hitting compatibility limits.

Step E — Check compatibility, firmware, and advanced network options
• On the packaging or vendor support site, confirm those older bulbs officially support Alexa / Google Home. Some early “Wi-Fi smart bulbs” only work with their own app and never expose a smart home integration.
• Update firmware for those bulbs if the vendor app offers it — some older IoT devices need a firmware update before they become discoverable to hubs.
• If you use mesh Wi-Fi or VLANs, make sure the bulbs aren’t on a separate subnet from your Echo / Nest devices; discovery usually requires everything on the same local network segment.
• For setups using IPv6, guest VLANs, or extra firewalls, keep IoT devices and hubs on the same, simple LAN whenever possible. Advanced segmentation is great for security but often breaks discovery unless carefully configured.

If those bulbs still don’t appear after all that, it’s often easier to replace them with a fully compatible brand than to fight with unsupported integrations.
Customer
I checked the box and, sure enough, those two bulbs don’t actually list Alexa or Google support — just their own app. That explains it. I’ll probably replace them with something that works better. For now, the plugs and newer bulbs all show up and can be grouped and automated, so I’m happy.
Technician avatar Technician
That sounds like a win.

Summary: To fix IoT devices not discoverable, make sure your phone, hub, and smart devices are on the same 2.4 GHz Wi-Fi, complete setup in the vendor app first, refresh or re-link the Alexa/Google skills, then disable AP isolation and allow multicast/mDNS so discovery traffic can flow. Finally, confirm that each device is actually compatible with your smart home platform and has up-to-date firmware.

If you add more devices later and they show up as “device not found” or “no new devices discovered”, you now know where to look — and if you want someone to walk through your router and smart home settings live, you can always open a chat with an expert and we’ll go step by step with you.
Customer
Awesome. Discovery works now, routines run properly, and I understand what to check next time. Thanks for the detailed walkthrough!
Technician avatar Technician
Any time! If a friend or coworker says their smart home devices are not discoverable, Alexa can’t find devices, or their Google Home app can’t find Wi-Fi devices, you can share this checklist — and if you’d like someone to click through the router and app settings with you in real time, just start a chat with an expert and we’ll take it from there.

Quick answer: the accepted fix

Accepted fix when IoT devices are not discoverable: confirm your phone, hub, and smart devices are on the same 2.4 GHz Wi-Fi, complete setup in the vendor app, disable AP/client isolation on the router, allow multicast/mDNS traffic, refresh Alexa/Google skills, and then re-run device discovery so “device not found” errors clear for all smart home devices.

Why IoT devices stop being discoverable (Wi-Fi band, isolation, compatibility)

Most IoT devices not discoverable problems aren’t random bugs — they come from how your Wi-Fi and smart home platforms are set up. Common causes include phones and hubs on 5 GHz while smart plugs only support 2.4 GHz, guest networks that isolate devices from each other, router options like AP isolation that block local discovery traffic, or outdated skills and apps that don’t sync your devices correctly. In some cases, the device simply isn’t compatible with Alexa, Google Home, or HomeKit at all, so it will never show up in discovery.

Thinking of the path as device → vendor cloud/app → Alexa/Google/HomeKit helps. If the device isn’t stable in its own app, fix that first. If it works there but not in your smart home platform, the problem is often a skill/action link or network isolation. When everything shares the same SSID and subnet and multicast is allowed, discovery becomes far more reliable and those “device not found” messages usually disappear.

How to check whether the issue is the IoT device, the app, or your network

To quickly narrow down an IoT device not discoverable issue, use this checklist:

First, verify the device is in pairing mode and can be added and controlled in the manufacturer’s app on a phone that’s connected to your home Wi-Fi. If the vendor app can’t see it, you’re dealing with a basic Wi-Fi, password, or power problem. Next, confirm the phone, IoT device, and smart home hub (Echo, Nest, Apple TV, etc.) are all on the same 2.4 GHz network and not on a guest SSID. Finally, log into your router and check for AP isolation, client isolation, VLANs, or strict firewalls that could block mDNS/UPnP. Fixing these usually restores discovery in Alexa, Google Home, and HomeKit.

IoT devices not discoverable — quick troubleshooting tips

Confirm 2.4 GHz Wi-Fi and vendor app first, then fix discovery and isolation settings.

Fast path: make sure the IoT device is in pairing mode → connect your phone and hub to the same 2.4 GHz Wi-Fi → add and control the device in the manufacturer’s app → link or refresh the Alexa/Google/HomeKit integration → disable AP isolation and allow multicast/mDNS on the router → re-run device discovery. Keeping your network simple and using fully compatible smart home devices helps avoid recurring “device not found” and “no new devices discovered” errors.

Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your IoT brand, router model, and smart home platform, please consult a verified expert on Whizz-Tech before making decisions.

Getting Started Is Easy

Ask for help, 24/7

Members enjoy round-the-clock access to 12,000+ verified Experts for IoT devices not discoverable, Alexa not discovering devices, Google Home can’t find Wi-Fi devices, and other smart home problems.

Expert will respond in minutes

We match you with a networking and smart home specialist who knows IoT discovery protocols, 2.4 GHz vs 5 GHz Wi-Fi, and Alexa/Google/HomeKit setup for all major brands.

Save time & money

Stop factory-resetting every device and guessing at router settings. Get a clear, step-by-step IoT discovery fix in chat and get your smart home working again quickly.

FAQ

Why are my IoT devices not discoverable in Alexa or Google Home?

Most IoT devices not discoverable cases come down to network configuration. If your phone, hub, and device are not on the same 2.4 GHz Wi-Fi, if the router has AP/client isolation turned on, or if you’re using a guest network or VPN, discovery traffic can’t reach your smart home devices. Make sure the devices work in the vendor app first, then disable isolation and re-run discovery in Alexa or Google Home.

How do I fix “No new devices found” when I run discovery?

If Alexa or Google Home says “No new devices found”, start by power-cycling the IoT device and putting it back into pairing mode. Confirm it appears and works in the manufacturer’s app, then check that your router is not blocking multicast or mDNS. Finally, disable and re-enable the relevant smart home skill or linked service, and re-run discovery from the app.

Do my IoT devices have to be on 2.4 GHz Wi-Fi?

Many smart plugs, bulbs, and low-power IoT devices support 2.4 GHz Wi-Fi only. If your router uses one combined SSID for 2.4 and 5 GHz, your phone might be on 5 GHz during setup, which can cause pairing or discovery problems. Ensuring both the phone and device are on 2.4 GHz during setup often fixes device not found errors.

When should I reset my IoT device to factory settings?

If your smart home device is online in the vendor app but repeatedly fails discovery in Alexa, Google Home, or HomeKit after you’ve checked Wi-Fi, isolation, and skills, a factory reset is reasonable. Follow the manufacturer’s reset instructions (often holding a button until the LED blinks), then add the device back to the app and smart home platform from scratch.

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.