Matter multi-admin: one device in Apple Home and Google Home at once
Updated · Reviewed against the current HomeHubAtlas dataset
Short answer: yes, one Matter device can live in Apple Home, Google Home, and Alexa simultaneously — that's multi-admin, a core Matter feature, not a hack. You pair the device once, then share it from the first app to the others. Each ecosystem gets full control; automations stay per-ecosystem; and most devices support around five fabrics before running out of slots.
Fabrics: how one device serves several masters
When a controller commissions a Matter device, it enrolls it into its fabric — a cryptographic domain with its own credentials. Multi-admin just means the device holds several fabric credentials at once, each ecosystem talking to it directly over your LAN or Thread mesh. No ecosystem proxies another: if the Apple fabric is present, Apple Home controls the device even if Google added it first.
How to actually share a device
- Pair normally into the first ecosystem — scan the Matter QR code in the app of your choice.
- Generate a share code from that app. In Apple Home: accessory settings → "Turn On Pairing Mode". In Google Home: device settings → "Linked Matter apps & services". In Alexa/SmartThings: "Share with other apps" or equivalent.
- Add it in the second app with the new setup code, as if pairing fresh. The device joins the second fabric without leaving the first.
The original QR code usually can't be reused for the second ecosystem while the device is already commissioned — the share flow exists precisely to mint a temporary code.
What carries over, what doesn't
Basic state and control — on/off, level, color, lock/unlock, temperature — behaves identically in every fabric, because it's the same device answering. What does not sync: room assignments, device names (each app keeps its own), scenes, and automations. An automation lives in the ecosystem that owns it, so "sunset → porch light" in Apple Home doesn't exist in Google Home. Vendor-specific extras that live outside the Matter data model (adaptive lighting, energy history, firmware settings) typically stay in the maker's own app — the same caveat covered in the bridges guide.
Limits worth knowing
- Fabric slots. The spec requires at least five supported fabrics; budget devices rarely offer more. A household running Apple + Google + Alexa + the maker's app is already at four.
- Each ecosystem needs its own controller hardware. Sharing into Apple Home still requires an Apple home hub (Apple TV or HomePod); Google needs a Nest hub or speaker — see each hub page for what qualifies.
- Thread devices need a border router reachable by each ecosystem. Since Thread 1.3, border routers can share one mesh, but a device on Apple's Thread network must still be routable when Google's controller calls — the border-router guide covers this.
- Debugging is on you. When a device misbehaves, ecosystems have no view of each other's fabrics. Remove-and-reshare from one app is the usual fix and doesn't disturb the others.
When multi-admin is the right call
Mixed households (iPhone + Android), a voice assistant that differs from your automation brain (Alexa speakers, Home Assistant logic), or a slow migration between ecosystems without a rip-and-replace weekend. Browse the 1,824 Matter-certified devices in the dataset — every one of them supports this by certification requirement — and check hub comparisons to pick the controllers on each side.