Skip to content
Explainer

Running a Robot Vacuum Locally in Home Assistant (No Cloud)

Some robot vacuums will talk to Home Assistant entirely over your own LAN, others refuse to move without a server overseas. Here's how local control actually works, which brands are realistic, what rooting involves, and how to automate cleaning even when the vacuum itself stays cloud-tethered.

Kritin Curtis

Published ·Updated •6 min read
Running a Robot Vacuum Locally in Home Assistant (No Cloud)
AI-generated illustration

Drafted with AI writing tools, then edited and fact-checked by Kritin Curtis. How we research.

The short answer

Only some robot vacuums can run fully locally in Home Assistant — the reliable route is rooting a supported Dreame or Roborock with Valetudo, which gives you MQTT control, live maps and zero internet dependency. If your robot is cloud-only, keep it on an isolated IoT network and make the triggers local with Zigbee sensors instead.

Most robot vacuums sold in Australia ship as cloud appliances. You press "clean" in the app, the command goes to a server (often in China, sometimes Singapore or the US), and the server tells the robot sitting six metres away to start. It works, right up until the internet drops out, the vendor changes the API, or you'd simply rather your floor plan wasn't sitting on someone else's hardware.

The good news: a meaningful subset of robots can be made to run entirely on your LAN with Home Assistant. The less good news is that it depends heavily on the model, and the best options involve rooting.

The short version: three tiers of "local"

It helps to be precise about what people mean by local control, because the marketing blurs it.

Tier 1 — Cloud only. The Home Assistant integration logs into the vendor's account and relays commands via the internet. Nothing works offline. Most Ecovacs, Roborock (stock firmware), Eufy and Samsung robots sit here by default. It's still automatable — it's just not resilient. If you decide stock cloud features are enough, see how Roborock, Ecovacs and Dreame compare across different Australian floor types and pet households.

Tier 2 — Local API, cloud-assisted setup. The robot speaks a documented or reverse-engineered protocol on your LAN, and Home Assistant talks to it directly once you've extracted a token or key. Older Xiaomi/Roborock models are the classic example via the xiaomi_miio integration. Commands are local; maps and firmware updates may still involve the cloud.

Tier 3 — Fully local, cloud severed. The vacuum runs replacement firmware or a patched interface — Valetudo is the main project — that removes the vendor cloud entirely and exposes MQTT to Home Assistant. Live maps, zone cleaning, fan speed, consumable counters, all on your network. This is the real thing.

If resilience matters to you, aim for Tier 3 and treat Tier 1 as a fallback.

Valetudo: the genuinely local route

Valetudo is open-source firmware-side software that replaces the cloud connection on supported Dreame, Roborock, Viomi and a few other robots. It doesn't replace the robot's core navigation firmware — it hijacks the bit that phones home and gives you a local web UI plus MQTT with Home Assistant auto-discovery.

What you get once it's running:

  • Start, stop, spot and zone cleaning as native HA entities
  • Live map with room segmentation (via the valetudo-map-card or the ICantBelieveItsNotValetudo camera add-on)
  • Fan speed, water flow, mop settings
  • Consumable life sensors — brush, filter, sensors — which are perfect for maintenance reminders
  • No internet dependency at all

The catch is installation. Rooting is model-and-firmware-specific. On many Dreame units it means opening the case, shorting test pads or connecting a USB cable to an internal port, and flashing a patched image. On some models the process is fully documented and takes half an hour; on others it requires soldering, or the current firmware has closed the hole.

Dreame's mid-to-upper range has historically been the most Valetudo-friendly family, and the L10s Ultra generation is well documented in the project's device list.

L10s Ultra Robot Vacuum and Mop
#1

Dreame L10s Ultra Robot Vacuum and Mop

Best for: Mostly hard-floor homes wanting a camera-navigated robot that empties itself and washes and dries its own mops, and happy to use the Dreamehome app

What we like

  • Dreame lists a base station that empties the dustbin, washes the mops, dries them with hot air, refills water and adds cleaning solution
  • Dreame quotes up to 5,300Pa of suction and up to 60 days of hands-free cleaning from the 3L dust bag
  • Navigation uses an RGB camera and 3D structured light, according to Dreame
  • Works with Alexa, Google Assistant and Siri, per Dreame's product page
  • Dust bags and an accessory kit are still listed on Dreame Australia's own store

Worth knowing

  • The dock is large; Dreame gives its dimensions as 423 × 340 × 568 mm
  • Navigation relies on an onboard RGB camera, which some households may not want roaming the home
  • No longer shown in Dreame Australia's current robot vacuum line-up, and Dreame's direct warranty only covers purchases made from dreame.com.au
  • The robot carries an 80mL onboard water tank, so it relies on the dock for refills during larger mopping runs

