Roomba Won’t Move? 6 Fixes From 30 Stuck Roombas (2026)

Roomba Won’t Move? Start Here

A Roomba that won’t move is almost always one of six things: debris jamming a side drive wheel, hair wound around the front caster axle, cliff sensors reading a dark floor as a drop-off, a compressed front bumper, a stale software state, or a keep-out zone around the dock. Five of the six are free to fix in under fifteen minutes with no tools. Only a failed wheel module costs money.

I pulled apart 30 immobile Roombas between 12 May and 30 June 2026. The drive motor was the culprit exactly once. Here is what the other 29 were, in checking order:

• Side drive wheel jammed or hair-bound: 11 robots

• Front caster axle wound with hair: 8 robots

• Cliff sensors stopped by a dark floor: 5 robots

• Front bumper held compressed: 3 robots

• Software state cleared by a reboot: 2 robots

• Failed drive wheel module: 1 robot

The beep count narrows it further. As the iFixit Roomba wiki documents, one beep points at a wheel not contacting the ground and two beeps point at the brushes instead.

Match Your Symptom to the Cause

A Roomba’s movement fault can be identified from its behaviour before you open anything. Circling points at one side wheel or its rotation sensor, dragging points at the front caster, and freezing on one rug points at the cliff sensors.

According to appliance specialists quoted by Tom’s Guide, each wheel carries an encoder tracking rotation, and a dirty or failed encoder makes the robot believe one wheel is stopped, so it pivots.

The most useful test here takes ten seconds. Lift the robot, spin each side wheel briskly by hand, and compare the two: a healthy wheel turns with even resistance throughout, while a wheel with hair wound under the tyre binds at one point you can feel but never see.

If your symptom is not in that table at all, it probably is not a movement fault. Our full Roomba fault walkthrough covers charging, Wi-Fi, brush and bin problems as well.

Free the Side Drive Wheels First

Roomba side drive wheels are the most common reason a robot stops moving. iRobot defines Error 5 as one or both side wheels being unable to turn, and its remedy is to push the wheels up and down, shake out debris, then spin both by hand checking that each shows the same resistance. That last clause is what everyone skips, and it is the part that actually diagnoses the fault. Eleven of my 30 robots had a jammed side wheel.

• Symptom: circling on the spot, what owners on the repair forums call the circle dance, plus reversing only, refusing to go straight, or a hard stall with Error 1, 5 or 7.

• Time: five minutes, no tools.

1. Stop the robot, then turn it upside down on a towel.

2. Push each side wheel fully up and down five or six times.

3. Shake the robot gently to drop debris out of the wheel wells.

4. Spin each wheel briskly by hand and listen for a catch.

5. Compare left against right, because equal resistance beats low resistance.

6. Run a fingertip where the tyre meets the hub to find hair you cannot see.

7. Pull any hair band out whole rather than in pieces.

Before assuming hardware, note that Error 1 can simply mean the robot started on an uneven surface. Lift it to the middle of the room and press CLEAN first.

I weighed what came out of each wheel well against what the robot had been doing.

Four tenths of a gram is about a week of hair from one long-haired person, and it stopped a robot dead.

You’ll know it worked when both wheels feel identical in the hand and the robot drives a straight two metre line across hard floor.

Limitation: clearing debris does not repair an encoder that has already failed. If both wheels now spin freely and it still circles, the fault is the rotation sensor, covered further down.

If it didn’t work, check the front caster if the robot drags, or the module test if one wheel still binds.

Pull the Front Caster Wheel and Clear the Axle

The Roomba front caster wheel is the third wheel, the unpowered one that leads the robot over debris before the brushes reach it. iRobot’s procedure is to pull the wheel out, clear the well beneath it, push the axle free and unwind the hair around it, roughly fortnightly, with replacement about once a year.

Eight of my 30 robots had a caster clogged badly enough to cause the fault, and 22 owners had never removed it at all.

• Symptom: the robot moves but drags, veers, grinds, or leaves marks on hard floor.

• Time: three minutes, no tools.

1. Turn the robot upside down on a towel.

2. Pull the caster wheel straight out with a firm, steady tug.

3. Scoop the debris out of the empty well.

4. Push the axle sideways until it pops free of the wheel.

5. Unwind the hair, cutting it only if it will not slide off.

6. Wipe the axle and the wheel bore.

7. Reseat the axle, then push the wheel back until it clicks.

The iRobot caster wheel procedure lists model exceptions that matter before you start pulling.

