When a Matter-over-Thread device joins a hub but then appears as “unsupported,” pairing success and device support are two different checks. Before resetting anything, I capture:
- manufacturer, product, and Matter device type ID when available;
- the Thread border router and commissioning controller;
- hub, app, and firmware versions;
- whether a basic endpoint or control appears;
- the exact error and whether the device works in Apple Home or another controller.
I then keep the stable fabric intact, open pairing mode from the existing controller for multi-admin, add it to the second controller using the newly generated sharing code, and test one basic command before building automations.
If the device works on the same Thread mesh through Apple Home but Aqara reports it as unsupported, Thread reachability is probably fine; the controller’s supported device-type or cluster coverage becomes the primary suspect. This avoids turning a compatibility gap into a pairing outage.
What fields do you record before moving a Matter-over-Thread device between controllers?