Short answer
Aqara Hub M3 is works with Aqara. For most users, the practical path is to add m3 directly in aqara home.
Compatibility summary
| Device | Aqara Hub M3 |
|---|---|
| Platform | Aqara |
| Status | Works |
| Required hubs | No extra hub identified |
| Hub risk | medium |
| Protocols | Matter, Thread, Zigbee, Wi-Fi, Ethernet, Bluetooth, IR |
| Confidence | high |
| Tested by us | No |
Hub requirement diagnosis
No extra hub is modeled for the primary path, but your ecosystem controller still matters.
How to connect
- Add M3 directly in Aqara Home.
- Pair supported Aqara Zigbee and Matter child devices.
- Configure local automations, bridge sharing, and firmware in Aqara Home.
What may not work
- No extra hub is required; third-party Matter device support still varies by device type and firmware.
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.
FAQ
Does Aqara Hub M3 work with Aqara?
Works. The best path is: Add M3 directly in Aqara Home. Pair supported Aqara Zigbee and Matter child devices. Configure local automations, bridge sharing, and firmware in Aqara Home.
Does Aqara Hub M3 need a hub?
No extra hub was identified for this connection path, but controller requirements can still depend on your home setup.
What features may be missing in Aqara?
No extra hub is required; third-party Matter device support still varies by device type and firmware.