Short answer
Missing M3 Matter bridge entities are usually caused by partial Matter Bridge exposure, child devices that are not selected for Matter sharing, firmware gaps, or expectations from Aqara-only features that Matter does not expose.
Next step
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.
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.
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, or flag information that needs another review.
Save the setup path, missing hubs, limitations, and next steps for later.
Tell us which device, hub, or ecosystem should be added to the compatibility library.
Flag outdated, incomplete, or unclear setup guidance so it can be reviewed.
Get a practical checklist for hubs, Thread border routers, Matter pairing, and fallback paths.