Short answer
Missing Aqara M3 Matter Bridge entities usually mean the bridge is paired but the child device was not exposed to Matter, the child-device type is not supported by Aqara's bridge path, Home Assistant has stale Matter import state, or the missing feature is Aqara-specific and not standardized by Matter.
Next step
Diagnosis table
Start with the symptom that matches your setup. This avoids unnecessary factory resets when the real issue is a controller, border router, network, or entity exposure path.
| Symptom | Likely cause | What to check | Fix | Tool |
|---|---|---|---|---|
| M3 bridge appears but child devices are missing | The child devices were not selected for Matter sharing or are not supported by Aqara's bridge path. | Open the Aqara app and review the Matter sharing or bridge exposure list for the exact child devices. | Expose the selected child devices again, update Hub M3 firmware, then reload the Home Assistant Matter integration. | Open |
| Home Assistant entities differ from the Aqara app | Matter Bridge exposes standard clusters, not every Aqara app feature or vendor-specific setting. | Compare each expected feature against the Home Assistant entity list and note which features are Aqara-only. | Use Matter Bridge for standard entities, but keep Aqara app or a direct Zigbee path for feature-complete control. | Open |
| Bridge endpoint exists but entities stay stale | Home Assistant Matter state is stale after firmware, exposure, or child-device changes. | Record the existing entities, automations, and bridge state before removing anything. | Reload the Matter integration or restart Matter Server after documenting state; avoid factory reset as the first step. | Open |
| Automations need child devices that the bridge does not expose | The Matter Bridge path is the wrong path for that automation requirement. | Identify whether the automation needs vendor-specific settings, complete sensor attributes, or faster local events. | Evaluate ZHA, Zigbee2MQTT, or another direct Home Assistant path before adding more bridged devices. | Open |
Symptoms this page covers
- Matter bridge appears but child devices missing
- Only some entities appear
- Aqara-only settings unavailable
Likely causes
- The Aqara app did not expose selected child devices to Matter.
- The child device is not supported by Aqara's Matter bridge path.
- The target ecosystem imports fewer capabilities than the Aqara app shows.
- Matter Bridge exposes standard capabilities, not every vendor-specific setting.
Fix checklist
- Open the Aqara app and confirm which child devices are exposed to Matter.
- Update Hub M3 firmware and retry bridge exposure.
- Remove and re-add only after documenting which child devices were visible.
- Compare Home Assistant Matter exposure against the same bridge in Apple Home or Google Home if available.
- For automations that need complete entities, evaluate direct Zigbee coordinator paths.
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 treat Matter Bridge as a full replacement for every Aqara app feature.
- Do not assume a successful bridge pairing means all child devices are supported.
- Do not create automations before confirming the final exposed entity list.
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
Why does Home Assistant see Aqara Hub M3 but not the child devices?
The M3 bridge can be paired while specific child devices are not selected for Matter sharing, not supported by the bridge path, or not imported cleanly by Home Assistant.
Does Matter Bridge expose every Aqara entity?
No. Matter Bridge usually exposes standardized capabilities. Aqara-only settings, diagnostics, and some child-device features can remain in the Aqara app or require a different Home Assistant path.
Should I reset Aqara Hub M3 when entities are missing?
Usually no. First document which child devices are visible, check the Aqara Matter sharing list, update firmware, and reload Home Assistant Matter. Reset only after you know the bridge exposure path is wrong.
When is direct Zigbee better than Aqara M3 Matter Bridge?
Direct Zigbee is often better when automations depend on complete local entities, advanced attributes, or features that the Matter Bridge does not expose.
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.