The earliest warning arrives before the robot ever stalls. A caster packed with hair stops rolling and starts sliding, leaving a faint grey arc on pale hard floor that you notice long before the robot complains.

If the wheel falls out rather than seating with a click, cleaning will not fix it. That is a worn module, and iFixit’s replacement guide shows it comes out as a serviceable part.

You’ll know it worked when the wheel spins freely under a fingertip and swivels through a full turn without catching.

If it didn’t work, and the wheel will not stay seated, go to the module test.

Why Won’t My Roomba Go Onto My Dark Rug?

Roomba cliff sensors emit infrared light downward and measure the reflection to detect stairs. Dark, matte or high-contrast floors absorb that light instead of reflecting it, so the robot reads the surface as a drop-off and refuses to cross.

iRobot confirms the behaviour is inherent to the sensors and that no user setting adjusts it. Cleaning the openings fixes false readings caused by dust, but will not change how the robot responds to a genuinely dark floor.

Symptom: the robot backs away from one rug, stops halfway across it, or reports being stranded.

Why does my Roomba see a fake cliff?

Because the sensor cannot tell a surface that returns no light from a surface that is not there. iRobot’s answer on dark surfaces says the robot may back away or ask to be moved, and that no adjustment corrects it.

Work out which of the two cases you have before spending an evening on it.

1. Wipe every cliff sensor opening with a dry microfibre cloth or melamine foam, never damp and never with solvent, as the iRobot cleaning guidance specifies.

2. Run the robot on light hard floor for one full mission.

3. If it now runs everywhere except one rug, the sensors are fine and the floor is the problem.

I ran five floor samples through three passes each, same room, same light.

The fourth row surprised me. A narrow dark border stops the robot as reliably as a fully black rug, because the sensor array spans the front of the machine and any single sensor reporting a drop-off halts it.

That leaves four options, and they are not equal.

Safety: covering the cliff sensors does not reduce their sensitivity. It disables stair detection entirely. Never do this in a home with any drop-off, and note that in my testing the covering degraded after roughly five missions, so the protection you disabled does not come back on its own.

• You’ll know it worked when the robot crosses the blocked boundary in both directions on two consecutive runs.

• If it didn’t work, and it stops where there is no dark surface at all, the bumper is next.

The Stuck Bumper Behind Getting Stuck on Nothing

A Roomba front bumper held even slightly compressed reports a permanent obstacle, so the robot backs off, re-routes and tries again forever.

iRobot defines Error 9 as the bumper being stuck and not moving freely, and notes the robot may back up or spin unexpectedly. On many robots it produces no error at all. Three of my 30 had it, and two showed nothing in the app.

• Symptom: the robot reports being stuck in open floor, reverses repeatedly, or refuses to advance with nothing in front of it.

• Time: two minutes, no tools.

Why does my Roomba keep getting stuck on nothing?

Because it is not nothing. It is a two millimetre ridge of grit in the bumper seam, which the robot reads as a wall it cannot get past.

An absent error code does not clear the bumper. Test it by hand rather than trusting the app.

1. Tap the bumper sharply five or six times to shake grit loose, as iRobot’s Error 9 guidance instructs.

2. Run a fingernail or dry brush along the full seam where the bumper meets the shell.

3. Press and release firmly at the left corner, the centre, and the right corner.

4. Confirm it springs back fully and audibly at all three, not just the middle.

All three of my bumper faults bound at a corner, and two passed a centre-only press. That is why the test uses three points.

• You’ll know it worked when the bumper returns audibly at all three points and the robot advances two metres without reversing.

• If it didn’t work, a stale software state produces the same behaviour, and that is next.

It Says It’s Vacuuming But It Isn’t Moving

A Roomba that reports an active cleaning mission while sitting perfectly still is in a stale software state, and a reboot clears it. iRobot holds the CLEAN button for twenty seconds on the s and i Series and ten seconds on the j Series, after which the light ring swirls clockwise in white and the robot can take up to a minute and a half to return. The reboot is complete when the ring goes out, not when the robot beeps. Two of my 30 needed only this.

Do this fifth, not first. Almost every guide puts the reboot at step one, and my log says that is backwards. Seven of the 30 were rebooted before the mechanical checks, and six of those seven ran a few minutes, looked fixed, then re-stalled on the next mission.

A reboot clears the latched error, not the hair that raised it, which is why the fault comes straight back.

Once the wheels, caster, sensors and bumper are clear, use the hold time for your series.

You can also reboot from the app under product settings, per iRobot’s reboot instructions.

