The same code can mean different faults on different robots. Select the exact model first, then choose the error or symptom.
1 Brand2 Model3 Error / symptom
Choose your exact model before the code. The same number can mean different things across brands and generations.
How to use a robot-vacuum error result
Start with the label printed in the app or spoken by the robot, but treat that label as a routing clue rather than a complete diagnosis. Manufacturers reuse numbers across families, and a phrase such as “charging error” can describe dock power, contact alignment, battery state or a station communication problem. The finder therefore asks for brand and exact model before it offers a guide.
Once you open a result, read the match conditions before touching the robot. A good match should describe the same model family, the same error or symptom, and the same stage of operation. If the guide says “cannot find dock” but your robot reaches the station and repeatedly backs out, use the final-approach or charging path instead. That distinction prevents a map reset from being used on what is actually a contact or alignment problem.
Use pass conditions as evidence
Each ordered step includes a pass condition. The purpose is to narrow the branch, not to make you repeat every possible fix. For example, a robot that charges immediately when seated by hand has already proved more than a robot that never draws power at all. Record that result, then move to the next branch that explains what remains. If a controlled test changes nothing, preserve the result for support rather than cycling resets indefinitely.
When the finder should not be used
Stop owner-level troubleshooting when there is smoke, battery swelling, dangerous heat, a burning smell, damaged mains wiring or liquid where powered electronics are exposed. Do not bypass cliff sensors, open battery packs or defeat safety interlocks to make a guide “work.” For those conditions, use the manufacturer’s current safety and service channel for your exact region and model.
Don’t know the model or code?
Start from the behavior instead: docking, charging, map/navigation, Wi-Fi, cleaning path or wet-system problems.