The Connectivity Standards Alliance released Matter 1.6 on June 17, giving smart home device makers and platform companies a new set of tools aimed at the problems users still run into after years of Matter promises: awkward setup, fractured platform control, conflicting automations, and unclear device status.
The release does not add a splashy new class of devices. Instead, it focuses on the plumbing that determines whether a smart home feels simple after the box is opened. Matter 1.6 introduces NFC-based commissioning, a new Joint Fabric model for shared control across ecosystems, thermostat suggestions that respect user preferences, and status improvements for sensors, alarms, and device security infrastructure.
That makes this a quieter but potentially more important update than a spec expansion built around more product categories. Matter already has backing from major smart home players, including Apple, Amazon, Google, Samsung, IKEA, LG, Signify, and many device makers. The challenge has been less about industry logos and more about whether mixed-platform homes can work without repeated setup steps, app detours, and mysterious device behavior.
NFC setup is the most immediately understandable change
The most practical Matter 1.6 feature is full NFC-based commissioning. Earlier Matter updates let devices carry setup information in an NFC tag, but the commissioning process still depended on Bluetooth LE. Matter 1.6 lets the full commissioning exchange happen over two-way NFC communication.
For buyers, the plain-English version is tap-to-set-up. A phone can be held near a Matter device to commission it, even before the device is fully powered. The Alliance gives examples that fit common installation headaches: a light bulb can be commissioned before it is screwed into a ceiling fixture, and an in-wall switch can be prepared before mains power is turned on.
This matters because smart home setup often happens in physically awkward places. QR codes may be printed on tiny labels, hidden after installation, or hard to scan once a device is mounted. Bluetooth setup can also be brittle when installers are provisioning multiple devices in a row. NFC does not solve every onboarding problem, but it gives device makers a cleaner way to support pre-configuration and bulk installation.
Joint Fabric targets the multi-platform mess
The most consequential feature for households may be Joint Fabric, a new approach to Matter’s multi-admin promise. Matter 1.4 introduced Enhanced Multi-Admin, which helped ecosystems share device access after a single user consent. Matter 1.6 goes further by allowing multiple user-authorized controllers to co-administer one shared Matter network.
In current Matter setups, sharing a device across Apple Home, Google Home, Amazon Alexa, Samsung SmartThings, or another ecosystem can still feel like stitching together separate worlds. Joint Fabric is designed around a shared network model. A device added to that Joint Fabric can be available to all participating controllers, while administrators can be added or removed separately from the devices themselves.
The Alliance says participation in a Joint Fabric counts as one fabric toward a device’s capacity, leaving room for the same device to also join traditional ecosystem fabrics. That is a technical detail with practical consequences: low-cost smart home accessories often have limited capacity for how many fabrics they can join. A shared fabric could reduce the pressure on that limit in homes where different people prefer different control apps.
The strongest use cases are not just gadget-heavy homes. Joint Fabric also fits professionally managed properties, new-construction handovers, rentals, and homes where a builder, installer, homeowner, and family members need access without rebuilding the device network every time responsibility changes.
Thermostats get a smarter way to say no
Matter 1.6 also changes how ecosystems can interact with thermostats. Instead of sending only direct commands to change temperature or mode, a controller can send a time-bound suggestion tied to a supported preset. The thermostat can then evaluate that suggestion against current conditions and user preferences before acting.
That sounds subtle, but it addresses a real automation problem. A household might have one ecosystem optimizing for energy savings, another routine tied to comfort, and a utility demand-response program asking the thermostat not to override a savings event. Matter 1.6 gives thermostats a standardized way to process recommendations without blindly obeying whichever service spoke last.
The same mechanism can help when a user manually adjusts a thermostat and another automation tries to change it moments later. Instead of creating a fight between apps, the thermostat can treat the incoming change as a suggestion, defer it when appropriate, and provide a standardized explanation when it does not follow the recommendation.
Status and security updates make devices less opaque
Matter 1.6 includes several smaller core improvements that could make smart home dashboards more trustworthy. Devices can now communicate capabilities and operational limits in a more standardized way, helping controllers represent what a device can actually do instead of guessing or hiding features behind a manufacturer app.
Security sensors can expose event history across ecosystems, giving users and platforms more context about what happened and when. Smoke and carbon monoxide alarms gain an unmounted state, so a controller can show when a device has been removed from its installed position instead of treating it as simply present or absent.
The release also adds partitioned certificate revocation lists. That is not a kitchen-counter feature, but it matters for the long-term health of Matter’s device trust model. As the number of certified devices grows, the system needs a scalable way to revoke compromised or invalid device certificates without pushing every controller through one large monolithic update.
Do not buy on the spec alone
The usual Matter caveat still applies: a specification release is not the same thing as support in the products people already own. The Alliance says device makers, platform developers, and ecosystem partners can now review the Matter 1.6 specification and software development kit, but adoption will vary by company and product type.
That means shoppers should watch for specific support from the brands and ecosystems they use, not just a generic Matter logo. The useful questions are concrete: Does this device support Matter 1.6 NFC commissioning? Does my preferred platform support Joint Fabric? Will this thermostat expose suggestions and explanations, or only basic Matter controls? Will existing devices get firmware updates, or will these features arrive only in new hardware?
For installers and advanced users, Matter 1.6 is worth tracking because it targets the parts of the smart home that are hardest to fix after deployment. For ordinary buyers, the release is a sign that Matter’s next phase is less about proving that devices can connect and more about making mixed ecosystems less fragile once they do.
The standard’s promise has always been simple: smart home devices from different brands should work together securely and reliably. Matter 1.6 does not make that promise fully real by itself. It does, however, aim directly at the setup, sharing, control, and visibility problems that have made the connected home feel harder than it should.