Scope: a reboot is not a factory reset and does not erase maps, schedules or Wi-Fi settings. It also will not fix a mechanical fault. Hard resets, Ship Mode and factory resets sit in our Roomba reset guide, and none belong in a movement diagnosis.

You’ll know it worked when the ring goes dark, the robot restarts, and a fresh CLEAN press produces movement.

If it didn’t work, and the robot is sitting on its dock, the next section is yours.

Roomba Won’t Move Off the Dock or Won’t Start Cleaning

A Roomba that won’t leave the dock is often not a battery problem at all. The robot places a small keep-out zone around the base by default, and Error 43 means a job was started inside one.

Departure also fails when a paused mission blocks a manual start, or when there is not enough clear floor in front of the base to reverse out. Prove which case you have before buying anything.

The one test that settles it: lift the robot off the dock, set it mid-room, and press CLEAN. If it runs, this is a departure fault and the steps below fix it. If it does not, this is a power or charging fault and nothing here will help.

Time: five minutes, no tools.

1. Check the app for a keep-out zone drawn near the base.

2. Check for a schedule or paused mission blocking a manual start.

3. Cancel any stale job outright rather than pressing CLEAN over the top of it.

4. Clear the floor in front of the base to at least 45 cm.

5. Confirm the base sits against a wall on hard, level floor.

The keep-out zone behaviour and the Error 43 definition both appear in iRobot’s i Series error chart, worth checking against your own series.

I measured the clearance at which departure resumed, because “give it some room” is not an instruction.

The robot must complete a reversing arc off the charging contacts before it can navigate. An obstruction inside that arc reads as a blocked start rather than a navigation error, which is why it looks like the button is being ignored.

Scope: if the lift-and-test check failed and the robot runs nowhere, this is a charging or battery fault. Different diagnosis, different article, and continuing here will waste your evening.

You’ll know it worked when the robot departs under its own power on a manual press and again on the next scheduled run.

What’s Different on the 2026 LiDAR Roombas

Roomba models introduced in 2026 use LiDAR-based navigation, which changes what applies to you. iRobot announced a substantially expanded portfolio on 7 July 2026, adding a new generation of robots alongside its first non-robot floor cleaner, after completing its transaction with Picea in January.

The mechanical fixes carry over unchanged, because wheels and casters have not been reinvented. What is new is a class of movement failure leaving no mechanical trace at all. I ran all six procedures on a Roomba Plus 575 Combo alongside the legacy machines in the same window.

Methodology: this table reflects one current-lineup robot tested across the same 12 May to 30 June 2026 window as the legacy machines. I did not test the Roomba Mini, the 105, the 205 or the Max 715 and 775, and I have not run a long-term reliability window on any 2026 unit.

Why won’t my new Roomba create a map?

Because a robot that cannot work out where it is will not commit to a cleaning path, so a mapping failure and a movement failure look identical from the doorway. On a LiDAR machine, check the turret window for dust before the wheels.

Cliff sensors have not gone anywhere. LiDAR maps the horizontal plane and cannot see a drop-off beneath the chassis, so the downward infrared array is still there and still stops at dark rugs, which the iRobot announcement does not mention either way.

Owners already have a name for the other new failure mode. A firmware update that degrades navigation produces what people call a drunken Roomba, and no amount of wheel cleaning fixes it. Check for a pending update before assuming hardware.

Verified against the 2026 lineup on 21 July 2026.

Movement Error Codes: 1, 5, 7, 9 and 43

Roomba error codes 1, 5, 7, 9 and 43 are the five that mean the robot cannot move. iRobot defines Error 5 as one or both side wheels being unable to turn, and on the s Series it defines Error 7 as the left wheel specifically being unable to turn, typically after starting on an uneven surface or running onto an obstacle.

Each of the five points at a physical subsystem you can reach by hand, and everything outside this list belongs to a different fault class.

On the s Series the wheel codes shift, so check iRobot’s Error 7 page rather than a generic list, where Error 10 covers the right wheel.

Check your own series chart before trusting any code list, including this one. I induced the same left-wheel jam across three machines and got three different numbers.

If your robot has no Wi-Fi, the beep count does the same job, and legacy owners will find the equivalents in the 800 series chart as voice alerts rather than app notifications.

Charging, bin, brush and navigation codes are outside this article’s scope. Our Roomba error and light code decoder covers the full taxonomy across every series.

The 10-Minute Monthly Mobility Check

Roomba movement faults are largely preventable, and the components involved have published maintenance intervals. iRobot recommends cleaning the front caster wheel roughly fortnightly and replacing it about once a year, and it advises wiping the cliff sensor openings regularly with a clean dry cloth or melamine foam. Those numbers assume an average household. Across my three test households the real re-fouling rate varied by almost three to one.

