Robot Vacuum
A robot vacuum cleans floors on a schedule and reports its state to Home Assistant. Under local control it becomes a dependable, automatable appliance, with start, pause, return-to-base, spot-clean, and per-room cleaning all handled on the local network.
Connected to Home Assistant, a robot vacuum exposes a vacuum entity with cleaning state, battery level, and error
reporting, and accepts commands to start, pause, stop, return to base, clean a spot, locate the robot, and set the fan
speed. On models that report mapped segments, vacuum.clean_area can send it to specific rooms once those segments are
matched to Home Assistant areas.
How Selora AI uses robot vacuums
- Clean-when-away runs a full pass when the last person leaves.
- After-dinner cleaning sends the robot to the kitchen and dining room as a segment clean.
- Do-not-disturb windows pause or defer cleaning during meetings, naps, or overnight hours.
- Event-driven spot cleans can be triggered by other devices, like a mat sensor by the door or a litter-box cycle.
Why local control matters
Robot vacuums differ mostly in how much they depend on the vendor’s cloud. A local robot keeps responding when the internet or the manufacturer’s servers go down. Its map and room data stay on the LAN, and no floor plan of the home is sent offsite. A cloud-tethered robot stops taking commands when it cannot reach its servers. It also keeps the live map behind an app login and can lose features in a firmware update.
Selora sorts robot vacuums into three tiers so the trade-off is clear:
- Local-first. Robots running the cloud-free Valetudo firmware, or legacy Xiaomi and Roborock units controlled locally through the Xiaomi Miio token, run on the local network and can have their internet access blocked. These are the picks for privacy-critical and enterprise installs.
- Cloud-assisted-local. The current Roborock line via the Roborock integration provides fast local control, but needs a Roborock account to set up, pulls maps and routines from the cloud, and blocks its own local API whenever it cannot reach Roborock’s servers. It is current and well supported, but it still depends on the cloud.
- Cloud. Ecovacs and generic Tuya vacuums lean on the vendor cloud, with only partial or no local control. Dreame has no core integration, but the well-regarded community dreame_vacuum integration is capable (cloud, with a local option), and rootable Dreame models can run fully local on Valetudo.
Compatible devices
D9
A Dreame D9 or D9 Pro rooted and reflashed with cloud-free Valetudo firmware. It publishes a full vacuum entity and live map to Home Assistant over MQTT, runs on the local network, and can have its internet access blocked. One of the most private options in this catalog, and often easier to root than the Roborock equivalents.
L40 Ultra
A mid-range Dreame flagship. With no core Home Assistant integration, its native path is the community dreame_vacuum integration over HACS, which runs in cloud or local mode. Valetudo is the fully cloud-free option on rootable boards.
X50 Ultra
Dreame's step-climbing flagship. With no core Home Assistant integration, its native path is the community dreame_vacuum integration over HACS, which runs in cloud or local mode. Valetudo is the fully cloud-free option on rootable boards.
Deebot T30S Pro
A mainstream Ecovacs Deebot (the US name for the T30S Omni line). The core Ecovacs integration works well through the Ecovacs app but relies on the vendor cloud for Home Assistant control and mapping.
Deebot X8 Pro Omni
An Ecovacs flagship with a self-washing roller mop. The core Ecovacs integration is cloud-based, so control and map data flow through Ecovacs servers and stop responding to Home Assistant when the cloud is unreachable.
Qrevo Curv
A current Roborock flagship with a dual anti-tangle system and AdaptiLift chassis. The core Roborock integration gives fast local control on the LAN, but it needs a Roborock account and leans on the cloud for maps and when offline.
S5 Max
A Roborock S5 Max rooted and reflashed with cloud-free Valetudo firmware. It publishes a full vacuum entity and live map to Home Assistant over MQTT, runs on the local network, and can have all internet access blocked. The most private option in this catalog, once you match the hardware.
S6 MaxV
A legacy Roborock flagship that Home Assistant controls locally through the Xiaomi Miio integration using the device token. Once the token is extracted it runs on the LAN with no cloud in the control path, though the hardware is now discontinued.
S8 MaxV Ultra
The prior-generation Roborock flagship with PreciSense LiDAR and the RockDock Ultra. The core Roborock integration gives local control on the LAN, with the same Roborock-account and cloud-map caveats as the current line.
Saros 10R
Roborock's current ultra-slim flagship. The core Roborock integration gives fast local control on the LAN, though it needs a Roborock account to set up and pulls maps from the cloud. Day-to-day commands and polling stay on the network.
Mi Robot Vacuum
The original 2016 Mi Robot Vacuum, the model that made local Home Assistant control of robot vacuums possible. Driven by the Xiaomi Miio integration over the device token, it runs entirely on the LAN. A dependable fallback on the used market.
Recipes that need this role
No recipes currently reference this role.