When a Saros 20 Sonic cannot find its dock, first separate localization from charging. Roborock says return can fail if the robot was started somewhere else, hit an obstacle, or was moved manually. Place the dock against a wall with about 0.5 m clearance on each side and 1.5 m in front, then clean the dock’s front signal-transmission area and the robot’s front sensor. A direct return test from the same mapped floor is the clean proof.
Can the robot return when started close to the dock?
Confirm the exact model and exact code, light pattern or symptom.
Run the lowest-risk physical or software check first.
Use each pass condition to decide what the result actually narrows down.
Does this match your problem?
- The robot cleans but wanders instead of returning to the dock.
- The Saros 20 Sonic was started away from its normal mapped position or moved manually.
- The robot reaches the general dock area inconsistently.
- You are diagnosing can't find dock on a Roborock Saros 20 Sonic and want the exact model support path rather than a generic reset list.
Most likely causes
The robot lost its localization reference after being moved
Obstacles or poor clearance around the dock
Dirty signal-transmission or front-sensor surfaces
A robot that reaches the dock but fails to charge has already passed the dock-location test; move to charging-contact diagnosis instead of repeating navigation resets.
What your test result means
| What you observe | What it narrows down | Next move |
|---|---|---|
| Robot was carried or started in a different location | Map localization may be inconsistent | Start a normal cleanup from a recognized mapped area before testing return. |
| Dock clearance is blocked | Final approach geometry is compromised | Restore 0.5 m side and 1.5 m front clearance. |
| Dock signal area or front robot sensor is dirty | Base-location sensing may be degraded | Clean both areas and retest. |
| Robot reaches dock but does not charge | Dock finding succeeded; charging is the separate problem | Switch to Error 13/charging diagnostics. |
| Robot still cannot locate dock in a clear mapped setup | Owner return checks are exhausted | Escalate with map and return-attempt video. |
Do not factory-reset by default. Use the exact model’s reboot/network-reset procedure only when the manufacturer path calls for it.
Run these checks in order
Separate “cannot find dock” from “reaches dock but will not charge”
Watch one return attempt. If the Saros 20 Sonic reaches and seats on the station, autonomous homing succeeded and any later charging problem belongs to Error 13/charging. Stay on this guide only when it cannot locate or approach the dock reliably.
Run a mapped return without carrying the robot
Roborock lists a different start position and manual relocation as causes of return trouble. Start from a normal mapped location, remove temporary obstacles and let the robot attempt the return without being picked up.
Restore the documented dock approach zone
Place the dock against a wall with roughly 0.5 m clear on each side and 1.5 m in front. Remove cords, bins and furniture that encroach on the final approach. Keep the dock fixed during the next tests.
Clean both sides of the homing signal path
Wipe the dock’s front signal-transmission area and the robot’s front sensor, both of which Roborock identifies for locating the base. This is different from cleaning charging contacts after the robot has already arrived.
Run a nearby return, then a normal mission return
First command Return to Dock from a short distance on the same mapped floor. If that works, start a short cleaning task from the dock and let the robot return automatically. The comparison separates final homing from broader route/localization context.
Try one deliberate dock relocation only after the clean test fails
Roborock also suggests a new dock location when return still fails. Move it once to a clear wall-backed position with the same clearance, then repeat without carrying the robot. If failure persists, preserve the map and video for support instead of repeatedly moving the station.
Escalate when the Saros 20 Sonic still cannot locate the dock from a recognized mapped area after the approach zone is clear, the dock signal area and robot front sensor are clean, and one controlled dock-position test has failed. Send the saved map plus a video showing the robot’s final approach. If it reaches the dock but will not charge, switch to the charging/Error 13 path instead.
What to collect before contacting support
Give support a reproducible case instead of “it doesn’t work.” That reduces repeated basic troubleshooting and preserves the clues from your tests.
- Exact model name and the error code / voice prompt exactly as shown
- A photo or screenshot of the app error and the time it occurred
- A short list of the checks already completed and what happened after each one
- Firmware/app version if the issue began after a software change
Manufacturer evidence
Roborock Saros 20 Sonic troubleshooting — cannot find dock
The current Saros 20 Sonic support page covers dock clearance, moved-robot behavior and cleaning the dock/robot homing signal surfaces. This review separates finding the dock from charging on it, using the Saros 20 Sonic clearance, signal-area and front-sensor checks before any charging-path troubleshooting.
Additional official source: Roborock Support Center — Help & Manuals ↗Last editorial review: September 5, 2026Regional note: manufacturer help centers, model suffixes, mains-power requirements and warranty procedures can differ by country. If the source redirects to a local support site, confirm that the model/hardware scope still matches before following a region-sensitive step.
Official model support means the manufacturer page explicitly covers this model. Official series support means the manufacturer explicitly groups the model with a documented series path. Official manual means the diagnostic comes from the exact-model owner manual. Manufacturer-general means the source is an official brand-wide troubleshooting path and the page avoids presenting it as model-exclusive.
FAQ
Can carrying the robot confuse dock return?
Yes. Roborock lists starting the robot somewhere else or moving it manually as conditions that can interfere with dock finding. For a clean test, start from a recognized location on the saved map and let the Saros 20 Sonic travel back without being carried. If that works, the earlier failure was likely tied to localization rather than the charging system.
Should I move the dock first?
Not as the first move. First restore the documented approach clearance, clean the dock signal area and robot front sensor, and run a return test from the existing mapped setup. If return still fails, move the dock once to a clear wall-backed location and repeat. Repeatedly relocating it makes the test harder to interpret because the map reference keeps changing.
How much clear space should I leave around the dock?
For this Saros 20 Sonic troubleshooting path, Roborock specifies roughly 0.5 m of clear space on each side of the dock and 1.5 m in front. Keep cords, bins and furniture out of that final approach. After restoring the clearance, leave the dock fixed while you compare a nearby return with a normal mission return.
Why can’t my Roborock Saros 20 Sonic find the dock?
Roborock lists several return-to-dock causes: the robot may have been started from a different location, manually moved, blocked by obstacles, or unable to read the dock signal area. Keep the dock against a wall with roughly 0.5 m clear on each side and 1.5 m in front, clean the signal/sensor surfaces, then test return from a mapped area.
How much clearance does the Saros 20 Sonic dock need?
Roborock’s model troubleshooting says to place the dock against a wall with at least about 0.5 m of clearance on either side and 1.5 m in front. That open corridor gives the Saros 20 Sonic room to detect and approach the dock. If it finds the dock after clearing the area, the earlier failure was not a charging-contact problem.
Did this diagnostic narrow the fault?
Use this as an editorial signal, not a popularity counter. If a feedback address is configured you can email the note; otherwise you can copy it for your own support record.