Search for Aqara Home Assistant integration methods and you get five different answers. Zigbee2MQTT, ZHA, Matter, HomeKit Controller through a hub, and a telnet-based hub hack distributed through HACS. Plus an “Aqara” entry in Home Assistant’s own integration list that looks like it should settle the question and doesn’t.
This page is the decision layer over the setup guides already on this site. It does not walk through any one setup. It ranks the five paths by a single question that matters if you run a local-first house: how much of the Aqara app, account and cloud do you still depend on once the thing is running?
One framing point up front. Day-to-day control is local on all five paths. Flipping a light or reading a sensor stays on your LAN in every case. The differences are in setup, pairing and firmware updates, which is where the Aqara ecosystem tends to stay involved.
This comparison is a synthesis of guides this site has already published, plus the Home Assistant integration listing. It is not a side-by-side test. No path was run against the others for this piece, so there are no latency or reliability benchmarks here beyond the one figure attributed to the M100 guide.
The short answer
Ranked from least to most Aqara dependence:
| Path | Aqara hub needed | Aqara app or account still involved | What it costs you |
|---|---|---|---|
| 1. Zigbee2MQTT or ZHA with your own coordinator | No | None to set up or run | A USB coordinator, re-pairing, a weaker firmware update story (weakest on ZHA) |
| 2. Matter directly | No, but Thread devices need a Thread border router | None to commission. App only to install firmware updates | Matter-capable devices only, a border router, a small certified roster |
| 3. Hub bridged over Matter | Yes | App and account to register the hub and generate the Matter code, cloud for push notifications and OTA | Hub limits (M100 takes Aqara-branded Zigbee devices only) |
| 4. Hub over HomeKit Controller | Yes | App and account to register the hub, pair children and update firmware | No IR blaster, no pairing or removal from Home Assistant |
| 5. HACS/telnet hub integration | Yes | Same as path 4, plus an unofficial access route | Possible bricking, breaks on firmware updates |
If you are buying new and want the smallest footprint, path 1. If your devices are Matter over Thread and you already run a border router, path 2. If you already own a hub, path 3 or 4 depending on the model. Path 5 is for people who have read the caveats and still want it.
First, what “local” means here
“Local versus cloud” is the wrong axis for Aqara and Home Assistant. A better split has three phases.
Setup is when a device or hub is first paired, commissioned or given a Matter code. Day-to-day is the control and sensor traffic after that. Maintenance is firmware updates and, on some hub paths, push notifications.
The ranking in this article is about setup and maintenance. One fact applies to every hub path: the hub has to be registered once through the Aqara Home app, with an Aqara account and a live internet connection, before any local route exists. For what keeps working when the internet is down, the does Aqara work without internet piece covers it, and the Aqara local-mode privacy policy piece covers what the vendor says about data in that mode.
Path 1, your own Zigbee coordinator
The data path is device to coordinator to Home Assistant, all on your network. No Aqara app, no Aqara account, no Aqara servers. It is the only path of the five that needs none of them to set up and run.
The price is hardware and a bit of discipline. You need a USB Zigbee coordinator. The hub-free setup guide names the Sonoff ZBDongle-E and the Home Assistant SkyConnect as recommended options, and suggests a USB extension cable to keep the dongle away from 2.4 GHz interference. Devices paired somewhere else need a factory reset first.
Then you pick a stack. ZHA is built into Home Assistant and uses quirks to handle vendor-specific behavior. Zigbee2MQTT runs as its own service with an MQTT broker, uses converters, and brings its own frontend and OTA workflow. Neither guarantees full feature parity for every Aqara model, so check the exact model before assuming. And treat a later switch between the two as a re-pairing project, not a setting. The ZHA vs Zigbee2MQTT for Aqara article covers that decision in full.
Firmware updates are the weak spot on this path, and weakest on ZHA. ZHA enables OTA for five manufacturers by default and Aqara is not one of them, which is why the hub-free guide lists Aqara OTA as unsupported there. The ZHA OTA article documents an opt-in z2m provider that points ZHA at Zigbee2MQTT’s firmware index, but this site has not confirmed that it delivers Aqara images through ZHA, and community threads report devices still showing “unknown” after adding it. Zigbee2MQTT’s own OTA covers more Aqara models, though not every one, and a model with no image there has to be updated through the Aqara app.
This path also excludes anything that is not classic Zigbee. Matter/Thread devices belong to path 2, and Wi-Fi devices such as the cameras and the FP2 presence sensor reach Home Assistant through HomeKit Controller directly, per the hub-free guide. If you are mixing Aqara with other Zigbee brands on the same mesh, the mixed-brand router compatibility piece is the one to read. And a few Matter-era devices need a one-time firmware switch before they behave as Zigbee devices, covered in the Thread-to-Zigbee switch article.
Path 2, Matter directly to Home Assistant
This is where the confusing “Aqara” entry comes in. Home Assistant added an Aqara listing in 2024.10, but it is a brand listing that routes to the core Matter integration. It is not a standalone Aqara integration, and it is not an Aqara-cloud integration. The listing is classified as Local Push.
The roster is small. At the time it was checked for our native integration explainer, the page listed 13 certified products, covering a hub, two locks, light bulbs, a light switch, several sensors and a valve controller. Other Matter-capable Aqara devices can still work through the Matter integration without appearing on the list. The official page is at the Home Assistant Aqara listing.
The listing does not cover classic Zigbee devices, and it is a different mechanism from the older Xiaomi Gateway-style integration, so advice written for one does not carry over.
On the privacy side, the listing page says Matter devices work locally, and the account question splits by device role. A Matter end device commissions straight into Home Assistant from its QR or numeric setup code. The P2 sensor guide documents this, with the Aqara Home app needed only to install firmware updates, which cannot be pushed from Home Assistant. A hub acting as a Matter bridge is path 3, and that needs the app first.
The cost this path adds is Thread. A Thread-based Matter device such as the P2 needs a Thread border router on your network. The P2 guide lists an Apple TV, a HomePod mini, and Home Assistant’s SkyConnect running Thread firmware among the options. An Aqara hub that is only a Zigbee coordinator, like the M2, cannot fill that role.
Path 3, an Aqara hub bridged over Matter
If you own a hub, Matter bridging is the modern way to hand its devices to Home Assistant. The details depend on the model. The M100 connects only through Matter bridging. The M3 supports both Matter and HomeKit paths, covered in the M3 bridge guide. The M2 gained a Matter bridge in firmware 4.0.0, but our M2 HomeKit Controller guide documents fewer entities over it, with no plug power readings and no button multi-press events, so HomeKit Controller (path 4) remains the better-documented route for that hub. The hub lineup explainer helps if you are not sure which one you have.
The M100 guide documents the limits well. The hub accepts only Aqara-branded Zigbee devices. Capacity is 20 Aqara Zigbee devices plus 20 Thread devices, counted separately. The Aqara Home app (version 5.1.3 or later, per that article) has to configure the hub and generate the Matter code before Home Assistant can see anything. In VLAN setups, mDNS has to cross network segments, which the IoT VLAN guide covers.
Control runs on the LAN, and so do the Home Assistant automations built on it. The M100 article puts typical latency at 200 to 400 ms, which is that article’s figure and not a benchmark from this comparison. Push notifications and firmware OTA still go through the cloud.
There is also an advanced mode. Advanced Matter bridging exposes Aqara scenes and device-exclusive signals as virtual Matter entities in Home Assistant, described in the advanced bridging article.
Path 4, an Aqara hub over HomeKit Controller
HomeKit Controller talks to the hub over HomeKit over LAN. Setup is local after the pairing step: you enter the hub’s 8-digit code, and the integration discovers its child devices. It needs the same network segment, or mDNS routed across VLANs. If the hub was previously paired in Apple Home, remove it there first, because it can only have one controller.
What still touches Aqara is the setup and maintenance side. Registering the hub, pairing new devices to it, and hub and device firmware updates all go through the Aqara app, per the M2 HomeKit Controller guide. Automations you build in Home Assistant run on your HA server, so they don’t depend on Aqara’s cloud. Automations built in the Aqara app are a separate question. Aqara’s M2 page says local automations keep running when the internet drops, while this site’s hub lineup explainer reports M2 app automations as processed server-side. The two may describe different rule types, so test any app rule you depend on with the hub’s internet access blocked.
The limits are real. The IR blaster is not exposed. Zigbee devices cannot be paired to or removed from the hub from within Home Assistant, only from the Aqara app. The alarm panel cannot be set directly to “off”. And the M2 does not support the multicast protocol that the Xiaomi-gateway-style integration relies on, which is one more reason not to mix up the two.
Path 5, the telnet and HACS route
The HACS hub integration gets you things the other hub paths do not. IR blaster control, more reliable button events, and richer presence-sensor data than HomeKit Controller provides. It also stays on the local network.
The catch is how it gets there. Enabling telnet access on the hub is unofficial, and per the HACS telnet article, Lumi has been disabling the script the integration depends on in newer firmware. Updating the hub afterwards can break access again, with no guaranteed workaround. The project’s supported-hardware list is mostly CN-firmware models, with the M2 and H1 reached only by flashing modified firmware. Depending on the model, getting in means a firmware downgrade, a USB-stick flash or wiring out the UART pins. The M2 and H1 route is the riskiest, with a real chance of bricking the hub, and success is not guaranteed even after a correct flash.
This route involves modifying hub hardware or firmware. This article does not cover any flashing or soldering steps. Read the full linked article before deciding, and expect to lose the hub’s warranty and possibly the hub.
The conservative recommendation in that article is HomeKit Controller for baseline control, plus a separate IR bridge if you need infrared. That is this site’s position here too. The extra entities are rarely worth betting a working hub on, unless you specifically need the IR blaster and have already decided that a bricked hub is an acceptable loss.
Which path fits which reader
| You are | Look at | Why |
|---|---|---|
| Buying new, want minimal Aqara dependence | Path 1 | No hub, no app, no account |
| Running Thread-based Matter devices with a border router | Path 2 | Direct commissioning, app only for firmware |
| Already own an M100 or M3 | Path 3 | Matter bridge is the supported route, accept app-based setup |
| Already own an M2 | Path 4 | HomeKit Controller exposes more than its firmware-4.0.0 Matter bridge |
| Running a segmented IoT VLAN | Path 1, or path 3/4 with mDNS routed | Hub paths need discovery to cross segments |
| Want every last entity and accept risk | Path 5, after reading the caveats | Extra data, unofficial access |
If you are not sure which of your devices need a hub in the first place, the hub requirements guide sorts them by Zigbee, Bluetooth and Wi-Fi.
One reading of the pattern, which is this site’s synthesis and not something Aqara documents. The more the hub sits between a device and Home Assistant, the more the Aqara app and cloud stay involved for setup and updates, even though control is local throughout. That is why path 1 ranks first and the hub paths follow in order of how much they route through Aqara’s tooling.
FAQ
Do I need an Aqara hub to use Aqara sensors with Home Assistant?
No, for Zigbee devices. A Zigbee2MQTT or ZHA coordinator replaces the hub entirely, with the exclusions listed under path 1. Matter-over-Thread devices also skip the hub, but need a Thread border router instead.
Is Aqara’s Home Assistant integration local or cloud?
The “Aqara” listing is a Matter brand listing, classified Local Push. It is not an Aqara-cloud integration.
Zigbee2MQTT, ZHA or Matter for Aqara, which is best?
For the least Aqara dependence, Zigbee2MQTT or ZHA. Matter covers only Matter-capable devices and a short certified roster. Between the two Zigbee stacks, see the dedicated comparison linked under path 1.
Can I use the Aqara app and Home Assistant at the same time?
On the hub paths, yes. The app stays the place for pairing, removal and firmware, while Home Assistant handles control. On path 2 the app returns only for firmware updates. With your own coordinator (path 1), the app is out of the loop for nearly every model.
Does an Aqara hub work with Home Assistant during an internet outage?
Local control continues on the hub paths, and Home Assistant automations keep running because they live on your HA server. Whether automations built in the Aqara app survive depends on the hub and the rule, so test the ones you rely on. Push notifications and OTA updates need the cloud. The outage behavior article has the detail.
What this piece verified
All five paths were checked against this site’s published guides and the Home Assistant Aqara listing, both re-read on 2026-10-03, with the Matter account, ZHA OTA and M2 points rechecked on 2026-10-08. No path was tested side by side for this article. Path 1 is the only one that needs no Aqara app, account or server to set up and run, and path 2 brings the app back only for firmware updates. Two points stay open: whether ZHA’s opt-in z2m provider delivers Aqara firmware, and which Aqara-app automations an M2 runs locally during an outage.
Whether Home Assistant’s certified Aqara roster grows beyond the 13 products listed when this was checked is worth watching, because a longer list would make path 2 a realistic default instead of a niche option.