Aqara Zigbee child missing in another platform: check the documented prerequisites in order, then retry only the affected path.
Start with these checks
Aqara Home can show a Zigbee child even when the hub does not export that child type or feature through Matter. Verify the child-to-hub relationship, then the hub’s export table, then the target controller’s device type support. These are three separate checks.
- Verify local vendor pairing.
- Check supported child export list and firmware.
- Check target platform endpoint type.
Stop when you find the first unmet requirement. Fix it and try pairing again before changing the next variable.
How to interpret the outcome
Bridge support is model- and feature-specific.
A failed path does not prove every alternative path is unsupported. For example, a missing direct radio may still leave a separately documented bridge or cloud route.
Avoid these risky shortcuts
- Assume arbitrary Zigbee-brand interoperability
Relevant model records
Official references
- Aqara — Hub M3 integration roles Reviewed 2026-10-30
- Aqara — U100 and M100 official bundle Reviewed 2026-10-30
- Aqara — Smart Lock U50 introduction Reviewed 2026-10-30
These are evidence-based editorial checks, not a diagnosis of your individual home network.