The Aqara Hub M3 combines Zigbee, Matter, and Thread border routing in one puck — convenient until devices start vanishing from the mesh without you deleting them. Eviction in this context means Thread children lose their parent relationship with the M3 and wander until they find another router or go silent. Automations miss triggers; Aqara Home shows sensors offline while Apple Home still sees them, or vice versa.

Eviction is rarely malicious firmware behavior. It is usually table limits, competing border routers, or the M3 rebooting when Zigbee traffic spikes.

How eviction shows up in Aqara homes

Door and motion sensors that hung on the M3 yesterday now list a distant HomePod as parent — or no parent at all. Devices reappear after hub reboot, then drop again when the M3 handles Zigbee-heavy scenes.

You recently added a second Thread border router (Apple TV, Nest, Home Assistant OTBR) and instability began without moving sensors.

Hub M3 feels warm, or its LED pattern changes during eviction events — note timing.

Safe first steps

Update the Hub M3 firmware through Aqara Home before changing Thread settings. Aqara ships Thread stability fixes on a different cadence than Zigbee device support.

Place the M3 out in the open, not inside a metal networking cabinet. Thread radios need the same breathing room Wi-Fi does.

If you do not need the M3 as your only border router, decide which hub owns Thread for each room. Mixed ownership without planning causes eviction-like hopping.

Fixes that reduce eviction

Limit simultaneous mesh heals: pairing ten Zigbee devices while Thread sensors poll heavily can starve the M3 CPU. Stage pairing sessions.

Re-parent sensors deliberately: move evicted sensors near the M3 for an hour after hub reboot so they reattach locally before you rely on distant Apple or Google routers.

Remove duplicate Matter/Thread entries in Apple Home or Google Home after failed Aqara migrations. Duplicates force radios to hunt phantom routes.

Power and network: use the factory power adapter, not a marginal USB port on a switch. The M3 should sit on the same IPv6-capable LAN documented in Aqara’s setup guide.

Factory reset only for the hub when documented: resetting the M3 wipes Zigbee and Thread datasets — plan to re-pair affected devices from Aqara’s published order.

When to stop DIY

If the M3 reboots during non-smart-home use (audio alerts, LED faults) contact Aqara support — eviction may be a symptom of hardware fault.

Do not flash unofficial hub firmware to “unlock” Thread tables.

Verify eviction stopped

Monitor three sensors that previously dropped: one beside the M3, one mid-range, one far. They should stay online through a Zigbee scene that runs hourly and through one intentional M3 power cycle. Eviction is resolved when parents stay stable for forty-eight hours without manual re-pair.

Official sources