Robot Vacuum Not Mopping? Dry Pads Have Six Causes, and Five Are Settings

Why is my robot vacuum not mopping?

A robot vacuum is not mopping because one of six links in the chain between the tank and the floor has failed, and in order of likelihood those are: the run was not a mopping run at all, the mop module or pad plate was not detected, there was no water available to the pump, the water output was set so low that the pad never got properly wet, the mop lift was stuck in the raised position, or the pump itself has stopped working. The first five are things you can fix at home in a few minutes. Only the last one is a hardware fault, and it is by a wide margin the rarest.

The reason the order matters is that people start at the wrong end. The instinct on finding dry pads is to assume the pump has died and open a support ticket, when in most cases the robot simply did a vacuum run with the mop attached. Walk down the list in this order and you will usually stop at step one or two. The table gives the symptom that points at each cause, so you can jump straight to the right section.

Was it actually a mopping run?

It was probably not a mopping run, and that is the first thing to rule out, because every major app has at least three places where mopping can be switched off without you noticing. The cleaning mode on the main screen has a vacuum-only option. Each scheduled run carries its own mode, set when the schedule was created and never updated since. And room settings, in the Roborock, Dreame and Ecovacs apps in particular, can mark an individual room as vacuum-only or set its mop intensity to off, which the robot obeys even when the global mode says vacuum and mop. If any one of those three says "no", the robot drives the whole route with the pads attached and never opens the valve.

The quickest check is the run history. Open the last completed clean and read the mode line, which will say "Vacuum", "Mop", or "Vacuum and mop" on nearly every brand. If it says vacuum, you have your answer and nothing is broken. Then look at the map for that run: Dreame and Roborock shade mopped areas differently from vacuumed ones, and a map with no mop shading on a hard floor means the mop was off for that area. Our mopping guide goes through where each brand hides the per-room mop settings, since the room-level override is the one owners miss most often.

One more mode trap: carpet. A robot that has classified your whole floor as carpet will refuse to mop any of it, and some older or budget models do this when a large, dark rug confuses the carpet sensor. If the map shows carpet where there is tile, correct the floor type in the app and the mopping comes back. A home that is mostly rugs will legitimately see the pads come home dry, because the robot lifted or skipped them everywhere it went.

Is the robot detecting the mop pads?

The robot only mops when it detects that the mop module is installed, and detection is done by a magnet or a microswitch in the pad plate rather than by looking at the floor. On robots with a removable mop bracket, such as the Roomba combo models and most of the budget two-in-ones, a bracket that is not pushed fully home will not trip the switch, and the app will show the robot as vacuum-only even though pads are visibly attached. On robots with a permanent mop module and swappable pads, a pad that is misaligned on its velcro, or a plate that was snapped on crooked after washing, does the same thing.

Remove the module or plate, look at the contacts and the magnet seat for hair or grit, and reseat it until you hear it click. Then watch the app: the mop icon should change state within a few seconds of the module going on, and on most brands the robot announces "mop installed" if voice prompts are on. If the icon never changes no matter how you seat it, the detection switch has failed, which is cheap to fix under warranty but is also rare enough that you should check the rest of this list first.

Vibrating-plate robots add one more thing to check. The plate on a Dreame or Ecovacs sonic mop has to seat against its drive pin; if it is on but not engaged, the robot may read it as installed yet never vibrate, and a non-vibrating pad on a low water setting can come home looking dry even when the pump did run. Our pad types guide explains how each mechanism attaches and why the sonic ones are more sensitive to seating.

Is water actually reaching the pump?

Water reaches the pump only if the clean-water tank has water in it, the tank is seated so its outlet valve is pressed open, and the filter between the tank and the pump is not blocked, and all three fail more often than the pump itself. Start with the obvious: lift the tank out and look, because "add water" alerts are not reliable on every model and some robots will happily start a mop run with a few millimetres left. If the robot refills from a dock, check the dock's clean tank as well, since a robot with a full onboard tank that is not being topped up will mop the first room and go dry for the rest. Our self-cleaning dock guide covers the refill cycle and the dock-side faults that stop it.

The tank seat is the next one. The outlet on most onboard tanks is a spring valve that only opens when the tank is pushed fully into the robot; a tank that is in but not latched sits a millimetre short and the valve stays shut. Push it until it clicks and run the robot for thirty seconds in mop mode, then feel the pad.

