Archives: Troubleshooting

A robot vacuum that will not return to its dock or charge usually has one of three problems: the dock is placed where the robot cannot find or reach it, the charging contacts are dirty, or the battery is worn. Most cases are solved by dock placement and a wipe of the metal contacts.

Give the dock a reachable home

Robots find the dock by its short-range signal and by retracing their map, so placement matters more than owners expect. Manufacturers ask for clear space for a reason:

• Keep about 1.5 feet (0.5 m) clear on each side and about 4 feet (1.2 m) in front of the dock.
• Put the dock against a flat wall, not in a corner or behind a door.
• Leave it on a hard floor where possible; a thick rug at the dock makes docking alignment drift.
• Keep it in a mapped area the robot cleans, not a closed-off room.

Fix it in order

1. Wipe the charging contacts. Clean the metal pads on the dock and the matching pads on the robot with a dry cloth. A thin film of dust is the most common reason a docked robot does not charge.
2. Reseat the robot by hand. Place it on the dock manually and confirm the charge light comes on. If it charges by hand but not on its own, the problem is navigation back to the dock, not charging.
3. Power-cycle the dock. Unplug it for a minute and plug it back in. Confirm the outlet is live and any switch on the cord is on.
4. Shorten the return trip. If it runs out of charge before reaching the dock from far rooms, move the dock more central, or let it clean fewer rooms per run.
5. Re-map if the dock moved. If you relocated the dock, the robot may still drive to the old spot. Re-run mapping or setup so it learns the new location.

When the battery is the cause

Batteries wear. A robot that docks and charges normally but runs for far less time than it used to, or that will not hold a charge at all, likely needs a new battery. Battery life and replacement cost across models are covered in the ownership sections on each robot’s record in the database.

A robot vacuum that keeps getting stuck is almost always meeting the same few obstacles: high thresholds, dark or glossy floors its sensors misread, loose cords and rug tassels, or a gap just tall enough to enter but too low to exit. Fixing the environment resolves most repeat stalls.

Where robots get stuck, and why

Repeat stalls are rarely random. A robot follows a similar path each run, so it tends to fail in the same handful of spots:

• Thresholds and transitions. Most robots climb about 0.8 inch (2 cm). A saddle between rooms, or the lip of a deep-pile rug just above that height, traps them.
• Under low furniture. A sofa or bed with clearance close to the robot’s own height lets it drive in, then wedges it when the floor rises slightly or it turns.
• Dark or glossy floors. Cliff sensors can read a very dark mat or high-gloss tile as a stair edge and stop the robot, or it slips and loses its bearings.
• Cords, cables, and tassels. Loose cables and rug fringe wrap the brush or wheels and halt the drive.

Fix it in order

1. Clear the repeat-offender zones. Watch one full run and note where it stops. Tuck away cords, flip up or remove fringed rugs, and move light obstacles before each clean.
2. Block low-clearance furniture. If it wedges under one couch, add a low barrier or a no-go zone in the app so it never enters.
3. Clean the wheels and main brush. Hair and fiber wound around the brush or a wheel axle make the robot climb poorly and stall. Remove the brush and cut the wrap away.
4. Wipe the cliff sensors. Dust on the downward sensors (underside, near the front) causes false stair readings on normal dark floors. Wipe them with a dry cloth.
5. Address dark floors directly. If one dark rug always stops it, some apps let you disable cliff detection in mapped areas, or you can relocate the rug. Do not disable cliff sensors globally if you have real stairs.

When it is the robot, not the room

If the robot stalls in open, cleared floor with nothing underfoot, the cause is more likely internal: a worn wheel, a failing sensor, or a navigation fault introduced by a firmware update. A robot that used to cover the space and suddenly cannot, with no change to the room, is showing its own decline rather than a setup problem. Reliability patterns and post-update regressions for each model are recorded on the robot’s record and in the Tracker.

For the underlying question of how much a robot should handle on its own, see robot vacuum autonomy.

Most robot vacuums that will not connect to Wi-Fi are trying to join a 5 GHz network they cannot use: nearly all robot vacuums support only the 2.4 GHz band. Put your phone on the 2.4 GHz network during setup, and the connection usually completes.

Why robot vacuums are picky about Wi-Fi

Almost every consumer robot vacuum connects on 2.4 GHz only. That band travels farther and through more walls, which suits a robot that roams the floor, but many modern routers combine 2.4 GHz and 5 GHz under one network name. During setup the app hands the robot whatever band your phone is on, and if that is 5 GHz, the robot never sees a network it can join.

Fix it in order

Work through these from the top. Most vacuums are back online by step three.

1. Put your phone on 2.4 GHz. If your router uses one name for both bands, temporarily split them in the router settings, or join the band labeled “2.4G”. Then run setup again.
2. Move the dock closer to the router for setup. Pairing needs a stronger signal than daily running does. Once paired, return the dock to its normal spot.
3. Restart the robot, the dock, and the router. Power-cycle all three and wait a full minute before reconnecting.
4. Retype the password. Some robots reject networks with spaces or certain symbols in the name or password.
5. Turn off mobile data on your phone. With both Wi-Fi and cellular on, the setup app sometimes routes through cellular and cannot see the local network.
6. Reset the robot’s Wi-Fi. Most models have a button combination that clears the saved network. Check the manual for the exact one, then set up as new.

If it still will not connect

A few router settings block robots specifically:

• Band steering or “smart connect”. This pushes devices between bands automatically and confuses robots. Disable it during setup.
• Guest network or client isolation. A network that keeps devices from seeing each other stops the app and robot from pairing. Use your main network.
• MAC filtering. If your router only admits known devices, add the robot’s MAC address, printed under the dust bin or shown in the app.
• WPA3-only security. Older robots need WPA2. Set the router to WPA2, or a WPA2/WPA3 mixed mode.

When it is the robot, not your network

If other new devices join your Wi-Fi normally and the robot still fails after a Wi-Fi reset, the fault is more likely the robot’s radio or firmware. Signs that point at the robot:

• It pairs, then drops offline within minutes, repeatedly.
• The app cannot find the robot in setup mode at all, on any band.
• It connected before a firmware update and has not since.

A firmware update can change how a robot handles Wi-Fi, and a cloud-service change on the manufacturer’s side can take a model offline through no fault of yours. When either happens at scale, it is logged on the robot’s record and in the Tracker.

Wi-Fi is a convenience layer, not the cleaning itself: a robot that will not connect can usually still run a cycle from the button on the unit while you work the connection out.