Robot vacuums: what Matter exposes, and what stays in the app

Matter has covered robot vacuums since 2023, and the vendor app is still the only place you can draw a no-go zone. That is not a bug in your platform.

What the standard actually covers#

The robot vacuum cleaner device type is built from three clusters, and both Google and Amazon document exactly these:

Matter 1.4 added an optional service area cluster, which is the closest thing to "clean the kitchen". It is a list of vendor-named area identifiers the robot reports, which a controller can select or exclude. It is not a map. There are no coordinates, no room shapes, and no way to create or edit an area from the controller. You still draw and name your rooms in the vendor app, and the service area cluster hands those names across.

There are roughly 280 robot vacuum certification records in the alliance's database, so unlike cameras, this is a category where the hardware genuinely showed up. The problem is elsewhere.

What is not in Matter, and never has been#

This list is a specification gap, not a controller lag problem, in the sense set out in what Matter still cannot do. No firmware update to your hub adds a map. Draft work on future Matter releases has not addressed it either.

What each platform exposes#

PlatformWhat you get
Apple HomeThe best of the mainstream three. Whole-home cleaning, room selection and exclusion, pause, resume, dock, suction and mop power, locate, status alerts, and use in scenes and automations. Still no maps and no no-go zones
Home AssistantFull cluster support, plus a generic "clean area" action added in 2026.3 that maps the service area cluster onto Home Assistant's own areas rather than vendor identifiers
SmartThingsRun mode, clean mode and operational state
Google HomeRun mode, clean mode and operational state. Google does not implement the service area cluster at all, so room selection is unavailable
AlexaThe thinnest. Amazon's own category documentation maps only RVC Run Mode onto a mode controller. Clean mode, operational state and service area are unavailable

Apple's reputation on vacuums is worse than the reality. Support arrived with iOS 18.4 and it is genuinely usable: you can send the robot to specific rooms, keep it out of others, set suction level and dock it, all from the Home app and from automations. What you cannot do is see where it has been. If you use Apple Home, the vacuum is one of the better Matter appliance stories, which is notable given that Apple does not support the Matter appliance device types generally.

Alexa is the opposite. On Alexa, a Matter vacuum is effectively a switch with three positions. That is worth knowing before you buy a robot specifically to say "Alexa, vacuum the kitchen", because that sentence has nowhere to land.

Local, cloud, and what the vendor app is doing#

A robot vacuum is one of the most cloud-dependent devices in a normal house, and Matter does not change that. Even where the integration looks local, it usually is not end to end. Home Assistant's Roborock integration is explicitly hybrid: commands and polling run locally, while setup, fallback, map data and routines use the cloud. That is the honest shape of nearly every vacuum integration, and it is why the local versus cloud distinction has to be asked per feature rather than per device.

There is a privacy dimension here too. A mapping robot builds a floor plan of your home, and on camera-equipped models it collects images from inside it. Where that data goes and how long it is kept is a vendor policy question, not a protocol one. Smart home privacy without paranoia covers what each class of device sends home.

The iRobot warning, and what it teaches#

iRobot is worth studying because everything that can go wrong in this category went wrong at once.

In January 2026 iRobot shipped Matter support by firmware update to several Roomba models, with Apple Home as the only supported ecosystem. At the same time it removed Matter from the Roomba Combo j7 and j9, because those models had not been properly certified. Owners of two flagship robots watched a feature appear on the roadmap and disappear from their hardware in the same release.

Separately, iRobot filed for Chapter 11 in December 2025 and emerged in January 2026 as a private company under new ownership. That is not a prediction of anything; companies emerge from restructuring and continue for years. It is a reason to weigh how much of the product's value depends on servers the new owners have to keep paying for.

The general lesson is the one on when a smart home company shuts down: with a vacuum, the cloud dependency is unusually deep, because maps, scheduling and the app itself typically live there. A vacuum whose cloud goes away is a robot you start by pressing the button on its lid.

What Matter actually buys you here#

It is easy to read the list above and conclude that Matter is pointless for vacuums. That is too strong. Three things are worth real money:

  1. Voice and app control that survives a platform change. "Start the vacuum" and "dock the vacuum" work from any certified controller, and keep working if you switch platforms. See switching platforms without rebuying.
  2. Automation triggers in both directions. The vacuum's operational state is readable, so you can pause it when the doorbell rings, dock it when someone starts a call, or run it when the last person leaves. That trigger data does not cross a cloud-to-cloud integration reliably, and it does over Matter.
  3. Room dispatch, on the platforms that implement service area. On Apple Home and Home Assistant, "clean the kitchen" is a real automation, not a novelty.

What it does not buy you is a reason to stop opening the vendor app. Plan on using both.

Buying rules#

Why does my robot vacuum have no map in Apple Home or Google Home?

Because maps are not part of Matter. The standard covers run mode, clean mode and operational state, plus an optional list of vendor-named areas. There are no coordinates or floor plans in the specification, so no controller can display one, and no update will add it.

Can I set no-go zones through Matter?

No. No-go zones and virtual walls are entirely outside the specification and always have been. You draw them in the manufacturer's app, and the robot respects them regardless of which platform started the clean.

Which platform is best for a Matter robot vacuum?

Apple Home and Home Assistant. Both implement the service area cluster, so room selection and exclusion work, along with suction and mop power, pause, resume, dock and locate. Google Home does not implement service area at all, and Alexa exposes only the run mode.

Can Alexa clean a specific room with a Matter vacuum?

No. Amazon's documentation maps only the RVC Run Mode cluster onto Alexa, so you get idle, cleaning and mapping. Clean mode, operational state and room selection are not available. Room-specific cleaning has to come from the vendor's own Alexa skill, if the brand offers one.

Does Matter let me schedule my robot vacuum?

Not directly. Matter has no vacuum scheduling. You either schedule in the vendor app, which keeps working independently, or you build a time-based automation in your platform that sends a start command. Both are fine; the second one breaks if your controller is down.

Should I connect my vacuum over Matter or use the vendor integration?

Both, usually. Pair over Matter for reliable voice control, status triggers and portability across platforms, and keep the vendor app for maps, zones, consumables and firmware. Neither one replaces the other today.

Is a Matter vacuum local?

Partly. The Matter command path is local on your network, but map data, scheduling and often the vendor app itself are cloud services. Home Assistant's Roborock integration documents this shape directly: local commands and polling, cloud for setup, maps and routines.

Primary sources

Specification and vendor documentation we checked while writing this page. Where a claim depends on firmware behaviour rather than a published spec, the page says so inline.