Joint Fabric in Matter 1.6 Explained (Multi-Ecosystem Made Easy)
Joint Fabric is the single best feature in Matter 1.6, announced by the CSA yesterday (June 17, 2026). It finally solves the problem that’s driven multi-ecosystem households crazy since Matter launched: setting up every device multiple times for each platform.
Here’s exactly how it works, how it differs from what we had before, and when you’ll actually be able to use it.
What Joint Fabric Actually Does
Right now, if you want a smart light controlled by both Apple Home and Google Home, you commission it to Apple Home (creating one fabric), then separately commission it to Google Home (creating a second fabric). Each fabric is an independent connection. The device has to maintain both, each counts against its fabric limit, and if one breaks, the other doesn’t know about it.
Joint Fabric replaces this entire model.
With Joint Fabric, multiple ecosystems (Apple Home, Google Home, Alexa, SmartThings, Home Assistant) co-administer a single shared Matter network. There’s a central Datastore that holds the network configuration. Any authorized controller can manage devices on this shared fabric. Adding or removing a platform as an administrator is handled at the fabric level, completely independent of individual devices.
You set up a device once. It joins one fabric. Every authorized platform can immediately see it, control it, and include it in automations. One fabric slot used. One setup process. Full access from everywhere.
How the Central Datastore Works
The Datastore is the key architectural piece. Think of it as the shared truth about your network. It knows:
- Which devices are on the fabric
- Which controllers/ecosystems are authorized administrators
- Network credentials and security material
- Device configurations and capabilities
When Google Home wants to add itself as a controller, it talks to the Datastore, not to every individual device on your network. The Datastore authorizes Google Home, and suddenly Google can see everything. When you remove Alexa as a controller later (maybe you switched to a different voice assistant), the Datastore revokes Alexa’s access. Your devices don’t need to do anything.
This is dramatically simpler than the old model, where adding a new platform meant individually commissioning each device again.
Joint Fabric vs. Enhanced Multi-Admin (Matter 1.4)
This distinction trips people up, so let me be crystal clear.
Enhanced Multi-Admin (Matter 1.4) allowed one platform to grant another platform access to a device. But each platform maintained its own separate fabric connection. If you had Apple Home as fabric 1 and Google Home as fabric 2, Enhanced Multi-Admin made the sharing process smoother. You didn’t have to re-scan QR codes. But fundamentally, you still had two separate fabrics, two separate connections, and two fabric slots used on the device.
Joint Fabric (Matter 1.6) eliminates separate fabrics entirely. There’s one fabric. Multiple platforms share it. One connection. One fabric slot. The platforms don’t each maintain their own link to the device. They share a single link through the Joint Fabric’s central Datastore.
Here’s why that matters practically:
| Aspect | Matter 1.4 Enhanced Multi-Admin | Matter 1.6 Joint Fabric | Winner |
|---|---|---|---|
| Fabric slots used per device | One per platform (2-3 typically) | One total, regardless of platforms | Joint Fabric |
| Setup process | Commission once, share to other platforms individually | Commission once, all authorized platforms see it | Joint Fabric |
| Adding a new platform | Must share access device-by-device | Authorize at fabric level, instant access to all devices | Joint Fabric |
| Removing a platform | Revoke per-device (tedious for large networks) | Revoke at fabric level, one action | Joint Fabric |
| Device firmware requirement | Devices needed to support multi-admin | No device firmware change needed (hub/controller update only) | Joint Fabric |
| Offline behavior | Each platform maintains independent connection | Shared fabric, controllers coordinate through Datastore | Enhanced Multi-Admin (simpler offline) |
| Availability | Available now | Expected 3-6 months for hub updates | Enhanced Multi-Admin (available today) |
The offline behavior point deserves attention. With separate fabrics, each platform has its own direct connection and can operate independently if the network has issues. With Joint Fabric, the platforms coordinate through the shared Datastore. The CSA spec handles disconnection gracefully (controllers can still operate devices they’ve cached), but it’s a different model. Time will tell if this causes issues in practice.
Real-World Scenarios Where Joint Fabric Shines
The Mixed-Ecosystem Household
Sarah uses Apple Home on her iPhone. Her partner Marcus uses Google Home on his Pixel. Their kid has an Echo Dot in their room. Today, every smart device needs to be commissioned to three different platforms. That’s three fabric slots per device, three chances for something to break, and three apps to troubleshoot when things go sideways.
With Joint Fabric: commission once, everyone controls everything from their preferred platform. If Sarah gets annoyed with Apple Home and switches to Samsung SmartThings, she authorizes SmartThings on the Joint Fabric and she’s done. No re-commissioning 47 devices.
New Construction and Renovations
A builder installs 60 smart switches and lights in a new home. Right now, they’d commission everything to one platform, hand over credentials, and hope the new homeowner uses the same ecosystem. If the buyer prefers a different platform, there’s a painful migration process.
With Joint Fabric: the builder commissions everything once to the Joint Fabric. The new homeowner authorizes their preferred platform (or platforms) and immediately has full control. The builder can remove themselves as an administrator after handover. Clean, simple, professional.
Property Managers and Short-Term Rentals
You manage an Airbnb with smart locks, lights, and thermostats. Different guests use different platforms. Today, you can’t easily give a guest control through their own ecosystem. They use your setup or nothing.
With Joint Fabric: authorize a guest’s platform temporarily, revoke when they check out. They control devices from their own familiar app during their stay. Way better guest experience, and you maintain full administrative control.
The “I Want to Try a New Ecosystem” Scenario
You’ve been all-in on Google Home. You’re curious about Apple Home after buying an iPhone. Today, trying a new platform means commissioning every single device again. It’s such a hassle that most people just stick with what they have.
Joint Fabric eliminates switching costs entirely. Authorize the new platform, play with it for a week. Don’t like it? Remove it. Your devices don’t care.
What Needs to Update for Joint Fabric
Here’s the important part: Joint Fabric is primarily a controller/hub feature. The “intelligence” lives in the platforms (Apple Home, Google Home, Alexa) and the central Datastore. Your individual devices (bulbs, switches, sensors) don’t need firmware updates to participate in a Joint Fabric.
What does need updates:
- Apple HomePod / Apple TV: Firmware update from Apple (likely tied to iOS 20 or a point release)
- Google Nest Hub / Nest speakers: Firmware update from Google
- Amazon Echo devices: Firmware update from Amazon
- SmartThings Hub: Firmware update from Samsung
- Home Assistant: Software update (likely faster than the big platforms)
The platforms need to implement Joint Fabric support, including the Datastore protocol, authorization handling, and the shared administration model. This is non-trivial work, but it’s software, not hardware.
Realistic timeline: 3-6 months for the major platforms. Apple may bundle it with a fall OS release. Google and Amazon could ship faster via background updates. Home Assistant’s open-source community will probably have experimental support within weeks.
The Fabric Limit Problem (Solved)
One of Matter’s most annoying limitations has been fabric limits. Each Matter device supports a fixed number of fabrics (typically 5). If you use Apple Home, Google Home, Alexa, SmartThings, and Home Assistant, you’ve hit the limit. No room for a sixth platform.
Joint Fabric eliminates this problem. Five platforms sharing one Joint Fabric use one fabric slot. You’ve got 4 slots left. In practice, most people won’t even think about fabric limits anymore.
This was a bigger deal than it might seem. The 5-fabric limit was already causing problems for power users running multiple platforms plus Home Assistant. Joint Fabric turns the limit from “barely enough” to “more than plenty.”
Security Implications
Sharing a fabric across platforms raises obvious security questions. The CSA addressed this:
- Each platform authorized on the Joint Fabric gets its own access credentials through the Datastore
- Platforms can be granted different permission levels (full admin vs. limited control)
- Revoking a platform’s access is instant and doesn’t affect other platforms
- The Datastore handles certificate management and access tokens
- Compromising one platform’s credentials doesn’t give access to another platform’s credentials
The security model is arguably better than Enhanced Multi-Admin, where each platform maintained independent connections that were harder to audit centrally. With Joint Fabric, there’s one place to see who has access and one place to revoke it.
Will All Platforms Actually Support This?
This is the billion-dollar question. Apple, Google, Amazon, and Samsung are all CSA members and all contributed to the Joint Fabric spec. They’re all incentivized to support it because it removes a major friction point that keeps people from buying more smart home devices.
But there’s always the risk that one platform drags its feet or implements it in a limited way. Apple historically moves slower on interoperability features. Google tends to ship fast but sometimes breaks things. Amazon is unpredictable.
My prediction: all major platforms will support Joint Fabric within 12 months. The competitive pressure is too high. If Google supports it and Apple doesn’t, that’s a selling point for Pixel phones. None of them want to be the holdout.
What You Should Do Now
If you’re buying devices today: Don’t wait for Joint Fabric. Any Matter device you buy now will work on a Joint Fabric once your hubs support it. The devices themselves don’t need to change. Buy what you need. Check our list of the best Matter-compatible devices for current recommendations.
If you’re choosing an ecosystem: Joint Fabric makes this choice less permanent. You’re no longer locked in. But you still need a primary hub to act as the Joint Fabric host initially. Check our best smart home ecosystem guide for recommendations.
If you’re frustrated with multi-admin today: Enhanced Multi-Admin (Matter 1.4) is available now and works reasonably well as a bridge solution. It’s not as clean as Joint Fabric, but it’s better than fully manual commissioning. Read our Matter compatibility guide to see which of your devices support it.
If you manage multiple properties: Start planning your Joint Fabric migration now. This feature will save you hours per property. Talk to your smart home hub vendor about their Joint Fabric roadmap.
Frequently Asked Questions
Do my existing Matter devices need a firmware update for Joint Fabric?
No. Joint Fabric is implemented at the controller/hub level. Your existing Matter bulbs, switches, and sensors will participate in a Joint Fabric without any device-side update. Only your hubs (HomePod, Nest Hub, Echo, etc.) need firmware updates.
Can I use Joint Fabric with just one ecosystem?
Yes, but you won’t see much benefit. Joint Fabric shines when multiple platforms share administration. If you only use Apple Home, your experience stays the same. But having it available means you can try other platforms later without re-commissioning everything.
What happens if one platform goes offline?
Controllers cache device information locally. If Google’s servers go down, Google Home can still control devices it has cached. The Datastore synchronization happens when connectivity is restored. Your local control capabilities remain intact.
Is Joint Fabric mandatory or optional?
Optional. Platforms and users can choose whether to participate in a Joint Fabric or maintain separate fabrics the old way. This is important for users who intentionally keep ecosystems isolated for security or organizational reasons.
Will Home Assistant support Joint Fabric?
Almost certainly, and probably faster than the commercial platforms. Home Assistant’s open-source Matter implementation is actively maintained, and the community is already discussing Joint Fabric support. Expect experimental builds within weeks of the hub SDKs being available.
The Bigger Picture
Joint Fabric represents a philosophical shift in how Matter works. The original spec treated each platform as an island that happened to speak the same language as other islands. Joint Fabric makes them roommates sharing an apartment. That’s closer to what consumers actually want: one smart home, accessible from any interface they prefer.
Combined with NFC commissioning for easier setup and Thermostat Suggestions for smarter automation, Matter 1.6 is the release that makes multi-ecosystem homes genuinely practical. Not just technically possible. Actually pleasant to use.
If you’re starting from scratch, check our guide on how to start a smart home with Joint Fabric in mind. The setup process is about to get a lot simpler.