Robot Vacuum Error Codes Explained

Published: June 2026 · 7 min read

Your robot stops mid-room, flashes a light, and announces "Error 3" — and the manual is somewhere in a landfill. This guide decodes what robot vacuums are actually telling you, grouped by the real-world fault behind the number, with the fix that clears it most of the time.

First, Why the Numbers Don't Match Between Brands

If you've owned more than one robot, you've noticed the codes never line up. There's a reason for that.

Every manufacturer maintains its own error table, and the same physical problem gets a different number on a Roborock, a Dreame, an Ecovacs, and a Roomba. Worse, the numbers shift between generations of the same brand. That's why chasing "what is Error 5" without naming your model leads nowhere. The reliable move is to ignore the bare number and read the message — modern robots speak the fault out loud and spell it out in the app ("main brush stuck," "cliff sensor error," "wash tray not detected"). Once you know which subsystem is complaining, the fix is almost always the same regardless of badge. The sections below are organized that way: by the fault, not the number.

When we set up a new robot for testing, the first thing we do is trigger a few of these deliberately — lift it mid-run, drop a sock in its path, start it with the dustbin removed — just to learn how that specific model phrases each warning. It's a two-minute habit that turns a cryptic beep into a known quantity later.

Movement and Navigation Errors

The most common category by far. These keep the robot from moving the way it expects to.

"Wheel stuck" / "Lift the robot and move it"

A drive wheel can't turn freely. Nine times out of ten it's hair or carpet fiber wrapped around the axle, not an actual obstacle. Flip the robot over, press each wheel firmly — it should spring back smoothly — and pull or cut away any wrapped debris. If the robot only throws this on a specific thick rug, the wheels are sinking and slipping; that's a traction limit, not a fault.

Less obvious cause: a wheel that's clogged with dried mop water and grit so it spins unevenly. A damp cloth around the wheel housing fixes it.

"Cliff sensor error" / "Cliff sensors are dirty"

The infrared cliff sensors on the underside think there's a drop-off. Three real causes: (1) dust on the sensor windows — wipe them with a dry microfiber cloth; (2) a genuine ledge the robot got too close to — relocate it and restart; (3) very dark flooring, which absorbs the infrared and reads like empty air. If dark floors are your issue, see our guide on dark floors and cliff sensors — you can often lower cliff sensitivity or zone the area off in the app.

"Trapped" / "Move robot to a new location"

The robot has wedged itself somewhere it can't reverse out of — under a low couch, against a cluster of cables, or boxed in by chair legs. Free it, then prevent repeats with a no-go zone or a physical tidy-up of the trouble spot. Recurring entrapment in the same place is a mapping fix, not a one-time rescue; our no-go zones guide covers setting virtual walls.

"Bumper stuck" / "Tap the bumper"

The front bumper is held in a pressed position, so the robot thinks it's permanently against a wall. Usually it's compacted dust in the bumper gap or a small object jammed behind it. Tap the bumper several times to dislodge debris; if it doesn't spring back freely, clean along the seam where it meets the body.

Brush, Suction, and Bin Errors

These point at the cleaning hardware itself. They're the easiest to fix and the easiest to prevent with routine maintenance.

"Main brush stuck" / "Clean the main brush"

The brush roll can't spin against its set resistance. Pull the brush out, cut away wound hair (especially at the end caps, where it hides), and clear the housing. This is the single most common avoidable error in homes with long hair or pets. A ten-second visual check after each run prevents almost all of them — see the maintenance guide for the full routine.

"Side brush stuck"

Same cause, smaller part. Hair or a thread has bound the side brush. Unscrew or pop it off, clean the post, and check the bristles aren't so splayed they're catching on the floor. A side brush that's permanently bent flat should be replaced — they're a few dollars.

"Suction fan error" / "Low suction"

Airflow is blocked somewhere between the inlet and the motor. Check, in order: a full or improperly seated dustbin, a clogged or damp filter, and a blockage in the air channel. A filter that was washed and reinstalled while still damp is a frequent culprit — it restricts airflow enough to trip the sensor. Always dry filters a full 24 hours.

"Dustbin removed" / "Install the dustbin"

The robot can't detect the bin (or the combined bin-and-filter module). Reseat it until it clicks. If it still won't register, wipe the small contact or magnet where the bin meets the body — grime there breaks the detection. On combo robots, make sure you've reinstalled the correct module (vacuum bin vs. water tank) for the job.

Dock, Water, and Charging Errors

As docks have grown into self-emptying, mop-washing, water-refilling stations, a whole new family of errors arrived with them.

"Cannot return to dock" / "Robot can't find the base"

The robot finished cleaning but can't navigate home. Causes: the dock was moved since the map was made, something is blocking the approach path, or the dock's signal window is dusty. Keep the recommended clearance around the dock (typically 1.5 ft on each side and several feet in front), wipe the charging-signal window, and make sure the dock has stayed put. If you relocated it, let the robot remap.

"Not charging" / "Charging error"

The robot is on the dock but power isn't flowing. The usual offender is oxidized or dusty charging contacts — both the strips on the robot's underside and the pins on the dock. Wipe both with a dry cloth. Confirm the dock itself is powered (a surprising number of "dead robot" reports trace back to a switched-off outlet or a loose barrel plug). If contacts are clean and the dock has power, a battery that drains in under an hour points to aging cells rather than a charging fault.

"Clean water tank empty" / "Add water"

Self-explanatory on the surface, but it also fires when the tank is seated wrong or its float sensor is stuck. Refill, reseat firmly, and if it still complains, check the tank's water-level float moves freely. In hard-water homes, mineral scale can gum up the sensor — a periodic vinegar descale prevents it.

"Dirty water tank full" / "Wash tray error"

The dirty-water tank needs emptying, or the mop-wash tray isn't detected. Empty and rinse the dirty tank, then check the wash tray is fully clicked into place and free of hair clumps. These stations build up grime fast; a wash-tray scrub every week or two heads off most of these warnings.

"Dust bag full" / "Replace dust bag"

On auto-empty docks, the disposable bag is full or not seated. Replace it — don't try to empty and reuse a disposable bag, since the seal weakens and fine dust leaks back out. If a new bag still triggers the warning, check for a clog in the dock's suction channel; a sock or a hair clump can partially block it without fully stopping airflow.

When the Fix Is a Reset — and When It Isn't

Some errors are software hiccups. Others are hardware telling you something. Knowing the difference saves a needless support call.

If a code appears once, clears after you clean the obvious part, and never returns, it was doing its job. If the same error keeps firing in a clean machine, work up the ladder: power-cycle the robot (hold the power button until it restarts), then, if mapping or navigation is the problem, delete the saved map and let it remap from scratch. A full factory reset is the last software step before you involve the manufacturer.

Treat these as hardware signals, not reset candidates: a grinding or clicking motor when the brush is verifiably clean (failing bearings), a battery that's dropped from 150+ minutes to under an hour (degrading cells, usually a $40–80 replacement), water leaking from the chassis (a cracked tank or seal), or persistent navigation failure after clean sensors and a fresh map. For anything under warranty — most premium brands run one to two years, some three for registered products — contact support before paying out of pocket. For the broader symptom list, our troubleshooting guide walks through fixes step by step.

More Guides

Still stuck? Our troubleshooting guide covers symptoms beyond error codes, and the maintenance guide prevents most of these from ever firing.

All Guides →

Written by Daniel K. · How we test