Aqara Zigbee Devices in Home Assistant Without the Aqara Hub
Many Aqara Zigbee sensors and switches can join a Home Assistant network directly. You need a supported coordinator and software that understands the exact device; the Aqara hub is optional for this route. Start by checking the model number, because Aqara also sells Wi-Fi and Thread products that use different integrations.
Use a coordinator in place of the Aqara hub
A compatible device can join the Zigbee network managed by ZHA or Zigbee2MQTT. It then reports to Home Assistant through that system. The Aqara Hub M2 route remains an alternative if you prefer keeping supported devices in Aqara Home.
Zigbee compatibility depends on the model
Many newer Aqara products use Zigbee 3.0; older Xiaomi and Aqara devices may use earlier implementations with their own quirks. Sharing the Zigbee radio does not guarantee that every setting or action is understood by every integration. Match the number on the device to the current device definition or handler.
Keep routine control local
With a local coordinator and Home Assistant, supported states and commands can remain within your home. Zigbee2MQTT also needs a broker, which should be local if that is your aim. No Aqara account is needed for this direct pairing path.
Check the actions you build afterwards. A local button can still trigger a cloud service, and remote notifications or software downloads can still need internet access.
Prepare the replacement network
Choose one system to manage the coordinator, establish the network, and pair a single device first. An Aqara hub is not a USB radio adapter for either integration, and a Zigbee device normally belongs to one coordinator’s network at a time.
Choose a supported coordinator
Use the adapter support list for the system you choose. Confirm the exact radio, firmware and connection type; similar product names can hide different chipsets. A supported USB coordinator is convenient near the server, while an Ethernet coordinator can help with placement when its integration supports it.
The Zigbee2MQTT adapter documentation and ZHA documentation describe supported hardware. Leave old CC2531-era adapters out of a new purchasing decision unless you have a specific reason to reuse one.
Set up ZHA or Zigbee2MQTT
ZHA is a Home Assistant integration and controls its coordinator directly. Zigbee2MQTT is a separate service: connect it to a supported coordinator and MQTT broker, then connect Home Assistant’s MQTT integration to that broker and enable discovery.
Home Assistant OS can run Zigbee2MQTT and a broker as apps. A separate server or container installation is also possible; Mosquitto is a common broker, not the only one. Give only one Zigbee service access to a particular radio.
Compare the two paths by device support
| Consideration | ZHA | Zigbee2MQTT |
|---|---|---|
| Setup | Managed within Home Assistant | Separate service and MQTT broker |
| Device support | Check current device handlers | Check the exact device database entry |
| Extra settings | Depends on the device handler | Shown in the device’s Exposes panel |
| Button automations | Device triggers or ZHA events | Discovered MQTT device triggers or MQTT messages |
| OTA updates | Depends on the device and update provider | Depends on the device and available firmware |
| Moving devices | Reset and pair to the chosen network | Reset and pair to the chosen network |
Avoid choosing from a blanket claim that one supports all Aqara devices better. Check the features needed for your own models, especially decoupled buttons, curtain calibration and presence settings.
Move a device from its existing network
Moving a Zigbee device means replacing its current network membership. Note its existing name, rooms and automations before removing it from the old system. A fresh pairing may create different Home Assistant entity IDs.
Use the model’s reset sequence
Follow the exact device instructions. Button location, hold time and confirmation pattern vary between sensors and switches. Do not assume that a five-second hold or three flashes applies to every Aqara product. For a mains switch, use its accessible controls after a proper installation.
Reset only when a new pairing is needed
A device already working on the intended network does not need a reset. When moving from an Aqara hub or another coordinator, remove the old membership where practical and follow the model’s reset and pairing procedure. A reset may also clear device settings, so make a note of those first.
Pair the first device
Choose a nearby battery sensor for the first test. Confirm discovery and state changes before moving on to several devices; that makes a broker or integration problem easier to distinguish from a radio problem.
Open the join window
In Zigbee2MQTT, enable Permit join, then start pairing on the device. In ZHA, open Settings → Devices & services → ZHA and choose Add device. Wait for the interview to finish and close joining when done. The window length depends on the interface and settings.
If an Aqara interview stalls
Check the battery, coordinator firmware and logs. Some battery devices need short button presses to stay awake during the interview; follow their device notes rather than repeatedly doing a long reset. Test again near the coordinator or a known compatible router.
After pairing, test from the final location. A successful interview beside the server does not prove that the device will report reliably across the house.
Find the entities in Home Assistant
ZHA places its devices under the ZHA integration. Zigbee2MQTT devices arrive under MQTT when discovery is enabled and both systems use the same broker. If a device works in Zigbee2MQTT but is missing in Home Assistant, check MQTT connectivity and discovery first.
Open the device, inspect disabled diagnostic entities if needed, and record the actual entity IDs. For a button, perform each intended gesture so its discovered triggers can become available.
Build coverage around the final locations
A Zigbee network has a coordinator, routers and end devices. Battery sensors generally rely on a parent router or coordinator. Network size alone tells you little about whether a sensor has a stable connection in a particular room.
Check which devices really act as routers
Many mains-powered plugs, bulbs and neutral-wire switches can route traffic. No-neutral switches often cannot, despite being connected to mains power. Aqara hubs usually run their own network rather than joining yours as extra routers. Check the exact product’s role.
Keep router devices powered. A bulb on a wall switch that is regularly turned off makes an unreliable route for nearby sensors.
Place the coordinator away from interference
Keep a USB radio away from the server case, USB 3 equipment and nearby Wi-Fi access points. A suitable extension cable can improve placement. Review Wi-Fi and Zigbee channel overlap if the logs show repeated radio problems, rather than changing channels without a reason.
Identify Zigbee, Thread and Wi-Fi products
- Aqara T1 contact and temperature sensors, Cube T1 Pro and Curtain Driver E1 are examples of Zigbee products; check their exact model entries.
- Door and Window Sensor P2 uses Matter over Thread, so it does not pair with a Zigbee coordinator.
- The FP2 uses Wi-Fi and a different Home Assistant integration.
- Dual-protocol products such as the FP300 must be in Zigbee mode for this workflow.
Do not infer a camera or doorbell’s Home Assistant connection from the fact that another Aqara product uses Zigbee.
Frequently asked questions
Can I pair a sensor to an Aqara hub and Zigbee2MQTT together? A Zigbee sensor normally has one network membership. Moving it requires joining the other network.
Will all features appear? Check the device definition and handler. Basic switching support does not guarantee every button action, setting or diagnostic.
Will the Aqara app still control it? A device paired directly to your coordinator is managed there. If keeping Aqara Home features is important, compare the M2 bridge setup before migrating.
Can I operate it offline? Local states and actions can work with the LAN running. Test the complete automation, including its targets and notifications.