Samsung Robot Vacuum Cycle Not Completing: Check Charging, Obstacles, and Sensors

Use only checks that match the exact appliance or system and its official guide.

1. Check 1

   Check the robot and SmartThings status without moving the vacuum first. Record whether the cycle is marked complete, paused, returning to charge, stopped by an error, or missing from the recent cleaning history. Note the cleaning mode, last location, battery indication, and any voice or LED message.

   Expected result: The robot is returning because of low battery, the history says the cycle completed, it is paused or asleep, a red error is shown, or it stopped without a status explanation.

   Next step: Follow the matching branch below and keep the exact model available. Do not infer a failed motor or battery from an incomplete-looking map alone.

   Why this matters

   Why: A low-battery return or a completed accessible-area report can be normal cycle behavior. A red error, repeated stop at one location, or no matching status points toward an obstacle, debris, sensor, charging, map, or model-specific fault.

2. Check 2

   Inspect the cleaning route and the robot's stopping area from a safe, dry position. Remove cords, small objects, low-clearance obstructions, and anything caught around the main brush, side brush, wheels, or mop attachments. If the model reports that it is stuck, place it in Sleep mode or use the model's documented stop control before clearing debris.

   Expected result: The robot is trapped, a brush or wheel cannot move freely, a mop or dustbin is not seated, the route is clear, or the same location is repeatedly missed.

   Next step: Clear only accessible debris and reseat only the model-documented removable part. Run one supervised retest after the robot is clear; do not force a wheel, brush, cover, or mop board.

   Why this matters

   Why: A trapped robot or blocked drive part can stop a cycle before the map is complete. A clear route shifts attention to lighting, dark surfaces, sensor windows, dock access, battery, or software and map state.

3. Check 3

   Clean the accessible sensor windows and signal areas with the method in the exact model guide. For Jet Bot Combo guidance, this includes the LiDAR, 3D, obstacle, carpet-detect, cliff, and signal-transmitter windows; use a soft cloth and do not use a wet cloth on electrical contacts unless the model specifically permits it.

   Expected result: A sensor window has dust or debris, a dark floor or reflective surface is repeatedly avoided, the robot reports a cliff or obstacle sensor issue, or the sensor areas are clean.

   Next step: Improve lighting and remove the specific visual or physical obstruction where safe, then perform one supervised run. Do not tape over, bypass, or disassemble a safety sensor.

   Why this matters

   Why: Dust, dark flooring, reflections, and room obstacles can make the robot treat an accessible route as blocked or risky. Clean sensors support a navigation or mapping check; a recurring sensor message after cleaning needs model-specific service.

4. Check 4

   Check the docking station and charging path. Confirm the outlet supplies power, the station is on a flat level surface, the charging pins and contacts are clean and dry, and the station has clear access on both sides and in front. If the robot is fully depleted or cannot dock, place it so the charging terminals align and observe whether charging begins.

   Expected result: The station is unpowered, tilted, blocked, dirty at the contacts, or the robot charges with aligned contacts; the robot leaves and returns repeatedly; or it will not charge.

   Next step: Correct only the accessible station position or contact cleanliness described by Samsung, then allow one charge attempt. Keep the robot out of service and request support if charging still fails or the station is damaged.

   Why this matters

   Why: A low battery can end the current movement, and a station that cannot be reached or cannot maintain contact prevents a recharge and resume. Repeated docking attempts or no charging leave a dock, contact, battery, or control issue possible.

5. Check 5

   Compare the selected mode and map behavior with the exact model instructions. In Auto Clean, observe whether the robot resumes after charging; in a mode that does not resume after recharge, use the documented mode or start command. Check SmartThings for a downtime schedule, no-go zone, cleaning history, or a map that was lost after the robot was lifted or manually moved.

   Expected result: The mode is Auto Clean and the robot resumes, the mode is Max Clean or another non-resuming behavior, a downtime or no-go setting ends the run, or the map was cleared or lost after moving the robot.

   Next step: Use the exact model's documented mode or SmartThings setting and run one supervised cycle from the intended starting area. Do not repeatedly delete maps or lift the robot while it is navigating.

   Why this matters

   Why: A mode, schedule, exclusion zone, or interrupted map can make a normal stop look like a failed cycle. If the robot stops in the same place despite the correct mode and map, a physical obstacle, sensor, drive, or control problem is more likely.

6. Check 6

   If the robot or station reports an error, record the exact voice message, LED state, and what was moving when it stopped before resetting. Use the matching model guide for one permitted reset or accessible clearing step, then observe whether the same message returns.

   Expected result: The message identifies a brush, wheel, bumper, cliff sensor, dustbin, clean-station tank, LiDAR, battery, or main-system condition; the message clears once; or the same error returns.

   Next step: Stop after the model-documented step and one supervised retest. Keep the unit or station off when there is a leak, damaged cable, abnormal heat, smoke, or a recurring electrical or battery-related message, and arrange qualified service.

   Why this matters

   Why: The message narrows the next safe check but does not identify a replacement part. Samsung routes recurring sensor, battery, main-system, leak, or unresolved error conditions to support.