Smart home technician helping fix TP-Link Deco device discovery issues

Steve H.

Expert ★★★★★ 27,853 satisfied customers

Specialities: TP-Link Deco mesh, 2.4 GHz IoT devices, Deco app troubleshooting, DHCP/IP reservations, mDNS/Bonjour discovery, guest network & isolation, router vs AP mode, firmware updates

Deco app not showing devices / TP-Link Deco not detecting devices — Wi-Fi band, app, and network discovery fixes

Technician avatar Technician
Hey! Let’s fix why your TP-Link Deco is not discovering devices — whether that means the Deco app not showing connected devices, a new device not showing up after you connect it, or your phone can’t find smart devices (Chromecast/AirPlay/printers) on the mesh.

Quick questions so we target the right “discovery” type (there are a few):
• Which Deco model(s) (M4/M5/M9, X20/X55/X60, XE75, BE-series) and is it in Router Mode or Access Point (AP) Mode?
• What’s not being discovered: (A) devices missing in the Deco app list, (B) your phone can’t find devices during setup (IoT pairing), or (C) devices can connect but services like AirPlay/Chromecast/Bonjour printer discovery don’t show up?
• Are the “missing” devices on Main Wi-Fi, Guest Wi-Fi, or an IoT Network? (Some Decos have a dedicated IoT SSID.)
• Any recent changes: firmware update, enabling Fast Roaming / Beamforming / Mesh Technology, changing Wi-Fi name, security (WPA2/WPA3), or using a VPN on your phone?

With those, we can stop the “Deco not detecting devices” issue instead of doing random resets.
Customer
I have a Deco mesh (X55). Internet works, but the Deco app isn’t showing connected devices. Also, when I try to add some 2.4GHz smart devices they sometimes connect to Wi-Fi but then they don’t appear properly, like the Deco not discovering devices at all. It started after I updated the Deco firmware.
Technician avatar Technician
Got it — that’s a very common combo after updates: Deco app device list missing + IoT devices not showing / not being discovered reliably.

Here are the usual causes when Deco “can’t discover” devices:
• The phone isn’t managing the mesh locally (VPN/mobile data interfering) → the app can act like it can’t “see” clients on the LAN.
• Smart devices that are 2.4 GHz only get tripped up by band steering (same SSID for 2.4/5) or WPA3/mixed security → setup completes but the device doesn’t stay reachable.
• Features like Fast Roaming, Beamforming, or Mesh Technology can be great for phones/laptops but can break older IoT onboarding or make a device “bounce” between nodes during setup.
• If your issue is service discovery (AirPlay/Chromecast/printer), that’s often mDNS/Bonjour behavior + isolation settings (Guest/IoT) rather than the device being offline.

We’ll fix it in a clean order: app/local access → stable 2.4 GHz onboarding → then discovery services.
Customer
I think I’m in Router Mode. My phone is on the main Wi-Fi. The main issue is the app shows almost nothing in the device list, like the Deco app not showing devices, but the TVs and phones are online. Also my printer and Chromecast are sometimes not discoverable from my phone.
Technician avatar Technician
Perfect — first we fix the “app can’t see clients” layer, because if the Deco device list is missing, it becomes hard to troubleshoot anything else.

Step 1 — Make sure the Deco app can manage locally
1) Connect your phone to the Deco main Wi-Fi (not Guest, not IoT).
2) Temporarily turn OFF VPN and OFF “Private Relay” (iOS) / any DNS/VPN apps. Also toggle mobile data off just for the test.
3) Ensure the Deco app has Local Network permission (iOS: Settings → Deco → Local Network ON). On Android: allow Nearby devices / network permissions if prompted.
4) Fully close the Deco app (swipe it away), reopen it, and pull to refresh the client list.

Step 2 — Reboot in the right order (quick but important)
• Reboot the main Deco first (the one connected to the modem). Wait until LED is stable.
• Then reboot your phone (sounds basic, but it clears stale discovery caches).

This resolves a lot of “TP-Link Deco not detecting devices in the app” cases immediately. If it’s still blank, we’ll do a clean app-side reset without touching your Wi-Fi settings.
Customer
I turned off VPN and mobile data, and gave the app local network permission. After rebooting the main Deco, the app showed some devices, but not all. A few devices are still missing. Also the printer is connected but AirPrint/printing discovery is unreliable.
Technician avatar Technician
Nice — progress. When the Deco app shows some devices but not all, it’s usually one of these: the app cache is stale, devices are being identified oddly, or something is blocking/isolating them.

Step 3 — Quick checks inside Deco (no factory reset)
1) In Deco app → More → check Block List. Make sure none of the “missing” MAC addresses/devices are blocked (sometimes happens after an update or profile change).
2) Go to Network (or Clients) → use search by device name/MAC if available. Some devices show up as “Generic” or under a different icon.
3) For key devices (printer, Chromecast, smart hubs), set IP Address Reservation so they keep the same local IP. Why: discovery and casting often breaks when the device gets a new IP after a DHCP renewal.

