Short answer
Aqara Hub M3 can expose supported Aqara child devices to Home Assistant as a Matter Bridge. Home Assistant needs Matter Server, but it does not require Green or Yellow hardware and the M3 does not need another Thread Border Router for its own hub role. Matter only exposes standardized supported device types, so some child devices and Aqara-specific entities can remain missing.
Best path
Finish M3 setup in Aqara Home
Update hub and child-device firmware, confirm every child device works, and select supported devices for Matter sharing.
Add M3 as a Matter Bridge
Use Home Assistant Matter Server to import the bridge and inspect the exposed entities before building automations.
Use direct Zigbee when entity depth matters
A Home Assistant Zigbee coordinator can be the better path when you need device-specific clusters or entities that Matter does not standardize.
Avoid path
Buying another Thread Border Router for M3
Hub M3 already has a Thread Border Router role; missing bridged entities are normally an exposure or device-type issue.
Expecting every Aqara child device through Matter
Matter Bridge support depends on the child's standardized device type, M3 firmware, and Aqara's current bridge implementation.
Resetting the bridge before checking sharing
First confirm child-device selection, supported type, firmware, and stale entity state.
Compatibility summary
| Device | Aqara Hub M3 |
|---|---|
| Platform | Home Assistant |
| Status | Partially compatible |
| Required hubs | Home Assistant Matter Server |
| Hub risk | medium |
| Protocols | Matter, Thread, Zigbee, Wi-Fi, Ethernet, Bluetooth, IR |
| Confidence | high |
| Tested by us | No |
Hub requirement diagnosis
Plan for Home Assistant Matter Server before pairing.
How to connect
- Set up Hub M3 and its child devices in Aqara Home, then update firmware.
- Enable Matter Bridge sharing on M3 and add the bridge to Home Assistant Matter Server.
- Compare exposed entities with Aqara Home before building automations.
What may not work
- Matter Bridge exposes supported standardized device types, not every Aqara child device or vendor-only attribute.
- Firmware, child-device sharing, IR, and Aqara-specific settings remain in Aqara Home.
Child-device entity exposure
Aqara Hub M3 can bridge devices through Matter, but entity exposure varies by child device type and integration path.
| Child device | Matter Bridge | Aqara app | Zigbee2MQTT | ZHA | Entities / missing |
|---|---|---|---|---|---|
Aqara Zigbee contact sensors contact sensor | partial | full | likely-full | partial | Exposed: open/close, battery Missing: Aqara-only settings, some diagnostics Confidence: medium. Basic sensor entities are the safest expectation through Matter Bridge. |
Aqara Zigbee motion sensors motion sensor | partial | full | likely-full | partial | Exposed: motion, battery Missing: advanced sensitivity, vendor diagnostics Confidence: medium. Expect standard motion entities first; advanced options may stay vendor-specific. |
Aqara D1 / wall switches switch | partial | full | likely-full | unknown | Exposed: switch Missing: scene binding, decoupled mode, some multi-gang details Confidence: low. Community reports suggest switches and lights are more likely to expose partial behavior than simple sensors. |
Aqara T1M / Aqara lights light | partial | full | unknown | unknown | Exposed: light control Missing: effects, advanced color modes, Aqara scenes Confidence: low. Matter Bridge may expose core light control but not vendor-specific effects or scenes. |
Aqara scenes and hub automations scene | not-supported | full | not-applicable | not-applicable | Exposed: None confirmed Missing: Aqara scenes, hub automations, IR or hub-specific features Confidence: medium. Do not assume hub-level Aqara automation features become Home Assistant entities through Matter Bridge. |
Verification and evidence
- Verified on
- 2026-07-19
- Evidence level
- Official Aqara and Home Assistant Matter documentation; bridge exposure varies by firmware and child-device type
Use the latest production firmware offered in Aqara Home before evaluating Matter Bridge exposure. No single minimum version is asserted here because availability and supported child-device types change by region and release.
Troubleshooting checklist
- Update Hub M3 and affected child devices in Aqara Home, then record the installed versions.
- Confirm the child device is selected or eligible for Matter Bridge sharing before re-importing the bridge.
- Separate the M3 roles: Zigbee hub, Matter controller, Matter Bridge, and Thread Border Router are not interchangeable.
- Remove and re-add the Matter Bridge only after checking supported device type and stale entity state.
Need a final setup and reliability path?
$1.99 setup + reliability report
Send your scene, devices, hubs, and target ecosystem. We will return what to connect, what hub is missing, which features may not work, reliability risks, fallback checks, and what to buy or avoid.
Related setup paths
FAQ
Does Aqara Hub M3 work with Home Assistant?
Aqara Hub M3 can expose supported Aqara child devices to Home Assistant as a Matter Bridge. Home Assistant needs Matter Server, but it does not require Green or Yellow hardware and the M3 does not need another Thread Border Router for its own hub role. Matter only exposes standardized supported device types, so some child devices and Aqara-specific entities can remain missing.
Does Aqara Hub M3 need a hub?
Usually yes: Home Assistant Matter Server.
What features may be missing in Home Assistant?
Matter Bridge exposes supported standardized device types, not every Aqara child device or vendor-only attribute. Firmware, child-device sharing, IR, and Aqara-specific settings remain in Aqara Home.
Does Aqara Hub M3 need Home Assistant Green or Yellow?
No. Home Assistant needs a supported Matter Server setup to import the M3 Matter Bridge, but Green or Yellow hardware is not mandatory.
Does Aqara Hub M3 need another Thread Border Router?
No for the M3's own role. Hub M3 is itself a Thread Border Router. Missing bridge entities are not fixed by adding another border router.
Why are some M3 child devices missing in Home Assistant?
The device may not be selected for sharing, its Matter device type may not be supported, its capabilities may be vendor-specific, or Home Assistant may still hold stale bridge state.