Aqara Zigbee Devices in Home Assistant Without the Aqara Hub

The Aqara Hub is optional. If you own Aqara Zigbee sensors, switches, or plugs, you can pair them directly to Home Assistant using a USB Zigbee coordinator — no Aqara Hub, no Mi Home account, no cloud of any kind. The data stays entirely on your local network.

This article covers the full picture: what hardware you need, how Zigbee2MQTT and ZHA compare for Aqara devices, how to factory-reset devices that were previously on an Aqara Hub, and what to expect when you pair your first device.

Why you do not need the Aqara Hub

Aqara devices use standard Zigbee 3.0

Aqara’s Zigbee lineup — sensors, remotes, switches, plugs — implements the standard Zigbee 3.0 protocol. That means they speak the same radio language as thousands of other Zigbee devices from other manufacturers. The Aqara Hub is just one possible Zigbee coordinator. It happens to be the one Aqara sells, and it ships paired to Mi Home, but nothing about the devices themselves requires it.

Any compatible Zigbee coordinator can act as the network controller. Home Assistant talks to that coordinator through either Zigbee2MQTT or the built-in ZHA integration, and your Aqara devices appear as entities just like they would with any other integration.

What you gain: fully local, no cloud, no Mi Home account

When you route Aqara devices through the Aqara Hub, the hub phones home. Even in the hub’s local mode, time sync and firmware updates pass through Aqara’s servers. With a third-party coordinator and Z2M or ZHA, no traffic ever reaches Aqara’s infrastructure. The Zigbee RF goes from the device to the coordinator, and from there to Home Assistant over your local network — that’s the full data path.

You also drop the dependency on the Aqara app entirely. No Mi Home account. No Aqara Home app. If Aqara’s servers go offline tomorrow, your sensors keep working.

Our Aqara Hub M2 local-control guide covers the hub-based local mode in detail for readers who want to compare. But if hub-free is your goal, continue here.

What you need instead

A Zigbee USB coordinator — which one to buy

You need a USB Zigbee coordinator plugged into the machine running Home Assistant. Two options cover most setups:

Sonoff ZBDongle-E — uses the EFR32MG21 chip. Widely supported in both Zigbee2MQTT and ZHA. Around $20. Good choice if you’re buying new hardware specifically for Aqara devices.

Home Assistant SkyConnect / ZBT-1 — sold by Nabu Casa, designed to run on the same machine as HA OS. Also EFR32MG21-based. If you’re already running Home Assistant OS on a dedicated Pi or mini-PC, this is the path of least resistance since HA recognizes it automatically on plug-in.

Either chip works well with Aqara devices. Avoid older CC2531-based dongles — they’re limited to 20 direct connections and lack the throughput for a larger device count.

One hardware note that affects pairing reliability more than people expect: use a USB extension cable. Plug the dongle into the cable, not directly into the USB port on your server. USB 3.0 ports radiate interference in the 2.4 GHz band that Zigbee shares with Wi-Fi, and a coordinator sitting centimeters from a USB 3.0 port will have range problems. A 1-meter extension moves the antenna into open air and makes a noticeable difference.

Home Assistant with Zigbee2MQTT or ZHA add-on

You need a running Home Assistant instance with either:

• Zigbee2MQTT — a third-party add-on (available in the HA add-on store). Requires the Mosquitto MQTT broker add-on alongside it.
• ZHA (Zigbee Home Automation) — built into Home Assistant. No additional add-ons needed.

Both integrations fully support Aqara Zigbee devices at the basic level. Where they differ matters if you’re planning to use switches or buttons with advanced features.

Zigbee2MQTT vs ZHA — which path for Aqara devices?

For most Aqara sensors (contact, temperature, motion, water leak), both integrations work well and the choice is mostly preference. The gap appears with switches, buttons, and plugs that have firmware-level features Home Assistant exposes as configuration options.

If your devices are primarily sensors, ZHA is a reasonable starting point. It has a simpler setup path, and a contact sensor or temperature sensor does not need decoupled mode or OTA updates.

If you plan to run Aqara wall switches, button controllers, or smart plugs — especially if you want decoupled mode (where the physical button doesn’t directly control the relay) or OTA firmware updates — Z2M is the better long-term choice. The configuration overhead is real but it’s a one-time setup cost.

The device-specific articles in this cluster document which features are Z2M-only vs. ZHA-compatible for each device. Check those if you have a specific device in mind.

