Robot vacuums in Home Assistant: local Matter vs cloud

A robot vacuum can join your Home Assistant dashboard and still phone home for important jobs. Matter is the cleanest route for local cleaning commands; the maker’s integration is usually the richer route for maps and room controls. Buy for the jobs you want to automate, not just the badge on the box.

Our purchase pick here is the Roborock Saros 10R: Roborock names its Matter-enabled firmware, currently lists Matter support, and Home Assistant documents both the Matter and native Roborock paths. Use Matter for everyday local controls; add the native integration when its extra features are worth the cloud dependency.

Features and compatibility come from maker and Home Assistant documentation; this is a research-based guide.

What works locally, and what still needs the cloud?

Job	Matter route	Native Roborock integration
Start, stop and return to dock	Local vacuum commands; the available controls follow what the device exposes	Local commands preferred, with cloud fallback
Cleaning status and basic settings	Only the states and settings exposed over Matter	A broader set of supported robot and dock entities
Map image in Home Assistant	Choose the native/app workflow for a map image	Map data is fetched through the cloud
Room cleaning	Depends on the robot’s exposed Matter areas and HA support	HA documents mapping vacuum segments to areas and selecting rooms
Routines and advanced setup	Keep the maker app for its full setup tools	Routines are fetched through the cloud
Robot internet access blocked	HA documents offline Matter operation with limited controls and sensors	The robot blocks its native local API until it can reach Roborock’s servers

That last row is the buying decision. The Roborock integration uses local communication, but local commands don’t make that whole integration cloud-independent. Its setup, map data and fallback still use Roborock’s service.

By contrast, HA’s Matter integration controls devices locally. The robot may still need its maker app and account for provisioning, firmware and advanced features. Treat those as separate questions: how you set it up, how HA sends a clean command, and where the map comes from.

Our documented Matter pick: Roborock Saros 10R

Choose the Saros 10R when you want a vacuum-and-mop robot with a documented Matter path and a full maintenance dock. Roborock’s Matter firmware announcement names 02.32.44 for this exact model in its 2025 rollout. Its current product page also lists Matter support.

Install the current firmware for your unit and confirm the Matter pairing option in the app. The named version is a useful model-specific reference, not a reason to downgrade a newer robot. Keep Saros 10R, Saros 10 and newer Saros revisions distinct when choosing the product.

The physical fit matters just as much as the integration. Roborock lists these dimensions:

Piece	Maker dimensions	Your fit check
Robot	350 × 353 × 79.8mm	Check the actual gap under furniture, including rugs and uneven edges
Dock	381 × 475 × 488mm	Leave the approach and service access required by the manual

The maker lists auto dust emptying and hot-water mop washing. Those features reduce some daily chores; you still need to service the dock, water system and consumables. Choose a spot where you can reach them easily rather than hiding the dock in a gap that only the robot enjoys.

We’re choosing the control path and documented fit, not ranking cleaning performance from suction figures. If you want a robot to clean a specific awkward carpet or threshold, make that part of your own acceptance check within the seller’s return terms.

Get the local basics working before building automations

Start with a simple dashboard control. You should be able to send a clean command, stop it and bring the robot back without opening a second app for each action.

1. Add the exact robot to the Roborock app, complete its initial setup and install the current firmware. Follow the maker’s process to expose its Matter pairing code.
2. Set up HA’s supported Matter Server path. Home Assistant OS with the Matter Server app is the straightforward documented route; follow the Matter setup instructions for your installation.
3. Use the Home Assistant Companion app’s Add Matter device flow. Keep the phone, controller and robot on a network that allows the discovery traffic the docs require.
4. Name the Matter vacuum clearly. If you also add the native Roborock integration, give those entities different names so you can tell which route an automation uses.
5. Open the vacuum’s controls and try a short supervised clean, stop/pause and dock command. HA shows command buttons according to the features the robot reports; the vacuum control-view guide explains that interface.

Don’t mix the two entities while testing. A native command that silently uses cloud fallback tells you nothing about whether your Matter entity works offline.

For the host side, our Home Assistant starter guide gets you started, and the mini-PC guide covers a host with room for other local services. You don’t need to buy another Zigbee coordinator to commission a Matter vacuum.

Maps and rooms: keep the useful distinction

A map image, a room identifier and a command to clean that room are different features. A robot can expose some of them without exposing all of them through the same integration.

For the native Roborock route, HA documents map and routine retrieval through the cloud. It also documents linking vacuum segments to HA areas and using the room-selection control. That’s the supported workflow to investigate when you want the robot on your dashboard with its richer map and room tools.

Matter room cleaning isn’t universally absent. HA supports area-aware vacuum controls when the robot and integration provide those features. For the Saros 10R, this guide’s purchase recommendation rests on the documented Matter route and basic controls; use the exposed entity features to decide whether you can build a room-specific action on your installed firmware. Keep the maker/native workflow for features that aren’t exposed there.

That keeps your dashboard honest. Label a button Clean the kitchen only after it targets a real area. If it starts a whole-floor clean, call it Start cleaning. Tiny label, big difference when someone has just dropped crumbs.

Roomba is not a blanket cloud-only answer

If you already own a Roomba, read its exact model against HA’s iRobot Roomba and Braava integration before replacing it. HA classifies that integration as Local Push and lists supported older robots. It currently excludes the newer 105, 405 and 505 models from that native integration.

The robot password is separate from your iRobot account password. Some models allow local credential retrieval during HA setup; others need a different retrieval method that can involve the cloud. Credential setup and everyday command transport are separate issues here too.

Keep a working, supported robot if it already does the job. For a new purchase, an exact model and control route are more useful than a brand-wide “local” or “cloud” label.

Run a clean offline-control check

Once the Matter entity works normally, test the feature you bought it for. This is a practical acceptance routine for your setup, not a cleaning benchmark:

1. Record which entity belongs to Matter and which belongs to the native integration.
2. At your router, temporarily block only the robot’s internet access while keeping its local network connection and HA running. Turning off its Wi-Fi would remove the local path too.
3. From the Matter entity, start a small supervised clean, stop it and send it back to the dock. Check the reported state as well as the command.
4. Note which settings and area controls remain available. A missing cloud map image is a different result from a failed local command.
5. Restore internet access and verify firmware/app maintenance still works. Save the result with the model, robot firmware and HA version so a later update has a baseline.

Use the result to choose the entity in each automation. Keep the everyday clean/dock buttons on Matter if they pass; reserve native/app tools for the richer features you use. Don’t block internet on the native integration and expect the same behavior—HA explicitly documents that dependency.

Three useful dashboard jobs

• A cleaning button you can trust: use the Matter entity’s Start vacuum cleaner action for a basic clean. Give it a whole-floor label unless you’ve validated area selection.
• Send it home before an activity: add Return vacuum cleaner to base to a scene script or a deliberate dashboard button. Select the Matter entity, not a similarly named native one.
• A maintenance glance: place cleaning state beside the battery or maintenance entities actually exposed by your chosen route. Keep the cloud-derived map card separate so its availability is easy to understand.

Build those simple controls first. Then add triggers from your existing Home Assistant devices. The Home Assistant hub has buttons, presence sensors and lighting projects to build around them.

The verdict

Buy the Saros 10R for a maker-documented Matter option, and put basic local cleaning controls on its Matter entity. Add the native Roborock integration for the map and richer room workflow, knowing it still depends on the cloud. Keep a supported existing robot when it already fits. The win is a vacuum that does the jobs you want through the route you intended—not a dashboard full of duplicate buttons and surprises.