The Matter promise is that any device commissioned on one fabric can also join Apple Home, Google Home, Alexa, and SmartThings without re-pairing. In practice, adding a second controller frequently ejects the first, or the device shows as “unresponsive” in the original app after the second controller finishes commissioning. Multi-Admin failures are the single most common Matter complaint on developer forums as of mid-2026. This guide covers what actually goes wrong, how to spot which layer is at fault, and how to recover without a factory reset.
What Matter Multi-Admin actually promises
Multi-Admin lets a Matter device be enrolled in up to 5 concurrent fabrics. Each fabric is a separate root-of-trust: Apple Home is one fabric, Google Home is another, and each of those has its own key material stored on the device. When you tap “share device” in Apple Home and complete the flow in Google Home, the sharing operation writes new fabric credentials to the device.
The failure modes come from three real limitations that the marketing does not mention:
- The device’s fabric table is not unlimited. Most first-generation Matter devices (Eve, Nanoleaf 2023, some Aqara) advertise 5 fabric slots but only guarantee stable operation with 2 or 3.
- The “sharing” flow assumes both controllers speak the same version of the Matter protocol. If Apple Home is on Matter 1.3 and Google Home is on Matter 1.2, the sharing handshake can partially complete and leave the device in a corrupt commissioning state.
- Devices that support Thread rely on a shared Thread network credential (the operational dataset). Two controllers on different Thread networks that both try to commission the same Thread device force the device to pick one, silently dropping the other.
The signs your Multi-Admin attempt failed
The symptoms differ slightly by controller, but the pattern is consistent:
- The second controller shows “Connected” for the device but state changes made in either app do not sync.
- The first controller starts showing the device as “No Response” or “Unknown state” within a few minutes.
- Rebooting the device restores the first controller and drops the second, or vice-versa, depending on which fabric was written last.
- The Apple Home Companion controller (HomePod, Apple TV) shows the device as removed even though it is still physically present.
The recovery sequence without a factory reset
Full recovery is possible without factory-resetting the device in about 70% of cases. Try these in order:
- In the second controller (the one you added most recently), navigate to the device and select “Remove from this app” or the equivalent. This releases its fabric slot cleanly if the sharing was cleanly written.
- Wait 60 seconds for the device to update its own fabric table. Watch the LED (most Matter devices flash a specific pattern when a fabric is removed).
- Reboot the device by power-cycling it. This forces it to re-read its fabric table and re-announce itself to remaining controllers.
- Check the first controller. If the device now shows a healthy state, stop here. The corrupted state was cleared.
- If the first controller still shows unresponsive, you need to re-commission from the first controller only. In Apple Home, tap the device, Reset Accessory, then re-add using the QR code.
Which controllers play well together in 2026
| Primary controller | Secondary controller | Stability | Notes |
|---|---|---|---|
| Apple Home | Google Home | Good | Sharing flow works reliably on Matter 1.3+ devices |
| Apple Home | Alexa | Fair | Alexa occasionally drops secondary role after Alexa app updates |
| Apple Home | SmartThings | Good | Requires SmartThings Station or v3 hub with Matter enabled |
| Google Home | Alexa | Poor | Both want to be primary; state sync between them is unreliable |
| Home Assistant | Any other | Excellent as secondary | Home Assistant handles secondary role cleanly, less so as primary |
| Three controllers concurrently | Any combination | Poor | Fabric table pressure causes intermittent drops even on capable hardware |
The Thread-specific complication
Matter over Thread devices add a layer: they need a Thread border router on each fabric to route traffic. Apple’s border routers (HomePod, Apple TV 4K) share a Thread network only within the Apple ecosystem. Google’s Nest Hub Max exposes its own Thread network. If a Matter-over-Thread device is commissioned to Apple Home first, then shared to Google Home, the device’s Thread network credential does not automatically update to include Google’s routers.
The Thread standard supports “credential sharing” between border routers via the Thread Group’s certification, but only devices from certified brands (Apple, Google, Nabu Casa’s Home Assistant Yellow, some Nanoleaf) advertise this. Third-party border routers often do not, which forces the Matter device to see only the routers of its original fabric.
The workaround is to explicitly enable Thread Credential Sharing on all your border routers where the toggle exists (in Google Home, Settings, Thread; in Apple Home, tap a HomePod, and enable “Share Thread network”). If your border routers do not support sharing, the device works reliably on the primary fabric only.
Frequently asked questions
How many fabrics can a Matter device actually hold? Spec allows 5. In practice, 2 to 3 is the reliable ceiling on 2023-2024 hardware. 2025 and 2026 devices with more RAM handle 4 to 5 without issue.
Does using Home Assistant as a controller count against the fabric limit? Yes. Home Assistant is a full Matter controller (via the Matter Server) and occupies one fabric slot per commissioned device.
Can I un-share a device without removing it from the primary? Yes. Remove it only from the secondary app. This releases its fabric slot and leaves the primary undisturbed.
Why does re-sharing after removal sometimes fail with “Device already commissioned”? The secondary controller’s app is caching the previous fabric assignment. Close the app fully, wait 30 seconds, and re-open before trying to share again.
Is there a way to see how many fabrics a device is currently in? On Apple Home, no (Apple hides fabric management). On Home Assistant, the Matter integration exposes this in the device diagnostics. On SmartThings, it appears in the device’s advanced properties on the web console.
Does re-commissioning after a failed share lose my device automations? Automations that reference the device by its ID (as most do) will need to be updated to point at the newly commissioned device. Rooms and names usually persist because they are stored per-fabric, but expect to reconnect the device to a few automations manually.
Can I use Matter Multi-Admin to keep an ecosystem I do not fully trust as read-only? No. Matter’s fabric model does not have a read-only role. Any commissioned controller can send state changes. If read-only access is a requirement, keep that ecosystem out of the sharing and expose the device through a bridge instead (a Home Assistant bridge, for example).