Step 4 — Confirm which SSID they’re on
If the printer or Chromecast is on Guest Wi-Fi or a separate IoT Network, your phone on Main Wi-Fi may not discover it (by design). For discovery features like AirPrint, Bonjour, Chromecast, keep phone + target device on the same network segment unless you’ve set up cross-network discovery (most homes haven’t).

After this, tell me: are your printer/Chromecast on Main, Guest, or IoT SSID?
Customer
The printer was actually on Guest Wi-Fi because I used it for visitors. Chromecast is on the main Wi-Fi. I moved the printer to the main Wi-Fi and it helped a bit, but my phone still sometimes can’t discover it. Also some 2.4GHz smart plugs fail during setup — the Deco app or their app just can’t find them.
Technician avatar Technician
That explains a lot. Guest networks commonly block local discovery, and the IoT onboarding issue is usually band/security related.

Step 5 — Fix “IoT device not discovered” on Deco (2.4 GHz onboarding)
Most smart plugs/bulbs/cameras are 2.4 GHz only. If your phone is on 5 GHz during setup, pairing can fail even if the SSID name looks identical.

Do this for the cleanest setup:
1) In Deco app → Wi-Fi settings: enable a dedicated IoT Network (if your model supports it) and set it to 2.4 GHz only with a simple SSID like Home_IoT_2G.
2) Security: use WPA2-PSK (AES) for the IoT SSID. Avoid WPA3-only during onboarding (many IoT devices can’t handle it).
3) Connect your phone to Home_IoT_2G during setup. Then add the smart plug in its own app (Kasa/Tapo/Smart Life/etc.).
4) If setup fails with “device not found,” factory reset the plug and retry near the main Deco (reduces roaming during setup).

Related keywords you’ll see that match your symptoms: Deco not detecting IoT devices, smart plugs not connecting to Deco 2.4GHz, Deco mesh not discovering devices during setup.

Once the plug is connected and stable, you can move it back to its room; it should roam normally on the mesh.
Customer
I do have an IoT Network option. I didn’t know it should be 2.4 only. Another question: my Chromecast and some speakers are connected, but sometimes casting doesn’t find them. Is that still “Deco not discovering devices” or something else?
Technician avatar Technician
Great question — yes, it’s still “device discovery,” but it’s specifically service discovery (mDNS/Bonjour/SSDP) rather than Wi-Fi association.

Step 6 — Fix “can’t find Chromecast / AirPlay / printer” on Deco
1) Keep phone + casting target on the same SSID (Main to Main, or IoT to IoT). Guest often blocks discovery by design.
2) Reboot the casting device (Chromecast/speaker) and the phone. Casting apps cache discovery results; stale caches look like “not found.”
3) In Deco app → More → Advanced (names vary): temporarily disable Fast Roaming and Beamforming for testing. Some older discovery implementations get flaky when clients roam aggressively between nodes.
4) If you use AP Mode behind another router, double-check you’re not accidentally on two different subnets (double NAT / separate LANs). Discovery protocols don’t cross subnets unless specifically configured.

If this step improves casting immediately, we’ll turn features back on one-by-one to find the exact setting that triggers “Deco not discovering devices” behavior on your network.
Customer
After moving printer to Main and setting the IoT network as 2.4-only, my smart plugs connect more reliably. Casting improved when I turned off Fast Roaming. But I don’t want to break performance. Is there a best-practice setup so my devices stay discoverable?
Technician avatar Technician
Absolutely — the goal is: fast Wi-Fi for phones/laptops and stable discovery for smart devices.

Best-practice setup for “TP-Link Deco not discovering devices” problems
• Use a dedicated IoT SSID (2.4 GHz only) for smart plugs, bulbs, older cameras. Keep it WPA2-PSK (AES) and don’t change its name/password often.
• Keep discovery-heavy devices (Chromecast, AirPlay speakers, printers) on the Main network with your phone. Avoid Guest for anything you need to “see” locally.
• Reserve IPs for: printer, Chromecast/speakers, smart hubs/bridges. It reduces “sometimes missing” discovery caused by DHCP changes.
• If Fast Roaming causes “disappearing” casting, leave it OFF (or keep it ON only if your environment truly needs it). In many homes, the speed difference is minor, but stability gains are big.
• After firmware updates, reboot the main Deco once. Updates can refresh rules and temporarily disrupt local discovery caches.

These steps address the most searched variants: Deco mesh not seeing devices, Deco app not detecting devices, TP-Link Deco device discovery not working, and new device not showing in Deco.
Customer
What if the Deco app itself says it can’t find the Deco network or it acts like I need to set it up again, even though Wi-Fi works?
Technician avatar Technician
That’s the “management discovery” case — different from client discovery — and it’s usually phone/app routing, not your mesh failing.

