Matter 1.6 Explained: Joint Fabric, NFC Commissioning, and Thermostats That Know Better

A Release About Plumbing, Not Product Categories

The Connectivity Standards Alliance released Matter 1.6 on June 17, 2026, making the specification available for device makers and platforms to integrate into their products. The announcement came at Unify, the CSA's inaugural conference, held in Austin, Texas, and the full specification is now published on the CSA website.

Anyone scanning the release notes for new gadget categories will come away empty-handed. Matter 1.6 adds no new device types at all. It is a focused feature release aimed squarely at three unglamorous but consequential problems: how devices get set up, how multiple ecosystems coordinate management of the same hardware, and how control commands account for context.

Three headline features frame the release:

• Joint Fabric — shared, multi-party administration of a single Matter network
• NFC-Based Commissioning — full setup over NFC, even before a device is powered on
• Thermostat Suggestions — recommendations that a thermostat can adopt or defer, rather than commands it must obey

Joint Fabric: One Network, Many Co-Administrators

Joint Fabric is the structural change in this release. It allows multiple user-authorized controllers to co-administer a single shared Matter network, with any device added to that Joint Fabric becoming accessible to all participating controllers. The mechanism rests on a central Datastore that the participating controllers share.

The Verge characterizes the result as a single Matter network that Apple Home, Amazon Alexa, Google Home, Samsung SmartThings and others can all become co-signers on — so a device added once appears across every authorized ecosystem, rather than needing to be paired separately with each one.

Crucially, administration is decoupled from device membership. Administrators can be added or removed independently of the devices on the network, which means a user can revoke a platform's authority at any time without losing the devices themselves. Walking away from an ecosystem stops being a teardown-and-rebuild exercise.

Why the Fabric Slot Math Matters

To understand why Joint Fabric is more than a convenience feature, it helps to look at the arithmetic that governs today's multi-platform homes. Certified Matter devices are required to support at least five fabrics simultaneously — and in a genuine multi-admin setup, that ceiling arrives faster than it sounds.

Apple Home is a particularly expensive guest. It consumes two of a device's five slots, because Apple synchronizes Matter accessories through iCloud Keychain, which requires a second separate fabric. That leaves noticeably less capacity for Google Home, Alexa, or Home Assistant to share the same device.

Joint Fabric changes the calculus. Participation in a Joint Fabric counts as only a single fabric toward a device's capacity, which leaves headroom for the device to join traditional ecosystem fabrics at the same time. One slot can, in effect, represent an entire consortium of administrators.

How Joint Fabric Differs From Enhanced Multi-Admin

Matter has been circling this problem for a while. Enhanced Multi-Admin arrived in Matter 1.4, announced in November 2024, and its Fabric Sync capability shared device access between separate fabrics. But the underlying structure was unchanged: each ecosystem still consumed its own fabric slot on every device.

Joint Fabric is not an incremental extension of that model. The CSA positions it as a new and distinct approach — rather than syncing state between multiple fabrics, it establishes one fabric with multiple authorized administrators sharing a common Datastore. The difference shows up directly in the slot math described above.

Where Joint Fabric Is Meant to Be Used

The CSA frames Joint Fabric around scenarios where ownership and administration genuinely need to be separated:

• New construction handovers, where a builder provisions devices before a resident takes over the home
• Multi-platform households, where different family members or different rooms run different ecosystems side by side
• Professionally managed properties, where building managers, tenants and service providers all need appropriate access to the same installed hardware

In each case, the ability to add and remove administrators without disturbing the devices is the operative feature — a tenant moving out, or a builder handing over the keys, becomes an administrative change rather than a re-commissioning project.

NFC-Based Commissioning: Setup Before Power

The second headline feature attacks the least loved part of the smart home: setup. Matter 1.6 introduces bi-directional NFC communication that can commission a device even before it is fully powered on.

This builds on groundwork laid in Matter 1.4.1, which added NFC onboarding payload support. That earlier mechanism embedded setup information in an NFC tag but still relied on Bluetooth LE to actually complete commissioning. In 1.6, the complete commissioning exchange can occur over NFC, making it a genuine alternative to BLE setup rather than a shortcut into it. To support this, the Core Specification adds an NFC Transport Layer (NTL) section.