Before you buy anything specifically to root it, check three things. Look at the exact model number (regional variants differ), the firmware version it ships with, and whether Valetudo's supported robots page lists a working method for that combination. Support is listed model by model. The notes on that page show rootability can hinge on the firmware version and even the hardware revision or manufacturing date, so check it again right before you buy. Buying a unit and finding it shipped with patched firmware is the most common disappointment.

And be clear-eyed about warranty: modifying the firmware may affect the manufacturer's warranty, so check the manufacturer's warranty terms before you start. Your consumer guarantees under the Australian Consumer Law are separate from a manufacturer's warranty (the ACCC explains consumer guarantees), but how they apply to a modified device isn't something to assume either way. Seek advice for your situation. If the vacuum is a $1,500 appliance you can't afford to brick, this isn't the hobby for you.

When the robot stays cloud-tethered

Some brands offer no easy local path. Ecovacs is the clearest example — by default the Home Assistant integration authenticates to Ecovacs' servers and relays everything through them. It exposes plenty of controls, but pull the WAN cable and your automations stop. The Home Assistant integration does let you choose a self-hosted server instead of the cloud during setup (based on the community Bumper project). That comes with its own requirements and limitations, and device support relies on reverse engineering.

Deebot X2 Omni Square Robot Vacuum
#2

Ecovacs Deebot X2 Omni Square Robot Vacuum

Best for: Larger Australian homes with a mix of hard floors and rugs where the owner wants a self-emptying, self-washing robot vacuum and mop that reaches into corners

What we like

  • Square body that Ecovacs says cleans to within about 5 mm of the edge, for better corner coverage
  • OMNI station auto-empties the dust bin, refills water, washes the mop pads with hot water and dries them with hot air, per Ecovacs Australia
  • Ecovacs quotes 8000 Pa suction and a 15 mm mop lift for rugs and carpet
  • Slim 9.5 cm robot height, which Ecovacs says lets it get under sofas and beds
  • Ecovacs Australia lists a 2.5-year warranty

Worth knowing

  • Ecovacs Australia's online store showed it as sold out when we checked, with a newer model suggested instead
  • Station uses dust bags, an ongoing consumable to buy
  • Home Assistant's Ecovacs integration is cloud-based by default and does not list the X2 by name
  • Ecovacs' own pages disagree on the mop-wash water temperature and battery runtime

That's not automatically a dealbreaker. A cloud-connected vacuum with a strong app, good edge-cleaning geometry and a reliable auto-empty dock may still be the better appliance for your house than a rootable one you fight with monthly. Just decide deliberately: are you buying a smart-home component or a floor cleaner that happens to have an app?

If you go cloud, mitigate it:

  • Put the vacuum on an IoT VLAN or guest network so it can reach the internet but not your NAS or cameras
  • Build automations that degrade gracefully — don't make your morning routine depend on a vacuum.start call succeeding
  • Keep a physical button or dock control in the loop for when the API has a bad day

Local triggers matter more than local commands

Here's the part people miss. Even with a cloud vacuum, you can make the decision-making local, which is where most of the reliability lives.

The pattern that works best in Australian homes: a Zigbee sensor network feeding Home Assistant, with the vacuum as the actuator. Door sensors on the laundry so the robot doesn't run while the dog's food bowl is out. A presence sensor so it only cleans when the house is empty. A vibration sensor on the dryer. All of that runs on your own coordinator with zero internet.

A USB Zigbee coordinator plugged into whatever runs Home Assistant is the cheapest way in, and it's one of the cheapest, highest-value purchases you'll make for a local-first setup. Prices vary by retailer and model, so check current listings.

Zigbee 3.0 USB Dongle
#3

SONOFF Zigbee 3.0 USB Dongle

Best for: Home Assistant, Zigbee2MQTT or openHAB users who want one local Zigbee coordinator for mixed-brand devices instead of a brand-specific hub

What we like

  • Home Assistant's ZHA documentation lists the ZBDongle-E (EFR32MG21 variant) among its recommended EZSP adapters, and Zigbee2MQTT lists it under its EmberZNet adapters
  • ITEAD says it works with ZHA, Zigbee2MQTT, openHAB, ioBroker, Domoticz and Jeedom, so Zigbee devices can be controlled locally without a vendor cloud
  • Powered from a USB port (ITEAD lists DC 5V, 100mA max), so there is no extra power adapter or mains plug to find a spot for
  • ITEAD says it can be reflashed as a Zigbee router, and Sonoff's dongle guide says Thread (OpenThread RCP) firmware is another option