Step 7 — Fix “Deco app could not find Deco / cannot find Deco network”
• Make sure your phone is connected to the Deco Wi-Fi (Main SSID).
• Turn off VPN, disable mobile data temporarily, and reopen the app (this forces local management instead of trying a remote path).
• If you recently changed phone OS permissions, re-check Local Network permission on iOS or network permissions on Android.
• Reboot the main Deco (not every node, just main first).

If the app still loops, the next safe step is to log out/in inside the Deco app or reinstall the app. That refreshes local discovery without changing your Wi-Fi name or kicking devices off the mesh.
Customer
This helped a lot. The device list is mostly back, the IoT stuff connects on the IoT SSID, and casting is stable with Fast Roaming off. So the main fix was separating IoT and avoiding Guest for devices I want to discover.
Technician avatar Technician
Love the outcome. Summary: when TP-Link Deco is not discovering devices, separate the problem into (1) the Deco app not showing devices (local management permissions/VPN/app cache), (2) IoT devices not found (use a 2.4 GHz-only IoT SSID + WPA2), and (3) casting/printing discovery (keep devices on the same SSID; avoid Guest isolation; consider disabling Fast Roaming if it breaks discovery). If you want, open the chat and we’ll tune the exact Deco settings for your model so you keep performance and reliable discovery.

Quick answer: the accepted fix

Accepted fix when TP-Link Deco is not discovering devices: ensure your phone can manage Deco locally (Local Network permission, VPN/mobile data off), reboot the main Deco, then use a 2.4 GHz-only IoT Network (WPA2) for smart plugs/bulbs. Keep printers/Chromecast/AirPlay targets on the Main SSID (not Guest), and add IP reservations for discovery-heavy devices.

Why Deco can’t discover devices (and why it gets worse after updates)

Most “Deco not detecting devices” reports come from a few predictable changes: firmware updates can refresh roaming/steering rules, the phone loses local network permissions, or IoT onboarding breaks due to band steering and security changes (WPA3/mixed modes). Another frequent cause is network isolation: devices placed on Guest Wi-Fi or an isolated IoT Network may be connected yet not discoverable via mDNS/Bonjour (AirPrint/AirPlay) or casting protocols. Finally, if a device’s IP changes often, it can “disappear” from apps that expect it at the old address — that’s why DHCP reservation helps.

How to confirm device discovery is truly fixed on a Deco mesh

Test in three ways: (1) check the Deco app device list updates correctly (devices show online/offline accurately), (2) add a 2.4 GHz smart device on the IoT SSID without failures, and (3) verify local discovery works (AirPrint printer appears, Chromecast shows in casting list, speakers show in AirPlay). If discovery works only sometimes, set an IP reservation for the printer/Chromecast and consider leaving Fast Roaming off if it causes intermittent “not found” behavior.

TP-Link Deco not discovering devices — quick troubleshooting tips

Most cases are fixed by local app access + a clean 2.4 GHz IoT network + avoiding Guest isolation for discoverable devices.

Quick path: disable VPN, confirm Deco app Local Network permission, reboot the main Deco, then use a 2.4 GHz-only IoT Network (WPA2) for IoT pairing. Keep printers/casting devices on the Main SSID, not Guest. Add IP reservations for printer/Chromecast/speakers and test discovery again. If casting/printing is still flaky, try toggling Fast Roaming and Beamforming to find the setting that breaks discovery on your setup.

Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your Deco model, firmware, and device mix, 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 TP-Link Deco, mesh Wi-Fi, and device discovery issues. Talk, text, or chat — whichever you prefer.

Save time & money

No scheduling hassles or expensive home visits. Fixing Deco mesh discovery issues online can save you time and money.

FAQ

Why is the Deco app not showing connected devices even though the internet works?

This usually happens when the phone can’t manage the network locally (VPN/mobile data routing, missing Local Network permission) or the Deco app cache is stale after an update. Connect to the main Deco Wi-Fi, turn off VPN, confirm Local Network permission, and reboot the main Deco to refresh the client list.

Why do 2.4 GHz smart devices fail to be discovered on TP-Link Deco during setup?

Many IoT devices are 2.4 GHz-only and can fail onboarding when the phone is on 5 GHz, when WPA3/mixed security is used, or when roaming/steering features interfere. Use a 2.4 GHz-only IoT SSID (WPA2-PSK AES), connect your phone to it during setup, and pair the device near the main Deco.

Why can’t my phone discover Chromecast/AirPlay/printers on a Deco mesh?

Casting and printing rely on local discovery protocols (mDNS/Bonjour/SSDP). If devices are on Guest or an isolated IoT network, discovery may be blocked even though the device is online. Keep phone and target device on the same SSID and consider IP reservations for printers/speakers/Chromecast.

Should I disable Fast Roaming or Beamforming to fix “Deco not discovering devices”?

For some networks, yes — especially if discovery is intermittent while roaming between nodes. Try disabling Fast Roaming (and optionally Beamforming) to test stability. If discovery becomes reliable, keep the setting off or re-enable features one-by-one to find the exact trigger.

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.