If you decide to go the Zigbee2MQTT route, you’ll want to walk through a full Z2M setup from scratch — install the Mosquitto broker add-on first, then the Zigbee2MQTT add-on, and point it at your coordinator’s serial port.

Before you start: factory reset devices that were on the Aqara Hub

This step is mandatory and is the most common cause of pairing failures. Aqara devices retain their previous network credentials — Zigbee channel, PAN ID, network key — after they’re removed from an Aqara Hub via the app. Even if the Aqara app says the device is removed, the device still holds that configuration internally.

A factory reset clears all stored network state and puts the device back into pairing mode. Without it, the device simply won’t respond when you try to pair it to your coordinator.

General reset procedure

Most Aqara devices reset the same way: hold the physical reset button for 5 seconds or more until the LED flashes three times (or rapidly, depending on the model). The device then blinks to indicate it’s in pairing mode and ready to join a new network.

The exact button location and LED behavior vary by device. Check the device-specific articles in this cluster for the reset procedure for your specific model.

If a device was never paired to an Aqara Hub — bought new and never used with Mi Home — no reset is needed. Just open the join window and pair normally.

Why this step cannot be skipped

When you open a join window in Z2M or ZHA and the device blinks, it looks like it’s trying to join. But if the device hasn’t been reset, it’s actually broadcasting on the Aqara Hub’s old channel and PAN ID, not listening for a new coordinator. The coordinator never sees a valid join request. The device eventually stops blinking and goes back to sleep. This looks exactly like a range or compatibility problem — it isn’t.

Factory reset first, every time.

Pairing your first Aqara device

Opening the join window in Z2M and ZHA

In Zigbee2MQTT: go to the Z2M frontend (accessible via the add-on sidebar in HA), click “Permit join (All)” at the top. This opens a 254-second join window across your entire Zigbee mesh. You can also permit joins only through a specific router device for range-limited situations.

In ZHA: go to Settings → Integrations → Zigbee Home Automation → Configure → Add Devices. This opens a similar time-limited join window.

Both interfaces show devices as they pair, in real time. You don’t need to do anything in Home Assistant manually — devices appear as discovered entities once the join completes.

Pairing tips specific to Aqara devices

Hold battery-powered sensors close to the coordinator when pairing. Aqara sensors are aggressive about power saving. During the join sequence, they transmit a join request and then quickly go back to low-power state if no response arrives promptly. If the coordinator is 10 meters away and there are no router devices in between, the sensor may transmit its join request and sleep before the coordinator processes it and responds. Holding the sensor 50–100 cm from the coordinator during the initial pairing sidesteps this entirely.

Re-trigger the reset button if pairing stalls mid-window. If 30 seconds have passed and the device hasn’t appeared in Z2M or ZHA, tap (don’t hold) the reset button again. This re-broadcasts the join request without factory-resetting the device. The join window is still open; the device is just prodding the coordinator again.

Mains-powered devices are easier to pair from their installation location since they don’t have the same sleep constraints as battery sensors. You can often pair a switch or plug in place, then pair the battery sensors from near the coordinator and move them to their final location afterward.

What happens after pairing — entities in Home Assistant

Once a device joins successfully, Z2M and ZHA both create Home Assistant entities automatically via their respective discovery mechanisms. No YAML configuration is needed in modern setups.

In Zigbee2MQTT, the device appears in the Z2M device list immediately. Home Assistant entities are created a few seconds later via MQTT discovery. You’ll find them under the Z2M integration in Settings → Devices & Services.

In ZHA, entities appear in the Devices list under the ZHA integration. The device interview (where ZHA reads the device’s capabilities) runs automatically during pairing.

From here, the device works like any other entity in Home Assistant. You can add it to dashboards, write automations, and check the device log from the integration page.

The device-specific articles in this cluster go into detail on entity naming, useful automations, and quirks to be aware of for individual devices. This article focuses on the pairing pipeline; the per-device articles cover what happens once the device is in.

Common Aqara contact and motion sensors — the Door and Window Sensor T1, or the high-precision motion sensor — are good starting points once your coordinator is up.

Building a reliable Zigbee mesh

Mains-powered Aqara devices as routers

Zigbee is a mesh protocol. Battery-powered devices (sensors, remotes, button controllers) are end devices — they communicate through the nearest router or directly to the coordinator. Mains-powered devices (switches, plugs, hubs) are routers — they relay traffic for other devices.