Worth knowing

  • Not a standalone hub - it needs a computer or single-board machine running Home Assistant, Zigbee2MQTT or similar software
  • ITEAD quotes 30 direct child devices in coordinator mode, so larger networks lean on mains-powered Zigbee routers
  • Windows and macOS need a USB serial driver, according to ITEAD
  • Several similarly named Sonoff dongles exist, so it is easy to buy a different variant from the one a guide assumes

Use a USB 2.0 extension lead to get the dongle away from USB 3 ports and SSDs — the 2.4 GHz interference is real and it's the number one cause of flaky Zigbee networks. Also pick a Zigbee channel that doesn't overlap your Wi-Fi; channels 15, 20 and 25 are the usual safe picks.

Matter won't rescue you yet

Matter 1.2 added a robot vacuum device type, and Matter is local by design — commands travel over your LAN, not a vendor server. On paper that solves everything.

In practice, Matter's vacuum support is still a fairly thin slice compared with a vendor app. Matter 1.2 covered remote start, progress notifications, cleaning modes (dry vacuuming vs wet mopping) and status details such as brush status, errors and charging. Cleaning by room or zone came later, as the service area feature in Matter 1.4, and Home Assistant only added initial support for Matter service areas in 2026.3. Don't expect live maps. Vendors that support Matter typically keep the rich features in their own app. What you actually get depends on the vendor's firmware and your controller, so check the Home Assistant Matter integration page for current support. So Matter gets you reliable local control of the basics, which is genuinely useful for automations, but it isn't a replacement for Valetudo or a full local integration today.

It's worth checking Matter support when buying, because it costs nothing and it's the most likely long-term path to local control without rooting.

A sensible plan

If you want local control and you're starting from scratch:

  1. Decide your tolerance for tinkering before you shop. Be honest.
  2. If it's high, cross-reference the Valetudo supported-devices list against what Australian retailers are actually stocking, and check the model suffix carefully — AU stock sometimes differs from EU listings.
  3. If it's low, buy the best appliance for your floors, accept the cloud integration, isolate it on an IoT network, and put your effort into local Zigbee triggers instead.
  4. Either way, build automations that fail quietly. A vacuum that doesn't start is an annoyance; a morning routine that hangs waiting for a cloud response is a support ticket from your household.

Nothing here involves mains wiring — robot vacuums and docks run from a standard Type I 240 V outlet — so there's no licensed electrician required. If you're adding a dedicated outlet in a cupboard for the dock, that's fixed wiring, and that's a licensed electrician's job under AS/NZS 3000.

FAQs

Does rooting a robot vacuum for Valetudo void the warranty in Australia?

Check the manufacturer's warranty terms before you root: modifying the firmware may affect the manufacturer's warranty. Your consumer guarantees under the Australian Consumer Law are separate from a manufacturer's warranty (the ACCC website explains them), but how they apply to a modified device isn't something to assume either way - seek advice for your situation. If it's an expensive appliance you can't afford to brick, it's not worth the risk.

Can I still automate an Ecovacs vacuum in Home Assistant if it only works through the cloud?

Yes. By default the Home Assistant integration authenticates to Ecovacs' servers and exposes plenty of controls, but everything relays through the internet, so automations stop if your WAN drops. The integration also offers a self-hosted server option during setup, based on the community Bumper project, which has its own requirements and limitations. Isolate it on an IoT VLAN or guest network and build automations that degrade gracefully rather than hanging on a vacuum.start call.

Will a Matter robot vacuum give me full local control without rooting?

Not yet. Matter 1.2 added a robot vacuum device type and is local by design, but support is still a thin slice compared with vendor apps - Matter 1.2 covered start, progress notifications, cleaning modes and status details, cleaning by room or zone (service areas) came with Matter 1.4, and Home Assistant only added initial support for that in 2026.3. Don't expect live maps, and what you get depends on the vendor and your controller. It's reliable local control of the basics, not a Valetudo replacement.

What should I check before buying a vacuum specifically to run Valetudo on it?

Check the exact model number (regional and AU variants differ from EU listings), the firmware version it ships with, and whether Valetudo's supported robots page lists a working rooting method for that exact combination. Support is listed model by model, and rootability can hinge on the firmware version and even the hardware revision or manufacturing date, so check again right before you buy. Units shipping with patched firmware are the most common disappointment.

My Zigbee sensors keep dropping out near my Home Assistant box - what's causing it?

USB 3 ports and SSDs throw 2.4 GHz interference, and that's the single biggest cause of flaky Zigbee networks. Use a USB 2.0 extension lead to move the coordinator dongle well away from those ports, and pick a Zigbee channel that doesn't overlap your Wi-Fi - 15, 20 and 25 are the usual safe picks.

Some of the links in this article are affiliate links. If you buy through one we may earn a commission, at no extra cost to you. It never changes what we recommend — see our affiliate disclosure.

Comments

Leave a comment

Your email address will not be published. Required fields are marked *