Using Aqara with Home Assistant

Ownership determines where a device is commissioned, updated and diagnosed. In an Aqara-owned design, Zigbee devices join an Aqara hub and remain visible in Aqara Home. Home Assistant receives a supported subset through Matter or another bridge path. Aqara Home remains the place for firmware, calibration and advanced manufacturer settings.

In a Home Assistant-owned Zigbee design, a compatible coordinator forms the Zigbee network and devices pair directly to Zigbee Home Automation, commonly called ZHA. The Aqara hub is not in that control path. A Zigbee device can belong to only one Zigbee network, so moving it requires a reset, re-pairing and reconstruction of automations.

A mixed design is normal: Aqara hubs can own locks and devices that benefit from manufacturer functions, while selected sensors join Home Assistant directly. Document the boundary by room and model so a future fault is not investigated in the wrong app.

Home Assistant's Matter integration runs a Matter controller and communicates with Matter devices over the local IP network. A compatible Aqara hub can act as a Matter bridge, translating supported Aqara Zigbee child devices into Matter device types without changing the radio network those devices use.

Add or share the Aqara bridge using the commissioning flow provided by the current controller. If the bridge is already in Apple Home, Google Home or another Matter fabric, use that platform's share or multi-admin process to obtain a new pairing code rather than resetting the hub. The phone, Home Assistant Matter server and bridge need working local-network discovery and IPv6 connectivity.

Matter is intentionally a common feature layer. A contact sensor, temperature sensor, light or switch may map cleanly; specialised settings, camera functions, complex button events or manufacturer-specific modes may not. Compare the actual entities after commissioning before migrating automations.

Home Assistant's HomeKit Device integration can pair with compatible HomeKit accessories over Ethernet, Wi-Fi, Bluetooth or Thread. This is a local integration and does not require an Apple online account for operation. Some Aqara hubs and cameras present HomeKit bridges or accessories that Home Assistant can discover.

Home Assistant's official instructions require the accessory to be unpaired from another HomeKit controller before Home Assistant can claim it. For an Aqara hub already serving a household through Apple Home, removing it may also remove child accessories and existing Apple automations. Do not use this route merely because it appears in discovery.

After Home Assistant owns the HomeKit accessory, its HomeKit Bridge integration can expose selected Home Assistant entities back to Apple Home. That creates a deliberate controller chain and should be documented. Matter multi-admin is usually cleaner when the Aqara bridge supports the required device types and the aim is to keep both controllers.

ZHA uses a compatible Zigbee coordinator connected to Home Assistant. It forms one Zigbee network and can pair devices from several manufacturers. Mains-powered router devices extend that network; battery sensors are usually end devices and do not repeat traffic.

Direct pairing removes the Aqara hub and Matter bridge from the path. It can provide local control and detailed Home Assistant automations, but Aqara Home firmware updates, calibration screens and manufacturer support may no longer apply. ZHA relies on standard Zigbee behaviour plus device-specific handlers, called quirks, where products use non-standard clusters or behaviour.

Home Assistant's ZHA documentation specifically notes compatibility issues between some Xiaomi/Aqara devices and certain third-party Zigbee routers. Build the mesh with recommended coordinator hardware and compatible powered routers, pair devices in their final locations, and confirm every required sensor, button and control event before scaling the design.

Home Assistant's community includes custom integrations for various Aqara or Xiaomi gateways and cloud APIs. These can expose functions that a standard bridge does not, but they are not the same as an official Home Assistant integration or an Aqara-supported interface.

A custom integration may depend on undocumented local tokens, cloud endpoints, specific firmware or a volunteer maintainer. Home Assistant, Aqara firmware or account changes can break it. Read the repository's supported-model list, open issues and release history before making it the only path for lighting, access or security automations.

Install community code through a controlled process, back up before updates and avoid automatic upgrades without review. If the integration stops working, the homeowner—not Aqara support or Home Assistant's core team—owns the diagnosis unless the maintainer provides a fix.

Supported Aqara cameras such as G5 Pro, G100 and G350 provide RTSP streams that local software can consume. RTSP can feed a Home Assistant camera entity or a dedicated recorder such as Frigate, but the stream does not automatically import Aqara Home AI events, cloud history or every PTZ control.

HomeKit camera support and Matter camera support are separate from RTSP. Home Assistant's HomeKit Bridge does not provide HomeKit Secure Video, and a local stream does not create cloud retention. Decide where video is recorded, who can view it and what happens when Home Assistant is unavailable.

Keep camera credentials unique and restrict the stream to trusted local networks. A recorder needs sustained storage, time synchronisation and power protection. Treat camera integration as a security system rather than a decorative dashboard tile.

Use Aqara Home for settings that belong to the product: firmware, sensitivity, detection zones, curtain calibration, lock credentials and camera options. Use Home Assistant for cross-brand logic, dashboards and automations only after the required entities are verified.

Avoid creating the same rule in both systems. If Aqara Home turns a light off after two minutes while Home Assistant keeps it on for presence, the conflict looks like unreliable hardware. Record the owner of every important automation and keep one tested manual fallback.

Security-sensitive actions deserve conservative design. Do not expose lock, alarm or camera controls broadly merely because an integration makes an entity available. Review user permissions, remote access, backups and update practice as part of commissioning.

Home Assistant is well suited to technically engaged owners who want cross-brand logic, local dashboards, detailed history and control of their own automation server. The flexibility is real because the owner operates the controller, networking, backups and update process.

For a household that wants manufacturer support and minimal maintenance, Aqara Home plus Apple Home, Google Home or Alexa may be the more supportable architecture. Home Assistant can be added later through Matter without moving every Zigbee device on the first day.

Start with a non-critical room, document the route, and test restarts and internet outages. Expand only after the owner can identify which system should be checked when a device becomes unavailable.