Robot vacuum not detected on my mesh Wi-Fi — why won’t it show up?
Steve H.
Expert ★★★★★ 27,853 satisfied customers
Specialities: Robot vacuum setup issues on mesh Wi-Fi (Roomba, Roborock, Shark, eufy), vacuum not showing up in app / can’t add device, 2.4 GHz pairing problems.
When a robot vacuum can’t be found on a mesh network: what changes, and what to check first
Technician
I don’t want you doing any factory resets yet. First, quick checks that don’t erase anything:
• Is this a new setup or did it start after you changed router/mesh settings?
• Which brand of mesh do you use (eero, Deco, Orbi, Google Nest, etc.)?
• On your phone, are you connected to the same home Wi-Fi name the vacuum should use?
Technician
Most robot vacuums pair on 2.4 GHz. If your mesh uses one combined Wi-Fi name for 2.4/5, the phone may be on 5 GHz while the vacuum can only use 2.4 GHz. That mismatch can look like “not detected.”
Two gentle questions to narrow it down:
• What vacuum brand/model is it?
• During setup, does the vacuum create its own temporary Wi-Fi (sometimes a network name appears on your phone), or does it pair through Bluetooth first?
Technician
Safe check #1 (iPhone)
Make sure the Roborock app has permission for Local Network (and Location, if the app asks for it). Without that, it can’t reliably discover devices during setup, even if Wi-Fi is fine.
Safe check #2 (avoid extra blockers)
If you use a VPN or “Private Relay,” pause it just while you test. Those can interfere with discovery and make it look like the vacuum isn’t there.
After that, tell me one thing: does your mesh have an IoT network option or a “2.4 GHz only” helper for older devices?
Technician
With eero, there’s a safe feature designed for exactly this: temporarily pausing the higher bands so your phone and the vacuum can meet on 2.4 GHz. It doesn’t change your whole network permanently.
Trust moment: I don’t want you changing advanced router settings or security modes unless we have to. Let’s try the simplest discovery path first.
Before you retry setup, one more practical detail: is the vacuum and its dock close to a mesh node, or is it far away behind furniture?
Technician
Safe check #3 (placement for setup only)
For the initial pairing, place the dock/vacuum within a short distance of the nearest node (even temporarily). Once it’s set up, you can move it back and see if it stays stable.
Safe check #4 (mesh steering)
If your eero app has the “my device is 2.4 GHz only” help, use it for the setup attempt. That prevents the phone from sticking to 5 GHz when the vacuum can’t follow.
If setup still fails, we’ll look at the next common blockers: Wi-Fi security mode and guest/isolated networks.
Technician
Safe check #5 (security compatibility)
Some older Wi-Fi devices struggle with WPA3-only networks. Many mesh systems offer a mixed mode (WPA2/WPA3). You don’t have to weaken everything permanently — we’re just identifying whether security compatibility is the blocker.
Safe check #6 (guest/isolated networks)
Guest networks often isolate devices from each other. If the app needs to talk to the vacuum on your home network, guest mode can break discovery. For setup, use your main network or a dedicated IoT network that allows local device communication.
One more question: did you recently enable “device isolation,” “AP isolation,” or anything like “block local network” in your mesh settings?
Technician
Trust moment: I don’t want you to flip a bunch of security switches back and forth. Just note whether the mesh is actively blocking new devices during the pairing attempt. If it is, you’ve found a clean reason for “not detected.”
About the vacuum’s “Wi-Fi reset” step: that’s often safe because it only clears the wireless pairing info on the vacuum, not your whole account. It’s helpful if the vacuum is still trying to join an old network name, or if a previous setup attempt got stuck.
Before doing that, quick sanity check: is your Wi-Fi name or password using unusual symbols? Some devices are picky during setup.
Technician
A calmer approach is to use a dedicated network option your mesh may provide (IoT network), or the temporary 2.4 GHz helper for setup. That reduces the need to touch the main password and also avoids band steering surprises.
If you attempt the vacuum’s Wi-Fi reset, do it once, then retry setup with these conditions:
• phone has Local Network permission on
• vacuum is close to a node during pairing
• the mesh is not blocking new devices at that moment
If it still won’t appear, the next “tell” is whether the app fails at the same point every time (that can point to security mode) or at random points (often signal/roaming).
Technician
Summary logic: mesh networks can steer your phone to a different band or node during setup, and iPhone permissions can quietly block discovery. Once the device is added, the goal is stability: keep it on a strong 2.4 GHz signal near its dock, and avoid settings that block new or local devices unless you specifically allow the vacuum.
If you notice it dropping often later, we’d focus next on node placement (signal at the dock), and whether the mesh is roaming the vacuum between nodes.
Quick answer: the accepted fix
Accepted first fix when a robot vacuum won’t show up during mesh setup: (1) confirm the phone gives the app Local Network access, (2) run pairing close to a mesh node and keep the vacuum on 2.4 GHz, (3) use the mesh “2.4-only” helper (or an IoT network) to reduce band steering, and (4) check that the mesh isn’t blocking new devices during onboarding. If discovery is still inconsistent, review Wi-Fi security compatibility (WPA2/WPA3 mixed mode) and avoid guest networks that isolate devices.
Why mesh Wi-Fi can stop pairing even when the internet works
Mesh systems try to be helpful by moving devices between nodes and between 2.4 GHz and 5 GHz. During setup, that “help” can break the handshake: your phone may be on a different band than the vacuum supports, or the vacuum may attach to a weak node near the edge of coverage. Some security features can also block new devices until you allow them.
How to tell if it’s a settings issue or a vacuum hardware problem
If the vacuum is charging normally and responds to buttons, hardware is usually fine. Discovery problems are most often caused by phone permissions, band steering, weak signal at the dock, or security/guest isolation settings. If it only fails on your mesh but would pair on a simple 2.4 GHz router, that’s a strong sign the network environment is the blocker.
Robot vacuum not detected — quick troubleshooting tips
Focus on permissions, 2.4 GHz pairing, and mesh steering during setup.
Quick path: enable app Local Network access on iPhone, keep the vacuum close to a mesh node while pairing, and use a mesh “2.4-only” helper or an IoT network so your phone and vacuum meet on the same band. Avoid guest networks that isolate devices, and check whether a “block unknown devices” feature is stopping onboarding.
Disclaimer: This information is AI-generated and intended for general guidance only. Do not open devices or attempt unsafe electrical work. For advice specific to your Tuya device model, wiring, and router/mesh settings, please consult a verified expert on Whizz-Tech or the manufacturer’s support before making decisions.
Getting Started Is Easy
Ask for help, 24/7
Members enjoy round-the-clock access to 12,000+ verified Experts, including Tuya/Smart Life troubleshooting, automation conflicts, and Wi-Fi stability fixes.
Expert will respond in minutes
We match you with an Expert who understands Smart Life automations, Tuya device resets, 2.4 GHz Wi-Fi issues, and why devices go offline or turn off.
Save time & money
No guessing, no unnecessary device swaps. Fixing Tuya random shutdowns remotely can save hours of trial-and-error with scenes, timers, and Wi-Fi.
FAQ
Why did my robot vacuum stop showing up after leading a new mesh Wi-Fi?
Many vacuums pair on 2.4 GHz, while a mesh may keep your phone on 5 GHz during setup. Band steering and node selection can interrupt discovery. App permissions can also block detection on iPhone.
Did this happen because my mesh network uses one Wi-Fi name for everything?
It can. A single combined Wi-Fi name can hide which band you’re on, and some devices can’t follow the mesh’s steering. Using an IoT network or a temporary 2.4-only helper often makes setup calmer.
Is this a settings problem, or is the vacuum’s Wi-Fi hardware failing?
If the vacuum charges and responds normally, hardware is usually fine. Most “not detected” cases are permissions, weak signal at the dock, security mode compatibility, or isolation settings. Hardware issues are more likely if it fails on multiple different routers.
Can I check this safely at home without changing my whole network?
Yes. Start with app Local Network access, bring the vacuum close to a node for pairing, and use a mesh 2.4-only helper/IoT network. Avoid guest networks that isolate devices. Save bigger changes (like security mode) for later if needed.
Sources
- eero Support — Temporarily hide 5 & 6 GHz bands for 2.4 GHz device setup
- Roborock Support — Wi-Fi connection fails / robot offline in app
- iRobot Support — Switching between 2.4 GHz and 5 GHz networks
- TP-Link Deco Support — How to set up an IoT network
Filed under: Device Not Discovered Found
Related articles
- Robot vacuum not detected on mesh Wi-Fi — why won’t it show up?
- Robot vacuum not detected intermittently — why it disappears from the app
- Robot vacuum not detected after router change — why won’t it show up?
- Smart doorbell not detected on 5GHz Wi-Fi — what am I missing?
- Smart hub not detected intermittently — why does it keep disappearing?
- Streaming device not detected after router change — what to check first
- Smart hub not detected on new network — can’t find it in the app
- Smart speaker not detected after a power outage (Alexa / Google / HomePod)