WishFinds is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate, we earn from qualifying purchases.
Quick answer: In roughly 8 out of 10 cases, the problem is the 2.4GHz vs 5GHz trap: almost every robot vacuum — Roborock, iRobot, eufy included — only connects to 2.4GHz WiFi, while modern routers steer phones to 5GHz by default. Switch your phone to the 2.4GHz band (or temporarily disable 5GHz) during setup, keep the robot within 10 feet of the router, and try again. The fixes below walk through this and every other common cause, in order.
Why Robot Vacuums Are So Picky About WiFi
A robot vacuum is a low-power smart-home device, and its WiFi chip is deliberately simple: 2.4GHz only, no 5GHz support. That’s true across the major brands — Roborock’s own product notes state plainly that their robots “only support 2.4G WiFi,” and the same limitation applies to iRobot’s Braava and Roomba lines and eufy’s RoboVac series.
2.4GHz is actually the right choice for a robot: it travels farther and penetrates walls better than 5GHz, which matters for a device that roams your whole house. The problem is purely a setup-time mismatch — your phone sits on the fast 5GHz band, the robot can only see the 2.4GHz band, and the pairing handshake fails. Once you understand that, most “broken WiFi” cases resolve in minutes.
Before You Start: The 30-Second Checklist
Run through these first — they solve the majority of cases:
- Your phone is connected to the 2.4GHz network (not 5GHz, not a guest network)
- The WiFi password is correct (watch for autocorrect and trailing spaces)
- The robot is charged above 20% and within 10 feet of the router
- Bluetooth is ON on your phone (most apps use it for initial pairing)
- You’re running the latest version of the brand’s app
If it still fails, work through the nine fixes below in order.
Fix 1: Force Your Phone Onto the 2.4GHz Band
This is the fix that works most often. Many routers broadcast one network name for both bands (“band steering”), and your phone will prefer 5GHz. During robot setup, that breaks pairing.
What to do: Open your router’s admin page or app and temporarily disable the 5GHz band (or split the bands into two network names, like “Home” and “Home-5G”). Connect your phone to the 2.4GHz network, run the robot’s WiFi setup, then re-enable 5GHz afterward — the robot stays connected to 2.4GHz permanently.
On mesh systems (Eero, Google Nest, Orbi), you often can’t disable 5GHz directly. Move far from the router — 2.4GHz reaches farther, so walking to the far end of your house can force your phone onto 2.4GHz — or use the mesh app’s temporary “setup mode” if it has one.
Fix 2: Move the Robot Next to the Router
Weak signal during the initial handshake causes cryptic failures. Place the robot (and its dock, if it has one) within 10 feet of the router with a clear line of sight, then start setup. You can move it back to its permanent spot afterward — remember, when choosing how to store a robot vacuum, dock placement near the center of your home gives the best day-to-day signal.
Fix 3: Double-Check the Password (Really)
Typos cause more failures than anyone admits. WiFi passwords are case-sensitive, and phone keyboards love to autocapitalize the first letter or add a trailing space. Type it slowly, or better yet, copy it from your router’s label and paste it. Also note: some older robot firmware chokes on special characters like !, #, or & in passwords or network names — if your SSID is full of emoji or exotic characters, simplify it.
Fix 4: Disable Your VPN and Ad Blocker
VPN apps and DNS-based ad blockers (including iCloud Private Relay on iPhones) reroute your phone’s traffic in ways that break the local device-discovery step. Turn them off completely during setup, not just paused. You can re-enable them after the robot is connected.
Fix 5: Grant the App Location Permission
This one confuses everyone, but it’s legitimate: on both Android and iOS, apps need location permission to scan for nearby WiFi networks. If you denied it, the app literally cannot see your network list. Go to your phone’s settings, find the robot’s app (Roborock, iRobot Home, eufy Clean), and set location permission to “While Using the App” or “Always.”
Fix 6: Restart Everything, in the Right Order
The classic IT fix works here too — order matters:
- Unplug the router for 30 seconds, plug it back in, and wait for full boot
- Force-close the robot app on your phone and reopen it
- Power-cycle the robot (hold its power button until it shuts down, wait 10 seconds, restart)
Try setup again only after all three are fully back up. Skipping the wait is the most common way this fix “doesn’t work.”
Fix 7: Reset the Robot’s WiFi (Not the Whole Robot)
Every brand has a WiFi-only reset that clears saved network credentials without wiping your maps and settings — always try this before a factory reset:
- Roborock: Press and hold the Home and Spot Clean buttons together until you hear “Resetting WiFi”
- iRobot (Roomba/Braava): Hold Home + Spot Clean + Clean together for about 10 seconds until the light ring spins
- Eufy: Hold the Home button for 10 seconds until it beeps
After the reset, the robot broadcasts its own setup network again — connect through the app fresh.
Fix 8: Check Router Settings That Block Smart Devices
A few advanced router features silently break robot vacuums:
- AP isolation / client isolation: Prevents devices from talking to each other — disable it
- MAC address filtering: If enabled, add the robot’s MAC address (printed on its underside or in the app) to the allowed list
- WPA3-only security: Some older robot firmware only speaks WPA2 — set the router to WPA2/WPA3 mixed mode
- Hidden SSID: Temporarily unhide your network during setup
| Setting | Detail |
|---|---|
| Required band | 2.4GHz (all major brands; 5GHz unsupported) |
| Security mode | WPA2 or WPA2/WPA3 mixed (avoid WPA3-only) |
| Network type | Main network, not guest (guest networks often block device-to-device traffic) |
| Phone during setup | Same 2.4GHz network, Bluetooth on, VPN off, location permission granted |
Fix 9: Factory Reset as a Last Resort
If nothing above works, wipe the robot and start over. The method varies by brand (usually a long button hold — check your manual), and you’ll lose saved maps and schedules, so export or screenshot anything important first. After the reset, set up WiFi before restoring anything else. If a factory-reset robot still can’t see any network at all, the WiFi module itself has likely failed — contact the manufacturer’s support while under warranty.
When the Problem Isn’t Your Network
Sometimes the honest answer is that the robot is the problem. WiFi chips do die, especially after power surges. If your robot connected fine for a year and suddenly can’t see any network after a storm or outage, that’s a hardware failure, not a settings issue.
It’s also worth saying: if your current robot is old enough that its app is discontinued or its firmware can’t handle modern routers, fighting the connection may not be worth it. Current models pair in minutes and hold connections reliably. The Roborock Q5 (2700Pa suction, LiDAR navigation, 180-minute runtime) and the eufy RoboVac 11S MAX are both known for painless setup, and if your budget is tight, our roundup of vacuum deals under $200 includes connected models that won’t fight your router.
Keep the Connection Stable After Setup
- Don’t move the router after setup without checking signal at the dock — a weak signal causes “offline” errors that look like new problems
- Reserve an IP address for the robot in your router settings (DHCP reservation) to prevent address conflicts
- Update firmware when the app offers it — connectivity fixes are a common patch note
- Avoid smart plugs on the dock — cutting power randomly corrupts the robot’s network state
Models with advanced navigation tend to have the most robust connectivity stacks — it’s no coincidence that robot vacuums with LiDAR, which need constant app communication for mapping, also have the most polished WiFi implementations. The same goes for specialty use cases: robot vacuums for dark floors rely on steady app connections for their sensor calibration routines.
Frequently Asked Questions
Why won’t my robot vacuum connect to 5GHz WiFi?
It can’t — the WiFi chips in virtually all robot vacuums are 2.4GHz-only by design. Connect your phone to the 2.4GHz band during setup and the robot will pair. This is the cause of most connection failures.
My robot was connected and suddenly went offline. What happened?
Usually a router reboot assigned it a new IP address, or a firmware update glitched. Power-cycle the robot first; if that fails, reset just its WiFi (Fix 7) and reconnect. A DHCP reservation in your router prevents recurrences.
Does a robot vacuum work without WiFi?
Yes, partially. Most robots clean fine with the physical buttons, but you lose scheduling, mapping, no-go zones, room-specific cleaning, and firmware updates. The vacuum still vacuums — it’s just dumber about it.
Can I connect my robot vacuum to a guest network?
Not recommended. Guest networks typically block device-to-device communication, which breaks app control even if the robot technically joins. Use your main 2.4GHz network.
Why does the app say “incorrect password” when the password is right?
Usually you’re on the wrong band (phone on 5GHz while entering credentials for a 2.4GHz-only device), or there’s a hidden character in the SSID/password. Simplify the network name, retype the password carefully, and try Fix 1.
How far can the robot be from the router?
2.4GHz reaches well — 30 to 50 feet through walls is typical. But do the initial pairing within 10 feet, then relocate. If the dock’s permanent spot has a weak signal, consider a mesh node nearby.