Roborock Error 24 — No-go zone or barrier detected
DIRECT ANSWER
COMMON CAUSES · RANKED
Robot placed inside a no-go zone MOST COMMON
Carrying the robot into a zone you drew in the app leaves it stranded on forbidden ground.
Stale or oversized zones on the map
Old zones from a furniture layout that no longer exists can cover the robot's current position.
Robot drifted onto barrier tape UNCOMMON
A rescue or slipping wheels can drop the robot onto the tape it normally avoids.
HOW TO FIX IT
Move the robot out
Carry it a metre or more outside the no-go zone or away from the barrier tape.
Restart the clean
Start again from the app or the clean button.
Audit your zones
Open the map in the app and delete or shrink zones that no longer match your home.
RELATED FIRMWARE
S5 series (S5)
SAMPLE DATA — dataset in progressFirmware timelines are rebuilt monthly from release notes. Versions marked as sample data are community-reported and not yet verified. Full firmware timeline →
MODELS AFFECTED
| Model | Status | Firmware | Parts | Verified |
|---|---|---|---|---|
| Roborock S5 | limited | s5 | Parts → | 2026-07-05 · Source |
| Roborock S6 | limited | s6 | Parts → | 2026-07-05 · Source |
Models resolved from the series chips above. Support status comes from our EOL library; rows link to the matching parts and firmware pages.
Corrections
Spotted an error? Report a correction — fixes ship within 48h and are logged on this page.