Local robot vacuum control
Compare Home Assistant's Roborock integration, Matter and Valetudo for offline cleaning, room selection, maps and setup requirements.
On this page
For local cleaning without rooting, I would start with a vacuum whose released firmware supports Matter. Valetudo offers cloud-free control on specifically supported hardware if you are willing to install it. The native Roborock integration can expose extra controls, but it keeps a cloud dependency.
Matter support was why I chose Roborock. I own a Roborock Qrevo MaxV, and in my owner review I described automating it to clean when nobody is home.
The comparison below draws on the linked documentation. It does not include an offline test of my vacuum.
Compare the controls you need
“Works with Home Assistant” does not answer whether cleaning survives an internet outage, whether setup needs an account, or whether you can select a room. Those are separate requirements.
| Connection | Offline control and trade-offs |
|---|---|
| Native Roborock | Cloud access remains required. Setup uses a Roborock account; maps and routines come through the cloud. Available mop, dock and maintenance controls depend on the model. |
| Matter | Commands run locally after setup. Room cleaning needs compatible device support. Check each dock or mop function separately, and whether initial vendor setup requires an account. |
| Valetudo | Local operation without a vendor cloud, with maps in its web interface. Requires root access on an exact supported robot. Home Assistant connects through MQTT; an additional card displays maps. |
The table draws on Roborock’s Home Assistant documentation, Matter’s setup requirements, and Valetudo’s capabilities and Home Assistant guide. Features depend on the device, firmware and integration version. For the broader distinction between native and Matter connections, see Matter bridge vs native Matter.
Native Roborock keeps a cloud dependency
Home Assistant prefers local communication for most supported Roborock robots, with cloud setup and fallback. Its documentation also says the vacuum blocks its local API when it cannot reach Roborock’s servers. Blocking its internet access therefore does not turn this integration into an offline solution. Maps and routines are cloud-fetched too. Home Assistant’s Roborock documentation
I would consider this route for an existing compatible Roborock when convenient access to supported mop, dock and maintenance controls is the priority. Compatibility varies within the Q-series, so a brand name alone is insufficient. Read the supported-device section for the exact model before choosing this connection. Supported Roborock devices and controls
Matter can clean rooms, with device support
Matter cleaning commands run locally after setup. Initial setup is a separate question: a manufacturer may require an account before enabling Matter. Follow the vacuum’s setup instructions and Home Assistant’s pairing guide. A Wi-Fi Matter device does not need a Thread border router merely because it uses Matter. Home Assistant’s Matter guide
Older advice that Matter cannot select rooms in Home Assistant is outdated. Home Assistant 2026.3 added area cleaning for Matter, Roborock and Ecovacs. That addition enables compatible devices; it does not give every vacuum room support. Home Assistant 2026.3 release notes
Open the vacuum entity’s settings and look for “Map vacuum segments to areas.” Match the reported segments to your Home Assistant rooms. If that option is absent, Home Assistant’s documentation says that entity cannot use its clean-area action. Room selection also does not tell you whether live maps, map editing or every dock setting is available. Home Assistant’s area-cleaning instructions
Before buying for Matter, confirm that the required firmware is released for your exact model and region. Roborock’s Qrevo Edge series page, checked September 12, 2026, still describes Matter as an upcoming update. That wording cannot verify what firmware an individual unit has today. I would ask for confirmation of the released feature instead of treating a product-page badge as enough. Roborock’s Matter update footnote
Valetudo requires a compatible robot and installation work
Valetudo replaces the vendor cloud connection while running alongside the robot’s existing firmware. Installing it requires root access. Valetudo itself needs no cloud account. It provides a local web interface, with features such as maps and room cleaning where supported; it does not reproduce every feature of the manufacturer’s app. Valetudo’s newcomer guide
For Home Assistant, Valetudo uses MQTT and automatic entity discovery. You need a local MQTT broker, such as Mosquitto. Basic controls appear as entities; more specific actions, including segment cleaning, can require MQTT messages. Displaying its map inside Home Assistant uses an additional map card. Valetudo’s Home Assistant instructions
I would read the installation instructions before choosing a robot for this route. Valetudo’s supported list is exhaustive: an absent model is unsupported. Similar names can conceal different hardware; the list explicitly distinguishes the supported Dreame L10s Ultra from the unsupported L10s Ultra Gen2. That is a compatibility example, not a purchase recommendation. Check hardware revisions and the linked rooting procedure as well as the model name. Valetudo’s supported robots
Verify your own offline requirements
Write down the automation you need before comparing products. Starting a whole-home clean when the house is empty is a different requirement from cleaning only the kitchen, changing mop settings and displaying a live map.
For a Matter or Valetudo setup, I would check those functions with internet access unavailable while keeping the local network running. Use the intended Home Assistant entity, confirm the robot responds, and check that its status updates. Try the room command separately from a whole-home clean, then check return to dock. A dashboard button alone is not evidence that the command completed.
Record the robot model, firmware, Home Assistant version and connection used with the result. This verifies the functions you rely on; it does not establish that every feature is offline or that a different model will behave the same way.