Can the same Matter device be in Apple Home and Google Home?
Yes, through a Matter feature called multi-admin. A device commissioned into one ecosystem is shared with a second by having the first controller open a commissioning window, which produces a fresh pairing code the second app uses. The device then belongs to both fabrics at once. The ceiling is the device's own fabric table capacity, a per-device implementation limit rather than a fixed platform rule.
Last checked: against CSA Matter Handbook (The Fabric), Silicon Labs Matter 2.7.0 multi-controller documentation, Nordic nRF Connect SDK 2.9.0 Matter multiple fabrics
What multi-admin is
The Connectivity Standards Alliance's own handbook states that nodes "may also be commissioned on more than one Fabric," and notes this capability is "often referred to as multi-admin." A fabric is one ecosystem's Matter network. A device on two fabrics is controlled independently by both, with neither acting as a gateway for the other.
This is a property of the standard, not a feature any one platform grants. It is why a Matter device does not force the choice that a HomeKit-only or Alexa-only device forces.
How the sharing actually happens
Both Silicon Labs and Nordic Semiconductor document the same sequence, and their wording agrees:
- Commission the device into the first ecosystem normally, using the pairing code on the device or its packaging.
- Open a commissioning window from the first ecosystem's controller. Nordic's documentation puts it as: "the administrator of the fabric in which the node is already present must open the commissioning window that allows the commissioner of another fabric to join the node to its fabric."
- Use the new code in the second app. Silicon Labs describes the open-commissioning-window command generating an 11-digit pairing code for the second ecosystem's controller.
In consumer apps this is surfaced as a "share" or "add to another platform" action rather than as a command, but the underlying mechanism is the same.
What multi-admin does not give you
Three limits are worth naming, because each one produces a surprise that reads like a fault:
- Feature parity is not inherited. Membership in a second fabric says nothing about which attributes that platform's app will display. A device can report an attribute that one ecosystem renders and another ignores.
- Thread credentials are not shared by joining. A Matter-over-Thread device needs a border router whose Thread credentials the commissioning ecosystem can reach. Home Assistant's documentation, for example, names specific qualifying border routers rather than treating any border router as sufficient.
- The device sets the ceiling. Fabric capacity is implemented in the device firmware and exposed through the Operational Credentials cluster. A low-cost sensor and a mains-powered hub-class device need not offer the same number of slots.
On the "five fabrics" figure
A specific number — most often five — circulates widely for how many ecosystems a Matter device accepts. On 23 September 2026 that figure could not be traced to a primary specification source that is publicly readable: the CSA's own handbook describes multi-admin without stating a minimum, and neither the Silicon Labs nor the Nordic Semiconductor documentation cited here gives a number.
The honest statement is therefore the structural one: the limit exists, it is defined per device through the fabric table and the SupportedFabrics attribute, and a buyer who needs a specific number should look for it in that device's own documentation rather than assume a universal value.
Related questions
Is the original pairing code reused?
No. Silicon Labs' documentation describes the first fabric's controller opening a commissioning window, which generates an 11-digit pairing code for the second ecosystem's controller to use. The code on the device's label is for the initial commissioning.
Does the second ecosystem see all the same features?
Not necessarily. Multi-admin governs membership, not feature exposure. Each platform surfaces only the Matter clusters it has implemented, so the same device can present different capabilities in each app.
How many ecosystems can a device join?
The Matter specification defines the limit through the fabric table and the Operational Credentials cluster's SupportedFabrics attribute, which is a per-device value. Figures circulating online for a universal minimum could not be confirmed against a primary specification source on 2026-09-23, so no number is asserted here.