Then the filter. Between the tank and the pump is a small foam or mesh filter, and if you have been using tap water in a hard-water area it will be clogged with limescale within a few months. A scaled filter looks stiff and chalky and is the single most common cause of a robot that used to mop and gradually stopped. Pull it, soak it in a one-to-one mix of white vinegar and warm water for an hour, rinse, and refit. Do the same to the spray nozzles on the underside with a cotton bud dipped in the same mix; a white crust around a nozzle hole means it is half closed. Our hot water mopping guide explains why heated docks scale faster and what water to use.

Is the water level just set too low?

The water level may simply be set too low, because the minimum setting on many robots is designed for sealed hardwood and leaves the pad barely damp on purpose. On a three-step scale, the lowest step on a Roborock or a Dreame delivers a fraction of the water of the highest, and on laminate or tile that reads as not mopping at all. The pad will have a slightly darker stripe in the centre where the nozzle sits and dry edges, which is the signature of this problem rather than of a fault.

Raise the level one step and run a single room. If the pad comes back evenly damp, you have found it, and the only remaining decision is how wet you want your floor. Owners with hardwood usually settle on the middle setting; tile and vinyl can take the top one. If you set a high water level and the pad is still dry, the setting was not the problem and you are back to the tank and filter section above. Streaky or patchy results at a sensible water level are a different fault with its own causes, covered in our streaks guide.

Dock-washed pads have a related trap. If the dock's drying cycle is set to its longest and the robot mops immediately after a wash, the pads start the run bone dry and the onboard pump has to saturate them from nothing, which on the low setting can take most of a room. Some apps let you set a pre-wet step; otherwise shorten the drying time for runs that start first thing in the morning.

Are the pads stuck in the raised position?

The pads may be stuck in the raised position, which means the robot is spraying water into pads that are being held a centimetre above the floor and never touch it. Mop lift exists so the robot can cross rugs without wetting them, and on most current models it is a small motor that raises the whole pad plate when the carpet sensor fires. Pet hair wound into that mechanism, or a pad plate refitted crooked after washing, can leave the lift jammed up. The giveaway is a gap you can see between the pad and the floor while the robot sits on a hard surface, and a pad that comes back wet in the middle but has clearly not been dragged across anything.

With the robot off, press the pad plate down with your thumb. It should drop smoothly and spring back when released. If it sticks, or you hear a crunch, lift the robot and clear hair from around the plate's hinge or the lift arms, then try again. A plate that moves freely by hand but stays up during a run points at the carpet sensor instead: a robot that thinks it is permanently on carpet keeps the pads up everywhere, and a dirty or failed sensor underneath can cause that. Our mop lift guide shows the mechanism on each brand and what the lift heights actually are.

How do I know if the pump has failed?

The pump has failed if the tank is full and properly seated, the filter and nozzles are clean, the water level is set to medium or above, and the robot is completely silent at the moment mopping starts. A working pump makes a faint ticking or whirring sound for a few seconds at the start of each mop segment and periodically through the run; hold the robot near your ear with the pads on and start a mop clean, and you will hear it on any model. Silence with everything else ruled out is as close to a diagnosis as you can get without opening the robot.

Before you call it, try two things. Run a water-pump test if the app has one, which the Dreame and Ecovacs apps hide under maintenance or device settings and which forces the pump for a few seconds. And check the app for a pump error code, since many robots log the fault even when they do not show it on screen; our error codes guide lists the water-system codes by brand. Pump failure inside the first year is a warranty job, and outside it the part is cheap on most brands and a ten-minute replacement on the ones with an accessible module. The replacement parts guide says which models make that easy and which bury the pump behind the main board.

How do I stop it happening again?

You stop dry pads happening again by fixing the water you put in the tank and by giving the mop system a monthly check, because the two causes that creep back are scale and hair. Use filtered or distilled water if your tap water is hard, or at the very least run a vinegar descale on the filter and nozzles every month or two. Clear the lift mechanism and the pad plate seat of hair each time you change pads. Keep an eye on the pad itself, since a pad that has gone stiff with detergent residue absorbs less and can look dry even when it has been sprayed; wash it in plain water or replace it. And check the mode line of a run occasionally, especially after the app updates, because a schedule that silently reverted to vacuum-only is a setting change you will otherwise only notice when the floor stops being clean.

If the robot mops but the result is poor rather than absent, that is a different problem with a different list. Dried spills that need scrubbing are a pad-pressure question, and a dock that smells is a drying question, covered in the mop smell guide. For everything else that stops a robot mid-job, the troubleshooting hub is the starting point.