Why My Roborock S8 Keeps Missing the Same Rug Corner
The Roborock S8 has one specific failure mode that drives owners to the support forums: it maps the living room beautifully, runs a clean pattern across hard floor, rolls onto the rug, and then skips the exact same corner every single run. Not a random miss — the same corner, the same rug, trip after trip. If you’re seeing a roborock s8 missing rug corner pattern that repeats, the cause is almost never a broken unit. It’s a collision between the S8’s carpet-detection logic, its LiDAR-based path planning, and whatever is physically happening at that specific corner of the rug.
The fix is usually a five-minute adjustment. But to pick the right one, you have to understand which of the three sensor systems on the S8 is getting confused, because they fail for different reasons and the wrong fix makes the miss permanent.
What the S8 actually sees when it approaches a rug
The S8 uses three independent sensing systems during a normal clean, and all three have to agree before it commits to covering a patch of floor. The top-mounted PreciSense LiDAR turret spins at roughly 5 Hz and builds the 2D floor plan you see in the Roborock app. This is the map that decides where the robot plans to go. The structured-light Reactive 3D obstacle sensor on the front bumper scans for anything taller than about 3 cm in the immediate path — that’s what dodges shoes and cables. And underneath, an ultrasonic carpet sensor pings the floor roughly every few centimeters to detect the density change between hard floor and pile.
When the robot approaches a rug, the ultrasonic sensor fires, the VibraRise mopping plate lifts the mop module 5 mm to keep it off the pile, and the path planner decides whether to treat this patch as “carpet” (vacuum it with boosted suction) or “no-mop zone” (skip it if mopping). That decision is binary and it happens once per approach. If the robot crosses onto the rug at a shallow angle and the ultrasonic sensor doesn’t trigger until the wheels are already on the pile, the planner can log the rug as an obstacle rather than a surface, and the path it builds over the rug will be incomplete. The corner furthest from the entry point is the one that gets amputated.
The three causes of a repeating corner miss
Across the owner reports I’ve read on the Roborock subreddit and the official support forum, the same handful of physical setups produce the same repeating miss. They break down cleanly into three categories, and diagnosing which one you have is the whole game.
1. The rug corner is curled, frayed, or tasseled
The most common cause. A rug corner that has lifted even 4-5 mm off the floor reads to the Reactive 3D sensor as an obstacle, not a surface. The S8 doesn’t try to climb it — it pathfinds around it, logs a small “bump” polygon on the map, and the planner treats the area just inside that polygon as inaccessible. On the next run, the saved map still has that obstacle noted, so the robot approaches the rug on a trajectory that deliberately avoids the corner it couldn’t reach before. You get the same miss, forever, because the map is teaching itself to miss.
The fix is to clear the obstacle, reset the affected area on the map, and let the robot re-learn. In the Roborock app, open the map, tap the rug’s room, and use Map Management → Reset Map for that room only if multi-floor editing is enabled. If not, a full map reset works but costs you all your no-go zones. Before the next run, flatten the corner with a heavy book for 24 hours, or if the rug is a persistent curler, use double-sided rug tape or a corner gripper. This is the single most common fix and it resolves maybe 60% of reports.
2. The rug is dark, low-pile, and positioned against a dark floor
The LDS on the S8 is laser-based and doesn’t care about color, but the downward cliff sensors on the underside do. Roborock uses infrared reflectance to detect stairs and drops, and a dark wool rug on dark hardwood reflects so little IR that the robot thinks it’s approaching a cliff. When that triggers, the S8 performs an emergency stop, backs up, and marks the area as unsafe. The same spot gets marked on every run because it’s a property of the rug material, not a random glitch.
Roborock documents this in the cliff-sensor section of the S8 user manual: the device can misread any surface darker than about 5% IR reflectance. The fix is either to swap the rug for a lighter one (not usually an option), move the rug so the dark edge isn’t near a real drop, or — the cleanest solution — use the Roborock app to draw a virtual wall that keeps the robot from approaching that specific corner at an angle that triggers the cliff sensor. Approaching the rug head-on rather than from a diagonal often sidesteps the issue entirely, because the cliff sensors on opposite sides of the chassis have to agree before an emergency stop fires.
3. The path planner is hitting a known coverage bug at room boundaries
This one is more subtle. If your rug sits at the edge of a room boundary that the S8’s segmentation algorithm has detected, the planner sometimes treats the rug corner that crosses the boundary as belonging to the other room. When you run a zone clean or room clean, that corner gets orphaned — it’s not in either room’s coverage plan. The symptom looks identical to an obstacle miss but the cause is software, not physical.
You can confirm this by running a full whole-home clean instead of a room clean. If the corner gets covered in whole-home mode but missed in room mode, it’s a segmentation bug. The fix is to manually edit the room boundaries in the Roborock app under Map Editor → Room Management → Split/Merge and redraw the boundary so the rug sits entirely within a single room. Firmware updates through 2024 and 2025 improved this but did not eliminate it, and owners reporting the issue on firmware 02.06.54 and newer still hit it occasionally on L-shaped rooms.
How to tell which cause you have in under two minutes
Grab your phone and open the Roborock app during a run. Watch the live map as the robot approaches the problem rug. You’re looking for three tells:
- If the robot physically stops at the rug edge and backs up before entering, you have a cliff-sensor false positive (cause #2).
- If the robot enters the rug cleanly, cleans most of it, and the missed corner shows as a small grey polygon on the map, you have a curled-corner obstacle miss (cause #1).
- If the robot enters, cleans, and the missed corner shows no polygon at all — the map just doesn’t include that area in the cleaning plan — you have a segmentation bug (cause #3).
This diagnostic works because the three failure modes leave different signatures on the live map. An obstacle miss draws a polygon. A cliff-sensor miss shows a backup track. A segmentation miss shows nothing, because as far as the robot is concerned, it completed the room.
The VibraRise mop module makes this worse on some rugs
If your S8 is actually an S8+ or an S8 Pro Ultra with the VibraRise mop attached, there’s an additional failure mode worth knowing about. The mop-lift mechanism raises the pad 5 mm when carpet is detected, but the detection has to trigger before the leading edge of the mop hits the pile. On a shallow-angle approach to a rug, the ultrasonic sensor can miss the edge entirely for the first half-second because the wheel touches carpet before the sensor’s beam angle covers the floor beneath the mop. The robot then senses the mop dragging, aborts the approach, and marks the rug as a no-entry zone for the rest of that run.
The fix is in the app under Cleaning Settings → Mop → Rug Avoidance. Set it to “Rise” rather than “Avoid” if your rug is a low-pile woven type (the mop will lift and the robot will still clean it). If the rug is high-pile or a shag, set it to “Avoid” and draw a no-mop zone that extends 10 cm beyond the rug’s physical border on the approach side. That extra buffer gives the ultrasonic sensor time to trigger cleanly.
Firmware, app version, and what to check before you escalate
Before you contact Roborock support about a corner miss, get two version numbers. In the app, tap the robot, then the gear icon, then Device Info. Note the firmware version and the app version. The S8 shipped with firmware 02.04.xx, and the major map-handling improvements landed in 02.06.54 and later. If you’re still on an early firmware, a manual update often resolves map drift issues that look like corner misses but are actually tiny cumulative errors in the saved map.
Force a firmware check by pulling down on the device info screen. If an update is available, run it with the robot on the dock and the dock plugged in — interrupted firmware updates on the S8 can brick the mapping module, and recovering from that requires a full factory reset that wipes all saved maps. I’d rather clean a rug by hand for a week than lose three months of tuned no-go zones.
A useful sanity check before escalating: drop a piece of white printer paper on the missed corner and run a zone clean over just that square meter. If the robot covers it cleanly, the rug is the problem, not the robot. If it still misses, you have a mechanical or sensor issue that warrants a support ticket. Reference your firmware version in the ticket and Roborock’s L2 support will typically ask for a map screenshot and a cleaning log export, both of which you can generate from Cleaning History → Share → Export Log.
The no-go zone trick that fixes stubborn cases
If none of the above resolves it and the corner still misses on every run, there’s one more trick that works because it exploits how the S8’s planner handles forbidden regions. Draw a small no-go zone inside the rug, maybe 20 cm square, not covering the missed corner but near the rug’s center. This forces the planner to re-compute coverage on the next run because the old saved path is now invalidated. The new path often covers the previously-missed corner because the planner re-enters the rug from a different angle to route around the new no-go zone.
After one or two clean runs, delete the no-go zone. The planner usually keeps the new, better path and the corner stays clean going forward. This is a cache-busting trick, essentially — the S8 memoizes its room coverage plans, and a small perturbation forces a re-plan. Roborock hasn’t documented this and it’s not guaranteed, but it’s the fix of last resort that worked for a coworker’s S8 Pro Ultra after three weeks of daily corner misses in her office.
When the fix doesn’t stick
For a repeating miss, the order of operations that resolves the most cases in the fewest steps is: flatten the corner, reset the room map, run a whole-home clean, check firmware, add the no-go cache-bust if still missing. Skip straight to contacting support only if the robot physically stops and refuses to enter the rug at all — that’s a sensor failure and no amount of map editing will fix it.
The thing to internalize is that the S8’s corner miss is almost always a feedback loop between a physical quirk of your rug and a map that’s learned to work around it. Break the loop once, with a flattened corner and a fresh room map, and the robot usually stays fixed. Treat the saved map as a mutable state that can go bad, not as a one-time setup, and the S8 gets a lot less frustrating.
You may also like
Leave a Reply