Robot vacuums that work with Home Assistant: brands and how they integrate

Roborock, Roomba, Ecovacs, SwitchBot, Shark, Xiaomi, Dreame: official or community integrations, local vs cloud, from Home Assistant docs. Table and buying advice.

Also available in French.

A robot vacuum pays off when it runs on its own—when the house is empty, after dinner, or only in the kitchen. That means tying it into Home Assistant. Brands integrate differently: some talk locally, others only via the maker’s cloud; some rely on community add-ons. The table below follows Home Assistant vacuum integrations (IoT class on each page, October 2026).

Two paths: the robot reaches Home Assistant on the local network, or through the manufacturer cloud
Green arrow: the robot talks to Home Assistant on the local network. Orange arrow: commands go through the manufacturer cloud. The table shows which path the Home Assistant docs describe for each brand.

At a glance

Brand Home Assistant integration Connection (HA docs) Notes
Roborock Roborock (official) Local polling Roborock account for setup, then local control
iRobot Roomba / Braava Roomba and Braava (official) Local push Wi-Fi models
Ecovacs Ecovacs (official) Cloud push Depends on Ecovacs cloud
SwitchBot SwitchBot Cloud (official) Cloud polling Docs list K10+, K10+ Pro, K11+, K20+ Pro, S10, S20
Shark Shark IQ (official) Cloud polling Shark IQ range
Xiaomi (older) Xiaomi Miio (official) Local polling Model-dependent
Dreame No official integration — Community via HACS
Matter robots Matter Local Vacuum type added in Matter 1.2 (CSA)

Our pick: Roborock. Official integration, local control, room selection, consumables and errors. Budget example: Roborock Q7 M5 in robot vacuums under £200 / $200.

Local vs cloud

  • Local: Home Assistant talks to the robot on your LAN. Commands are fast and survive internet outages or API changes—until the vendor breaks local APIs.
  • Cloud: Every command goes through the maker’s servers. It works until it does not—a outage or API shutdown can kill integration overnight.

For longevity, prefer integrations marked Local in Home Assistant docs.

What you can automate

Once integrated, the robot appears as a vacuum entity. Common patterns:

  • Start cleaning when everyone has left (person / zone tracking);
  • Clean only the kitchen after meals (room clean if the integration supports it);
  • Notify when the bin is full or the robot is stuck;
  • Track brush and filter wear.

automation:

  • alias: “Vacuum when house empty” trigger:
    • platform: state entity_id: zone.home to: “0” for: “00:15:00” action:
    • action: vacuum.start target: entity_id: vacuum.living_room_robot

Replace vacuum.living_room_robot with your entity id.

Before you buy

  1. Search the exact model on the brand’s Home Assistant integration page.
  2. Confirm official and local if possible.
  3. Pick navigation: LiDAR maps accurately and enables room cleans (LiDAR vs camera vs gyro).
  4. Mop and dock: mop types and self-cleaning docks.

No server yet? Install Home Assistant on Raspberry Pi 5.

All smart-home guides

Was this page helpful?

Have a question about this guide or need advice? Ask us here

Torn between two models or stuck on a build? Drop us a line and we will get back to you by email.