Why a Robot Vacuum Will Not Connect to Wi-Fi
Nine times out of ten the robot is fine and the network is the problem. Robot vacuums use 2.4 GHz-only radios, and modern routers hide 2.4 GHz behind a single network name, steer devices onto 5 GHz, and increasingly default to WPA3. Each of those is enough on its own to make pairing fail with an error message that blames the vacuum.
This guide covers the network side. For the exact button presses on the ZCWA BR151 and the Tuya Smart app, see the app setup page. Work through this guide when those steps have been followed correctly and pairing still fails.
Why 2.4 GHz only
It looks like a cost-cutting compromise and it partly is, but the engineering reasoning is sound. A 2.4 GHz signal penetrates walls and floors far better than 5 GHz, which matters for a device that drives itself into the far corner of a house and under furniture. And a robot vacuum transmits status packets, not video: the bandwidth advantage of 5 GHz is irrelevant to it.
The result is that almost every smart plug, sensor, bulb and vacuum on the market is 2.4 GHz only, while consumer routers have spent a decade being optimised to push devices onto 5 GHz.
The eight causes, in order of likelihood
1. Band steering on a single network name
The most common cause by a wide margin. The router broadcasts one SSID for both bands and assigns each device a band. Pairing works by the phone passing the network credentials to the robot, so if the phone is on 5 GHz the robot gets details for a network it cannot detect.
Fix: in the router settings, temporarily split the bands so 2.4 GHz has its own name, connect the phone to that, pair the robot, then merge them again. The robot remembers the credentials and keeps working after the merge.
2. WPA3-only security
Newer routers ship with WPA3 enabled by default. Many 2.4 GHz IoT chipsets support WPA2 only and fail without a useful error.
Fix: set the wireless security mode to WPA2/WPA3 mixed, or WPA2-PSK (AES) on the 2.4 GHz band specifically.
3. Location permission denied on Android
Android classifies Wi-Fi scanning as a location capability. Without the permission, the pairing app cannot enumerate networks and reports a generic failure.
Fix: grant location permission to the app, and on Android 12 and later make sure it is set to precise rather than approximate.
4. The robot was left on the dock
Several models, the ZCWA BR151 among them, will not enter pairing mode while charging.
Fix: lift the robot off the dock before holding the pairing button.
5. Mesh systems and access point isolation
Mesh networks nearly always use one SSID with aggressive band steering. Separately, many routers have an isolation setting — sometimes called AP isolation or client isolation, and always on for guest networks — that prevents devices on the network from seeing each other, which blocks the handshake.
Fix: use the mesh app's IoT or 2.4 GHz onboarding mode if it has one; never pair a smart device on a guest network; check that AP isolation is off.
6. Password and character issues
Long passwords with unusual characters get mistyped or mangled. Some IoT chipsets also fail on SSIDs containing emoji, apostrophes or non-Latin characters.
Fix: retype the password carefully; if the network name contains anything unusual, rename it for the duration of setup.
7. Distance and channel congestion
2.4 GHz has three non-overlapping channels and is shared with Bluetooth, microwave ovens, baby monitors and every neighbour. A weak or congested signal at the pairing location makes the handshake time out.
Fix: pair within a few metres of the router, then move the robot back. If it then drops off in use, the dock's location is the problem, not the pairing.
8. Full DHCP pool or MAC filtering
Rare in homes but real once a household passes twenty or thirty connected devices, or where MAC address filtering was set up years ago and forgotten.
Fix: widen the DHCP range in the router settings, or add the robot's MAC address to the allow list.
Diagnostic order
| # | Check | If it fails |
|---|---|---|
| 1 | Is the phone on 2.4 GHz right now? | Split the bands and reconnect the phone |
| 2 | Is security WPA2 or WPA2/WPA3 mixed? | Change from WPA3-only |
| 3 | Does the app have location permission? | Grant it, set to precise |
| 4 | Is the robot off the dock and in pairing mode? | Lift it off, hold the button until it beeps |
| 5 | Is this the main network, not a guest network? | Switch networks; guest networks isolate clients |
| 6 | Is the robot within a few metres of the router? | Move it closer for pairing only |
| 7 | Has the router been restarted recently? | Restart it and retry once |
| 8 | Are there more than ~30 devices on the network? | Widen the DHCP pool |
After pairing: staying connected
A robot that pairs and then disconnects repeatedly is telling you about signal strength at the dock. Docks get put where they are out of the way — a hallway corner, behind a door, under a console table — which is reliably the worst reception in the room. Either move the dock somewhere with a clearer path to the router, or put a 2.4 GHz access point or mesh node within a few metres of it.
The BR151's own radio specification — 2.4 GHz only, no 5 GHz support — is listed on the specification page. One more thing worth knowing: changing the Wi-Fi password silently unpairs every smart device in the house. If several stop responding on the same day, that is usually why.
Wi-Fi FAQ
Why will my robot vacuum only connect to 2.4 GHz Wi-Fi?
Because the radio inside it is a 2.4 GHz-only chipset, which is what nearly every smart home device uses. 2.4 GHz travels further and passes through walls better than 5 GHz, and a vacuum sends a few bytes of status rather than streaming video, so the extra bandwidth of 5 GHz would buy it nothing. The chipset also costs a fraction as much.
What is band steering and why does it break setup?
Band steering is when a router publishes 2.4 GHz and 5 GHz under a single network name and decides which band each device gets. During pairing, the phone hands the robot the network it is currently on — and if the router has put the phone on 5 GHz, the robot receives credentials for a band it cannot see. Splitting the bands temporarily is the fix.
Can a robot vacuum connect to a mesh network?
Yes, once paired. The difficulty is during pairing, because mesh systems almost always use a single network name with band steering. Most mesh apps have a temporary 2.4 GHz-only or IoT-onboarding mode; enable it, pair the robot, then switch it back.
Does WPA3 stop robot vacuums connecting?
Often, yes. Many 2.4 GHz IoT chipsets support WPA2 only and fail silently against a WPA3-only network. Setting the router to WPA2/WPA3 mixed mode resolves it without weakening security for devices that do support WPA3.
Why does the robot connect and then drop off Wi-Fi later?
Almost always signal strength at the dock, since the dock is usually pushed against a wall in a corner — the worst place in the room for reception. Moving the dock, or adding a 2.4 GHz access point near it, fixes the majority of cases. A router password change also silently unpairs every smart device in the house.
Does the app need location permission?
On Android, yes. The operating system treats scanning for nearby Wi-Fi networks as a location capability, so pairing fails with an unhelpful error if the permission is denied. This catches more people than any other single setting.
Device-specific steps for the ZCWA BR151 are on the app setup page; faults that are not network-related are on the support page.
Related guides
How robot vacuums navigate: random, gyroscopic and lidar →
Why one robot crosses a room in neat parallel lines and another wanders. What each navigation type costs, and which one a given floor actually needs.
Choosing a robot vacuum for pet hair →
The roller brush is the part that fails in a home with animals. What to look at instead of suction figures, and the maintenance a pet home really involves.
Robot mopping on hard floors: what it can and cannot do →
A robot mop wipes; it does not scrub. The difference between gravity pads and metered tanks, which floors are safe, and why water flow is the fault people report most.