When a robot vacuum starts spinning in circles, the cause is usually much more mundane than it looks: a dirty sensor, a jammed front caster, one drive wheel with more resistance than the other, or a confused map after the dock was moved. This is a good home fix as long as you stick to cleaning, checking free movement, and resetting whatever the manufacturer allows the user to touch. If one drive wheel doesn't respond at all, the vacuum keeps reporting a sensor fault after cleaning, or the housing has already been opened due to water, stop there.
You don't need special repair experience, but it helps to know where the cliff sensors, front caster, side brush and dock contacts are on your model. It's also useful to be able to tell a navigation problem apart from mechanical resistance: if the robot keeps searching for direction while one end keeps catching, those aren't the same thing to fix.
1 Prepare a clean space and a baseline state
Turn the robot off at the switch, take it off the dock and empty the dustbin so small debris doesn't mislead your inspection. Set it on a table or floor with good light and have a soft cloth, cotton swabs and a small brush ready. Before resetting anything to factory state, note whether the problem started after the dock was moved, after an app update, or after getting stuck under furniture — that small detail often explains the whole behavior.
2 Pin down exactly when the spinning starts
Watch whether the robot spins as soon as it leaves the dock, only when it hits a dark-colored rug, only in one room, or only after first contact with an obstacle. If it always turns the same way, suspicion immediately falls on one wheel, the front caster, or the sensor on that side. If the spinning only shows up after the map loads, the problem may be a virtual barrier, a poorly placed dock, or confused room orientation, rather than the drivetrain itself.
3 Clean the sensors and check that the wheels turn freely
Wipe the cliff sensors on the underside, the front sensor window, and the movable bumper with a dry, soft cloth and no harsh chemicals. Then remove hair and thread from the side brush shaft, the front caster, and both drive wheels. When you turn the drive wheels by hand, resistance should feel similar on both sides; if one barely moves backward or stays retracted, you already have a concrete lead, and there's no point chasing the problem through the app alone.
4 Sort out the dock and software obstacles only after the mechanical check
Put the dock back against a flat wall with enough clear space on the left, right and in front, then wipe the contacts on both the robot and the dock. In the app, temporarily remove virtual walls, no-go zones and the old map only after you've already confirmed the wheels and sensors are behaving normally. A software reset only makes sense once you're sure the robot can drive in a straight line; otherwise the fault just gets masked for one more cycle.
5 Run a short supervised pass and set a boundary
Let the robot run first on a small, flat, well-lit area free of rugs, cables and chairs, to see whether it holds a straight line and changes direction properly at an obstacle. Only afterward put it back in its normal space. If it still spins the same way, one wheel still skips, the bumper stays stuck in, or the app keeps reporting a sensor fault even though every accessible spot is clean, don't open the drive module blindly — stop at that diagnosis.
Final check
- On a flat surface the robot drives straight, doesn't constantly pull to one side, and doesn't get stuck spinning in place.
- Both drive wheels and the front caster turn evenly and freely, with no wound-up hair and no hard binding.
- The cliff sensors, bumper and dock contacts are clean, and the problem doesn't come back right after remapping or a short cycle.
- It's clear whether the cause was dirt and navigation, or the robot needs service on the drivetrain, sensors or electronics.
Common problems
- After cleaning, the robot runs normally for a few minutes, then starts spinning again.
- Most often the front caster is still partially stuck, or one drive wheel loses movement only under load. Compare the left and right resistance again instead of immediately blaming the map.
- The spinning only happens on dark rugs or very glossy tile.
- In that case the cliff sensor may be misreading the surface as a drop-off. Confirm it works properly on a light, flat surface; if it does, the problem is with floor conditions, not the drivetrain.
- After wiping and resetting, the app still reports the same sensor or the same wheel.
- That points to a fault that's no longer on the surface: a cable, a switch, an encoder or the module itself. A new mapping run won't help here — it needs service that can open up and measure the assembly.