Robot vacuum shows in the app but won’t start cleaning
Steve H.
Expert ★★★★★ 27,853 satisfied customers
Specialities: Robot vacuum app sync issues, cleaning jobs not starting, map and dock status checks, battery and sensor-related diagnostics, update-related behavior changes.
What to check first when a robot vacuum appears online but refuses to clean
Technician
Let’s check the safest things first. I don’t want you to reset maps, remove the robot from the app, or force anything that could make it harder to diagnose.
Before this started, did anything change at home — an app update, a Wi-Fi change, a moved dock, or a low-battery warning?
Technician
When you tap clean, do you hear any voice message, see any light change, or get a short error in the app? Even something small like “busy,” “positioning,” or “please check” matters here.
Technician
Common reasons are:
• the battery level is present but not high enough to begin a job
• the robot thinks it is still completing another task
• the dock position or map state changed after an update or after being moved
Trust moment: let’s avoid deleting maps or re-pairing it right away. Those steps can create extra work if the cause is only a temporary status lock.
Technician
Let’s rule out the gentle checks first:
• Is the robot showing as charging, idle, or unavailable right now?
• Does manual start from the button on the robot act the same way, or is this only from the app?
• Is “Do Not Disturb,” child lock, or a similar quiet mode turned on in the app?
Technician
Do Not Disturb can block scheduled jobs and sometimes interfere with task timing, but the dock and map detail still matters because of that “positioning” note.
I also want to ask one careful question: are the wheels, bumper, or cliff sensors visibly dusty or stuck? We are only checking, not taking the robot apart.
Technician
Let’s stay with safe checks first. I don’t want you to force-start it if a wheel or sensor is partly blocked. That can make the next error harder to read.
One more thing: after pressing clean, does it try to move even a little, or does it remain fully still on the dock?
Technician
The usual blockers are:
• battery not ready enough for a full cycle
• dock contact or charging state not clearing properly
• map or positioning confusion after the dock moved
• sensor or wheel resistance right at startup
This is common after updates, but we should rule out risks before assuming it is only software.
Technician
The most useful distinction now is this:
• if it is only the app command failing, think app sync or account state
• if the app and top button both fail, think dock, map, battery, or sensor status
You’re already giving the clues that matter.
Technician
Because the dock was moved and you had a positioning message, I would keep these as the leading possibilities:
• the robot has not re-established its dock/map reference cleanly
• startup checks are being blocked by dirty sensors or wheel drag
• the battery level is visible but not yet acceptable for the selected task
Trust moment: don’t remove it from the app yet, and don’t factory reset unless simpler checks fail. Right now this still looks diagnosable without doing anything drastic.
Quick answer: the accepted fix
Accepted first checks when a robot vacuum appears in the app but will not start cleaning: confirm whether the same refusal happens from the robot’s physical button, because that separates app sync issues from robot status issues. Review safe blockers first, including Do Not Disturb, charge level, dock position changes, and whether the robot shows “idle,” “charging,” or a brief positioning warning. Look closely for light debris around sensors, wheels, and bumper areas, since the robot can stay online while still failing its startup check. Keep testing calm and simple, and avoid map deletion or full resets until the basic status, dock, and sensor questions are ruled out.
Why a robot vacuum can look connected but still refuse to clean
A robot vacuum can stay visible in the app because the Wi-Fi link is still working, but the cleaning task may be blocked by battery rules, map confusion, dock alignment, or a safety check. This often happens after the dock is moved, after the app updates, or when the robot has dust around sensors and wheels. In that situation, the app is not the full story. The better question is whether the robot itself believes it is ready to leave the dock and begin a job.
How to tell if this is an app issue or a robot status issue
The easiest diagnostic clue is whether the top button on the robot behaves the same way as the app command. If both fail, the cause is usually inside the robot’s current state rather than the phone app. If the app fails but the top button works, the problem is more likely app sync, cloud delay, or account-side communication. Checking this first saves time and helps avoid unnecessary resets.
Robot vacuum connected in app but not cleaning — safe checks first
Start with calm checks that help separate a command problem from a startup block.
Helpful checks include looking at the exact robot status in the app, comparing app start with the top button on the robot, confirming the dock was not moved recently, and checking for dust around sensors, wheels, and bumper areas. If the robot reacts slightly and stops, that usually means the command reached it but a pre-start check failed. Avoid deleting maps or re-adding the vacuum until those simpler clues are reviewed. That keeps the problem easier to trace.
Disclaimer: This information is AI-generated and intended for general guidance only. Do not open devices or attempt unsafe electrical work. For advice specific to your Tuya/Smart Life device model and router settings, please consult a verified expert on Whizz-Tech or the manufacturer’s support before making decisions.
Getting Started Is Easy
Ask for help, 24/7
Members enjoy round-the-clock access to 12,000+ verified Experts, including Smart Life pairing help, Tuya onboarding, and router troubleshooting for device not found issues.
Expert will respond in minutes
We match you with an Expert who knows Tuya not discovering devices, EZ mode vs AP mode, iOS permissions, and 2.4 GHz Wi-Fi setup — step-by-step.
Save time & money
No guessing, no endless resets. Fixing Smart Life device not found remotely can save hours of trial-and-error with Wi-Fi, pairing modes, and permissions.
FAQ
Why did my robot vacuum stop starting cleaning all of a sudden?
This can happen after an app update, a moved dock, a battery threshold change, or a blocked sensor check. The robot may still appear online while refusing the job. A sudden change does not always mean hardware failure.
Did this happen after an update or network change?
Yes, that is common. The app can still see the vacuum while the robot itself is stuck in a state that prevents cleaning. Update-related behavior, cloud sync delays, and changed status rules can all play a part.
Is this a settings issue or a hardware problem?
It can be either, but simple status issues are more common at first. Do Not Disturb, low battery for a full task, dock position changes, or dirty sensors can stop a run. Hardware becomes more likely only after those safe checks are ruled out.
Can this be checked safely at home?
Yes. Start with the robot status in the app, compare the app command with the top button, and inspect the dock, wheels, and sensors for obvious issues. Avoid deleting maps or doing a factory reset until the basic checks are done.
Sources
- iRobot Support — Robot Status and Actions
- iRobot Support — Rebooting Your Robot: All Roomba and Braava Models
- ECOVACS Support — Cleaning did not start as scheduled
- Dreame Support — Troubleshooting Guide: Getting Your Robot Vacuum Back Online
Filed under: Robot Vacuum Mapping Navigation Issues
Related articles
- Robot vacuum returns to base and then leaves again — what is going on?
- Robot vacuum map disappeared and now it cleans like the home is new
- Smart vacuum says dust bin full even after I emptied it
- Away mode turns on even though someone is still in the house
- Thread border router looks fine, but Thread devices keep disappearing
- Matter setup code works, but the device never becomes usable
- Matter device pairs once, then disappears from the home
- Smart button lost half its actions after a firmware update — what changed?