A small network with only a coordinator and battery sensors works fine for devices in the same room. Once devices are more than 10–15 meters from the coordinator, or separated by thick walls, mesh routing becomes important.

Aqara mains-powered devices route Zigbee traffic automatically once they’re paired. A single Aqara smart plug in a room helps battery sensors in that room reach the coordinator without you doing anything else. You don’t configure routing manually — Zigbee handles it.

An Aqara H1 wall switch is an example of a mains-powered device that functions as a router while doing its main job.

Coordinator placement and USB interference

The coordinator should be in a location where it can reach your mains-powered router devices without dead spots. For most homes, somewhere central works — near the router rack or wherever your HA host lives.

The USB extension cable mentioned earlier is not just a nice-to-have. USB 3.0 generates broadband noise across the 2.4 GHz band — a known issue documented in an Intel white paper and discussed extensively in Z2M and HA community threads. The noise is wideband rather than confined to specific channels, so it can degrade any part of the Zigbee spectrum. Moving the coordinator even 50 cm away from the USB 3.0 port (and especially away from USB 3.0 cables) reduces this interference significantly.

If you’re experiencing random device drops or intermittent pairing failures after a working setup, check coordinator placement before looking at device configuration.

Which Aqara devices are Zigbee? (and which are not)

Not every Aqara device uses Zigbee, and this matters because non-Zigbee devices are out of scope for this guide.

Zigbee (covered here):
– Contact/door sensors (T1, P2, E1 series)
– Motion and presence sensors (T1, P1, FP1 series — note: FP2 is Wi-Fi, not Zigbee)
– Temperature and humidity sensors
– Smart plugs (SP-EUC01 and Zigbee variants)
– Wall switches (H1, D1, E1 series)
– Smart buttons and remotes (WXKG series)
– Vibration sensors
– Water leak sensors
– Cube T1 Pro
– Curtain drivers (ZNCLBL01LM and similar)
– Radiator thermostat E1

Not Zigbee (different setup path required):
– Cameras (G2H, G3, E1, G4 — these are Wi-Fi devices, handled via HomeKit Controller or RTSP)
– FP2 presence sensor (Wi-Fi, handled via HomeKit Controller in HA)
– Newer Matter/Thread devices paired to the M3 Hub
– Any device explicitly listed as “Wi-Fi” in the Aqara product specs

The FP2 is a common source of confusion: it looks like a Zigbee sensor but connects over Wi-Fi. If you’re planning to use an FP2, it requires a different integration path — HomeKit Controller in Home Assistant rather than a Zigbee coordinator.

When in doubt, check the product page for the connectivity type. Aqara lists “Zigbee 3.0” explicitly for Zigbee models.

Frequently asked questions

Can I use Aqara devices with Home Assistant without the Aqara hub?
Yes. Aqara Zigbee devices use standard Zigbee 3.0 and pair directly to any compatible USB coordinator. No Aqara Hub required.

Do I need the Aqara hub to use Aqara sensors locally?
No. The hub is one option, not a requirement. With Z2M or ZHA and a USB coordinator, sensors operate entirely locally — no Aqara servers in the data path.

What is the best Zigbee dongle for Aqara devices?
The Sonoff ZBDongle-E (EFR32MG21) and the Home Assistant SkyConnect / ZBT-1 are both solid choices. Use a USB extension cable with either to keep the antenna away from USB 3.0 interference.

Should I use Zigbee2MQTT or ZHA for Aqara devices?
ZHA for simple sensor setups; Zigbee2MQTT if you need switch decoupled mode, full button action sets, or OTA firmware updates. Both work for basic sensors.

How do I reset an Aqara device to use it without the Aqara hub?
Hold the device’s reset button for 5+ seconds until the LED flashes, then pair it within the coordinator’s join window. The exact button location varies by device — check the device-specific article for your model.

Why won’t my Aqara device pair after resetting?
Common causes: coordinator is too far away (hold the sensor near the coordinator during pairing), USB 3.0 interference (use an extension cable), or the device needs a second tap of the reset button to re-broadcast its join request.

If you’re ready to set up Zigbee2MQTT from scratch, the path is the Mosquitto broker add-on, then the Z2M add-on, then your coordinator’s serial port. Or if you want to compare the hub-based approach before committing, our Aqara Hub M2 local-control guide covers what the M2 gives you that a plain coordinator doesn’t.