Matter was supposed to make one device work with every hub. In a home with more than one hub, that promise still breaks in specific, predictable ways.
You scan a device’s Matter code in Apple Home and it pairs in seconds. Feeling optimistic, you try to add the same device to Alexa or Google Home so the rest of the house can control it, and everything stalls. This is the multi-admin problem, and it is the single most common way Matter disappoints people who own more than one smart home platform. The good news is that the failures follow a pattern, and once you know it, most are avoidable.
Quick Answer
Adding a Matter device to a second hub fails because you cannot reuse the original pairing code. The first app has to generate a new code for each additional platform, one device at a time, and the handoff can take several minutes with no guarantee it works. Version mismatches between ecosystems make it worse. The fix is to always pair through your primary app first, then use its share function to create a fresh code for the second hub.
Table of Contents
The core problem: multi-admin is still fragile
Matter lets a single device answer to several controllers at once, a feature called multi-admin. In theory you pair a smart plug once and share it with every app. In practice, you cannot scan the printed code twice. Your first platform becomes the owner, and to add a second one it has to mint a new setup code for that device specifically. As The Verge documented in its reporting on Matter’s ongoing problems, sharing a single device can take upwards of five minutes and still fail, with no clear error to tell you why.
Why version mismatches quietly break pairing
Matter moves fast, and the ecosystems do not move together. Since the standard launched on October 4, 2022, it has shipped six versions, reaching Matter 1.5 in November 2025, according to the Matter version history. The catch is that Apple Home, Alexa, and Google Home each adopt new versions on their own schedule. So a device that needs a 1.4 feature can pair in the platform that supports it and stay invisible in one that is still on 1.2. When two hubs run different versions, a device can desync, turn into a ghost entry in one app, or work in only one place despite showing up in both.
Is there a real failure rate? Not a published one
Here is the honest part, since this is framed as a statistics question. No one, not the Connectivity Standards Alliance nor the platform owners, publishes a Matter pairing failure rate. Anyone quoting a precise percentage is guessing. What you can actually measure is the fragmentation: six spec versions in three years, three major ecosystems on different release timelines, and a device-by-device sharing process rather than a bulk import. Those are the conditions that produce failures, and the volume of owners reporting multi-day pairing struggles tells you the friction is real even without a clean number attached.
The multi-hub failures you will actually hit
Across multi-hub homes, the same handful of breakdowns show up again and again:
- Duplicated or orphaned fabrics. A half-finished share leaves the device claimed by a controller that no longer really manages it, blocking new attempts.
- Wrong controller selected. You try to add the device from the second app directly instead of sharing it from the owner app, and it refuses.
- Version desync. One hub updates to a newer Matter version than the other, and the device drops out of the older one.
- Battery and network chatter. Several controllers polling the same device can drain a battery sensor faster and clog a Thread network.
How to pair a Matter device to a second hub
Do it in this order and the success rate climbs sharply. The key rule: share from the owner, never re-scan the sticker.
- Pair the device to your primary app first by scanning the printed Matter code once.
- In that app, open the device settings and find the share option, labeled something like “Turn on pairing mode,” “Add to another Matter network,” or “Link apps and services.”
- Let it generate a new setup code, then enter that fresh code in the second app. Do not reuse the code on the box.
- Keep both hubs and the device on the same Wi-Fi network, and if it is a Thread device, make sure you have a working Thread border router.
- If it still fails, remove the device from every controller, factory reset it, and start again from the primary app.
What to check before you buy for a multi-hub home
Prevention beats recovery here. Before adding hardware to a home that already runs two ecosystems, confirm the device lists Matter support for the specific version your platforms are on, decide which app will be the primary owner, and keep that choice consistent across the house. A single primary controller with deliberate sharing is far more stable than pairing each device independently into two apps and hoping they agree.
What To Know
- You cannot scan a Matter device’s printed code into two hubs; the first app must generate a new code for the second.
- Sharing one device across platforms can take several minutes and sometimes fails silently.
- Matter has shipped six versions since 2022, and ecosystems adopt them at different times, which causes desync.
- No official Matter pairing failure rate exists, so treat any exact percentage as a guess.
Frequently Asked Questions
Why does my Matter device work in one app but not another?
Usually a version mismatch or an incomplete share. The device may rely on a Matter feature the second platform has not adopted yet, or it was never properly shared from the owner app. Share it again from the primary controller using a freshly generated code.
Can one Matter device really connect to multiple hubs at once?
Yes, through multi-admin, but you add each hub one at a time using a new code from the owner app, not by scanning the original code repeatedly. Expect the process to be slow and to occasionally need a retry.
Do I need the same Matter version on all my hubs?
Not identical, but big gaps cause trouble. If one hub is several versions ahead of another, devices can desync or vanish from the older app. Keeping your hubs updated reduces, though does not eliminate, these mismatches.
What is a fabric in Matter, and why does it matter?
A fabric is a controller’s secure network of Matter devices. Each hub you add creates another fabric on the device. Half-finished shares can leave stale fabrics that block new pairings, which is why a full factory reset often clears a stubborn device.
Is it better to use one hub instead of several?
For reliability, yes. A single primary controller avoids most multi-admin friction. Use multiple hubs only when you genuinely need different ecosystems, and share devices deliberately rather than pairing them into each app separately.
Practical Takeaway
Matter across multiple hubs is workable in 2026, but only if you respect how sharing works: pair once in a primary app, generate new codes for anything else, and keep versions current. Skip the instinct to re-scan the box code in every app, since that is what produces most of the failures. For more smart home and device coverage, browse Visboo’s Technology section, and our look at smart TV privacy controls is a useful companion for anyone building a connected home.