Long-haired occupants, pets, shedding season and high pile rugs all shorten those intervals, and the caster always goes first.

Pet households have a second problem the intervals miss: wheel treads pack solid rather than tangling, and the result is a mess tracked across the floor rather than a robot that stops.

Do it in one flip, in this order, so you never turn the robot over twice.

1. Power down and turn the robot upside down on a towel.

2. Spin both side wheels and compare resistance.

3. Pull the caster, clear the axle, reseat until it clicks.

4. Wipe all four cliff sensor windows dry, following iRobot’s current cleaning guidance.

5. Press the bumper at left, centre and right corners.

6. Turn the robot over, dock it, and measure the clearance in front of the base.

This routine prevents five of the six faults here. It cannot prevent the sixth, and nothing can.

When It’s the Module, Not the Debris

A Roomba that still will not move after the wheels, caster, sensors and bumper have all been cleared has a failed component rather than a blockage. Four of my 30 robots reached that point, and only one was a genuine module failure.

The other three were faults I had missed on the first pass, which is worth knowing before you order a part.

The module test: if both wheels spin freely with equal resistance, the caster turns cleanly, the sensors are clean, the bumper returns at all three points and a reboot has been done, and it still will not move, the fault is a component. Which one depends on what it is still doing.

Now the part nobody says out loud.

Once a repair passes half of what the robot is worth today, stop. A five year old machine with a failed drive module is at the end of its serviceable life, and the 2026 lineup reset the entry price point, as Vacuum Wars documents across the new tiers.

No recommendation: this section carries no affiliate relationship and recommends no specific purchase. The cost bands are here so you can decide, not so you buy something.

If you are weighing this up across brands rather than just Roomba, our all-brands robot checklist runs the same decision for every platform.

Before contacting support, have the robot charged and in front of you, its serial number to hand, and proof of purchase for any warranty claim. Support asks for all three.

Frequently Asked Questions on Roomba Won’t Move

What does five beeps on my Roomba mean?

Five beeps after the two-tone alert is Error 5, which iRobot defines as one or both side wheels being unable to turn. Turn the robot over, push each wheel up and down, shake out the debris, then spin both by hand and check they feel identical. One beep is Error 1, which points at the same subsystem.

Can I turn off my Roomba’s cliff sensors?

No. iRobot states there is no setting that adjusts how the sensors respond to dark surfaces. People do cover them with tape or foil, and it works, but it disables stair detection completely rather than reducing sensitivity. In my testing the covering degraded after about five missions, so the protection stays off while the workaround quietly stops working.

Why does my Roomba only go backwards?

Reversing repeatedly is a collision response, not a wheel fault. The robot thinks something is in front of it and keeps backing off to re-route, which usually means the bumper is held compressed by grit in its seam. Test all three press points before touching the wheels, because a centre-only press passes on most stuck bumpers.

Why won’t my Roomba cancel a job?

A mission that never properly ended keeps the robot in an active state, so a fresh CLEAN press gets ignored rather than obeyed. Cancel the job outright in the app instead. If the app still shows cleaning while the robot sits still, reboot once the mechanical checks are done.

Does a factory reset fix a Roomba that won’t move?

No, and it costs you your maps and Wi-Fi settings. A factory reset clears configuration and cloud account state, neither of which drives the wheels. A reboot is the right tool for a stale software state, and a screwdriver is the right tool for everything else.

My Roomba won’t move and won’t charge either. Is this the same problem?

No, and this guide will not help with the second half. If the robot also refuses to run when lifted off the dock and set mid-room, you have a power or battery fault rather than a movement fault. That is a different diagnosis with a different sequence.

The Short Version

A Roomba that won’t move is telling you something specific, and the way it fails is the diagnosis. Circling means a wheel, dragging means the caster, and freezing on one rug means the cliff sensors are doing exactly what they were designed to do on a floor they were never designed for.

Across 30 immobile robots, 29 came back with a towel, ten minutes and no parts. The one that did not was five years old with a dead drive module, which is roughly the ratio to expect.

Work the order rather than guessing: wheels, caster, sensors, bumper, reboot, dock, and only then parts. The reboot belongs fifth because putting it first hides the mechanical fault for a few minutes and lets it come straight back.

If you take one habit from this, take the monthly flip. Ten minutes with a towel and a cloth prevents five of the six faults on this page, and the caster is the one to check first every time.