Robot Vacuum Won't Connect to Wi-Fi: The Complete Fix

1. The 2.4GHz Band — The #1 Cause

Almost every robot vacuum connects only to 2.4GHz Wi-Fi, not 5GHz. The 2.4GHz band has longer range and better penetration through walls — ideal for a low-power device roaming your floors — but most modern routers broadcast both bands under a single combined network name, and your phone may be sitting on 5GHz.

The fixes, in order of preference:

• Put your phone on 2.4GHz during setup. Many routers let you create a separate 2.4GHz network name; connect your phone to it temporarily while pairing the robot.
• Temporarily split the bands. In your router admin, give the 2.4GHz and 5GHz networks different names, complete robot setup, then (optionally) recombine.
• Temporarily disable 5GHz during setup so your phone has no choice but to use 2.4GHz.

If setup fails the instant you submit your password, the band mismatch is the most likely culprit — even when the password is correct.

2. Password and Network-Name Gotchas

Robots are pickier than phones about credentials:

• Special characters: some robots choke on certain symbols in the Wi-Fi password. If yours fails, try a temporary simpler password (letters and numbers) to confirm.
• Network name (SSID) characters: emojis or unusual characters in the network name can break pairing. Use a plain-text SSID for setup.
• Typos: re-enter the password carefully — the robot has no way to tell you it's wrong versus unreachable.
• Hidden networks: many robots can't join a hidden SSID. Un-hide it during setup.

3. Weak Signal at the Dock

The robot needs a usable signal where its dock lives, which is often a far corner, a basement, or behind furniture. Test by standing at the dock with your phone — if Wi-Fi is weak there for you, it's weak for the robot. Solutions: move the dock closer to the router during initial pairing (you can relocate it afterward, though it then needs signal at the new spot), add a mesh node or extender near the dock's area, or reposition the router. Note that some extenders create a separate network name the robot didn't pair with — make sure the robot is on a network that actually reaches the dock.

4. Router Settings That Block Robots

A few router features commonly interfere with smart devices:

• AP isolation / client isolation: if enabled, it prevents your phone and robot from seeing each other on the network. Disable it.
• MAC filtering: if you allow-list devices, add the robot's MAC address.
• WPA3-only security: some older robots only support WPA2. Set the 2.4GHz band to WPA2 or mixed WPA2/WPA3 mode.
• Too many devices / DHCP exhaustion: a full DHCP pool can refuse new devices. Reboot the router to clear stale leases.
• Captive portals / guest networks: robots can't complete a browser login, so don't put them on a guest network that requires one.

5. Phone Permissions and Bluetooth

Many robots use your phone's Bluetooth and local-network permissions during the initial handshake before the robot is on Wi-Fi. If the app's permissions are denied, pairing silently fails. In your phone settings, grant the manufacturer app: Bluetooth, Local Network, and (on Android) Location — which the OS requires for Wi-Fi scanning. Then fully close and reopen the app and retry.

6. Reset the Robot's Network and Re-Pair

If the robot was working and dropped off, or setup is stuck, do a clean network reset:

• In the app, remove/delete the robot from your account.
• On the robot, perform the Wi-Fi reset (commonly holding a specific button combination until you hear a voice prompt or see the Wi-Fi light blink — check your model's manual).
• Reboot your router and your phone.
• Re-add the robot from scratch with your phone on the 2.4GHz band.

This clears half-completed credentials that often cause persistent failures.

7. Connects but Keeps Dropping Offline

If the robot pairs but repeatedly shows offline, the issue is usually signal or roaming, not pairing. The robot drives out of good coverage mid-clean, or your mesh network hands it between nodes in a way it handles poorly. Try: relocating the dock to a stronger-signal spot, adding a mesh node to cover the cleaning area, disabling band-steering for the 2.4GHz network, or assigning the robot a static IP/DHCP reservation so it isn't bumped. Persistent drops at a specific spot in the house almost always indicate a coverage dead zone.

Frequently Asked Questions