For users, the practical effect is the disappearance of the QR code hunt. There is no printed code to locate, illuminate, and scan at an awkward angle — you simply hold a phone near the device.

NFC in Practice: Real Installation Scenarios

The "before it is powered on" detail is what turns this from a minor convenience into an installation workflow change. The CSA highlights several concrete cases:

• Commissioning a light bulb before it is screwed into a ceiling fixture — no ladder, no straining to scan a code on a fitting overhead
• Setting up an in-wall switch before mains power is turned on, so the electrical and network work do not have to be sequenced around each other
• Provisioning multiple devices in advance for larger installations, tapping through a box of hardware on a bench rather than device by device on site

For professional installers and builders — the same audience Joint Fabric is courting — the two features complement each other neatly: provision in bulk over NFC, then hand administration over cleanly.

Thermostat Suggestions: From Commands to Recommendations

The third headline feature is a philosophical shift as much as a technical one. Thermostat Suggestions replaces direct commands with time-bound recommendations tied to the thermostat's supported presets. The thermostat can then adopt or defer each suggestion based on user preferences and context.

The canonical example is the one everyone with more than one smart home app has lived through: a thermostat that was just manually adjusted can recognize that a suggestion arriving moments later from another source is likely not what the user intended — and defer it, rather than dutifully undoing a deliberate choice made seconds earlier.

Deferral is not silent, either. When a thermostat does not follow a suggestion, it provides a standardized explanation, so the requesting service knows why its recommendation was set aside instead of simply observing that nothing happened.

Protecting Intent Across Ecosystems and Utilities

The feature's most concrete payoff is in energy programs. A user enrolled in a utility demand-response program can protect those commitments, so an automation from another ecosystem cannot accidentally override a savings event — a scenario where a stray routine does not just cause annoyance but costs money or breaks an agreement.

More broadly, preferences such as optimizing for energy savings, humidity control, or air quality can be recognized and respected across connected services. Those preferences no longer need to be configured separately in each service, which removes one of the more tedious failure modes of a multi-platform home: settings that drift out of sync because they were entered four times in four places.

Core Specification Enhancements Beyond the Headliners

Beneath the three flagship features, Matter 1.6 also lands a set of core specification improvements:

• Standardized communication of device capabilities and operational limits, so controllers can understand what a device can and cannot do without vendor-specific guesswork
• Security sensor event history, giving controllers access to a record of past events rather than only current state
• An unmounted state for smoke and CO alarms, allowing an alarm to report that it has been taken off its bracket
• Partitioned certificate revocation lists, building on the CRL support added in Matter 1.4.2

How 1.6 Fits the Recent Release Cadence

Placed against its predecessors, Matter 1.6 reads as a deliberate return to infrastructure after a category-expansion release:

• Matter 1.4 (November 2024) — brought Enhanced Multi-Admin
• Matter 1.4.1 — added NFC onboarding payload support
• Matter 1.4.2 — added Wi-Fi-only provisioning and improved security, including CRL support
• Matter 1.5 — introduced cameras, closures (window shades, drapes, awnings, gates and garage doors) and enhanced energy management
• Matter 1.6 — shifts focus back to setup, coordination and control rather than new categories

Two of 1.6's three headline features are direct continuations of earlier work: NFC-Based Commissioning completes what 1.4.1 started, and Joint Fabric revisits the problem Enhanced Multi-Admin took a first pass at in 1.4.

The Adoption Question

Which brings us to the caveat hanging over the whole release. As of the Matter 1.6 announcement, no Matter ecosystem had shipped Fabric Sync — the Enhanced Multi-Admin synchronization introduced back in November 2024 — with others. A capability that has sat in the spec for more than a year without a single shipping implementation is not an encouraging precedent for how quickly Joint Fabric will move from specification to product.

Apple is a frequently cited example: it has not been quick to implement new Matter specifications, and Apple Home still does not support all the Matter 1.4 features announced in November 2024.

There is a counterexample worth noting, though. Apple implemented Thread 1.4 support in tvOS 27, enabling Thread credential sharing so that devices join existing Thread networks rather than spinning up parallel networks across border routers from different manufacturers. That is exactly the class of cross-vendor plumbing fix Joint Fabric represents — evidence that when the interoperability payoff is clear enough, the work does eventually get done.