SwitchBot robot appears as a switch: check the documented prerequisites in order, then retry only the affected path.
Start with these checks
A robot can appear under a generic endpoint while the platform has incomplete robot-vacuum controls. Compare the bridge’s exported endpoint and the target platform’s device-type support. Do not assume maps and rooms will follow a basic switch-like representation.
- Check whether using the bridge route.
- Verify on=clean and off=recharge mapping.
Stop when you find the first unmet requirement. Fix it and try pairing again before changing the next variable.
How to interpret the outcome
Documented bridge entity mapping, not evidence of full native robot support.
A failed path does not prove every alternative path is unsupported. For example, a missing direct radio may still leave a separately documented bridge or cloud route.
Avoid these risky shortcuts
- Promise maps or room cleaning from this switch entity
Relevant model records
Official references
- SwitchBot — Matter sub-device support table Reviewed 2026-10-30
These are evidence-based editorial checks, not a diagnosis of your individual home network.