Short answer
Aqara Hub M3 can expose supported child devices through Matter Bridge, but Matter bridge exposure does not guarantee every Aqara Zigbee device, switch, light, setting, or entity will appear in Home Assistant.
Next step
Symptoms this page covers
- Some child devices missing
- Only part of the hub appears
- Switches or lights not exposed
- Matter bridge entities incomplete
Likely causes
- The Aqara app has not exposed the specific child device to Matter.
- The child device type is not fully represented through Matter Bridge.
- Home Assistant has imported the bridge but not all bridged endpoints.
- Aqara firmware, Matter bridge support, or Home Assistant Matter support is behind the expected behavior.
Fix checklist
- Confirm the child device works inside the Aqara app first.
- Check whether the child device is explicitly exposed to Matter from the Aqara app.
- Re-open the Matter bridge page in Home Assistant and compare exposed endpoints.
- Update Aqara Hub M3 firmware before retesting entity exposure.
- If local control and entity completeness matter more, compare ZHA or Zigbee2MQTT for that device.
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. |
Avoid these mistakes
- Do not assume every Aqara child device bridged by M3 will expose the same entities as Zigbee2MQTT.
- Do not buy M3 only for Home Assistant entity completeness without checking the target child devices.
- Do not mix up hub features with child-device Matter bridge exposure.
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
Should I factory reset Aqara Hub M3 first?
Usually no. First confirm the controller, hub, network, and integration path. Resetting too early can remove useful evidence about which ecosystem or Thread network currently owns the device.
What should I check before buying another hub?
Check whether you already have the required Matter Controller, Thread Border Router, vendor hub, Zigbee coordinator, and Home Assistant service. Use the linked calculator or diagnostic tool before purchasing extra hardware.
Does Matter expose every feature and entity?
Not always. Matter often exposes standard controls, while advanced settings, vendor-specific features, and some bridged child entities may remain available only through the vendor app or another integration path.
Can SmartHomeCompat guarantee this fix for Home Assistant?
No. These pages are based on official docs, product information, public compatibility data, and community issue patterns. They are designed to narrow the likely setup path and reveal missing pieces.
Should I use Aqara Hub, Matter, or a direct Home Assistant path?
Use Aqara Hub when you want vendor-managed setup and Aqara app features. Use Matter when cross-ecosystem sharing is more important. Use direct Home Assistant paths such as ZHA, Zigbee2MQTT, or HomeKit Controller when local control and entity exposure matter more.
Feedback
Help improve this compatibility data
Smart home compatibility changes quickly. Send a report, request a missing device, flag information that needs another review, or tell us if a paid setup diagnosis would save you time.
Describe your devices, hubs, blocker, reliability risk, and the report output that would save you time.
Tell us which device, hub, bridge, protocol, or ecosystem should be added next.
Flag outdated, incomplete, or unclear setup guidance so it can be reviewed.
Choose a gateway, bridge, interface, or conversion path for KNX, BACnet, Modbus, DALI, Matter, Zigbee, Z-Wave, MQTT, or Home Assistant.