Matter fabric & multi-admin
A Matter fabric is one ecosystem’s trust domain: the set of devices and controllers sharing security credentials, such as your Apple Home. Multi-admin is the Matter feature that lets a single device join several fabrics at once — the same plug can live in Apple Home and Google Home simultaneously, each with local control, no re-pairing.
When you commission a device, the controller installs its fabric’s certificate on the device. Multi-admin works by having the first ecosystem open a temporary commissioning window and hand you a fresh pairing code (“share” or “pair with another app” in most apps); the second ecosystem then adds its own credentials alongside the first. The spec requires devices to support at least five fabrics.
Multi-admin is genuinely useful in mixed households — iPhone and Android, or Alexa voice with Apple automations — because each fabric talks to the device directly and locally, not through the other ecosystem’s cloud. The limits: automations and scenes do not sync across fabrics (each ecosystem keeps its own), and removing the device from one fabric leaves the others intact, which occasionally surprises people expecting a factory reset.
| Minimum fabrics per device | 5, required by the Matter specification |
|---|---|
| Credential installed per fabric | A Node Operational Certificate signed by that ecosystem’s root CA |
| Sharing mechanism | The first admin opens a temporary commissioning window and mints a fresh setup code |
| Commissioning window | Time-limited, typically about 15 minutes, then it closes on its own |
| What syncs between fabrics | Device state only — never names, rooms, scenes, or automations |
| Removing the last fabric | Returns the device to a factory-fresh, commissionable state |
What a fabric is made of
A fabric is a certificate hierarchy. Each ecosystem operates a root certificate authority; when it commissions a device it issues that device a Node Operational Certificate carrying a fabric ID and a node ID unique within the fabric. All subsequent traffic runs over CASE sessions authenticated with those certificates, which is why control is genuinely local — the device and the controller prove who they are to each other without a cloud in the loop.
Each fabric also gets its own access control list on the device. Apple’s controllers can only act with the privileges Apple’s fabric entry grants; Google’s cannot see or edit Apple’s entries. That isolation is the whole point: adding a second ecosystem does not weaken the first, and a compromised controller cannot silently take over the others.
The device keeps one fabric table with a small number of slots. Slot count, not bandwidth or CPU, is the resource multi-admin consumes, and it is the one that runs out.
How sharing actually works
The printed QR code commissions a device exactly once. To add a second ecosystem, an existing admin opens a temporary commissioning window on the device and generates a new setup code for it — Apple Home calls this “Turn On Pairing Mode”, Google Home files it under “Linked Matter apps & services”, Alexa and SmartThings use some variant of “share with other apps”. The window is time-limited, so if you wander off mid-process you will need to start again.
The second ecosystem then runs a normal commissioning flow against that temporary code, installs its own operational certificate alongside the first, and starts talking to the device directly. Nothing proxies through the first ecosystem, and the first ecosystem does not need to stay online for the second to work.
Matter 1.4 added Fabric Sync, a mechanism for ecosystems to share devices between themselves automatically rather than making you shuttle codes around. It is specified and shipping in some stacks, but as of mid-2026 the manual share flow is still the one that works everywhere, so that is the one worth learning.
Where multi-admin disappoints people
Nothing above device state crosses a fabric boundary. Names, room assignments, scenes, favourites, and automations all live in the ecosystem that created them, so a device shared into three apps needs organising three times. Pick one ecosystem as the automation brain and treat the rest as remote controls — trying to maintain parallel automations across fabrics is how households end up with lights that fight each other.
The five-slot minimum arrives sooner than expected. Apple, Google, Alexa, the manufacturer’s own app, and a Home Assistant instance is five, and budget devices rarely implement more than the minimum. A device that refuses to join one more ecosystem is usually out of slots rather than broken; removing a fabric you no longer use frees one.
Removal semantics also catch people. Deleting a device from one app removes only that fabric’s credential — the device stays fully functional everywhere else, which looks like a failed removal if you expected a reset. Removing the last remaining fabric is what returns it to factory-fresh state, and a device you are selling or giving away should be reset for exactly that reason.
Frequently asked questions
How many ecosystems can one Matter device join at once?
At least five, because the specification requires devices to support five fabrics, and most budget hardware implements exactly that minimum. Each ecosystem — Apple Home, Google Home, Alexa, SmartThings, Home Assistant, the maker’s own app — consumes one slot. Higher-end devices sometimes support more, but there is no way to tell from the box.
Does adding a device to a second ecosystem break the first?
No. Each fabric holds its own credentials and access control entries, and both ecosystems talk to the device directly and locally. The first ecosystem does not even need to be online for the second to work. What you will notice is that names and rooms have to be set up again in the second app.
Do automations sync between Apple Home and Google Home?
No, and this is the single most common disappointment with multi-admin. Automations, scenes, room structure, and device names are ecosystem-local. A sunset-triggered porch light configured in Apple Home does not exist in Google Home. Only the live device state — on/off, brightness, lock status — is shared, because it is the same physical device answering both.
Why can I not reuse the original QR code for a second ecosystem?
The printed code is consumed by the first commissioning. After that the device is no longer openly commissionable — which is a security property, not a limitation. An existing admin has to explicitly open a temporary window and issue a fresh code, which proves that whoever is adding the second ecosystem already has legitimate control of the device.
How do I remove a device from just one ecosystem?
Delete it in that ecosystem’s app. That controller sends a remove-fabric command for its own slot and nothing else changes; the device keeps working in every other ecosystem. To fully reset a device, remove it from every ecosystem or use the manufacturer’s factory-reset procedure, then re-scan the original code.