Key Takeaways
- Matter 1.6 (released June 17, 2026) is the current spec version β its headline changes are NFC setup, Joint Fabric, and Thermostat Suggestions
- Existing Matter 1.x devices remain fully compatible β nothing breaks
- This is distinct from Thread (the network layer under Matter) and from Thread/Wi-Fi 7 router considerations
- Also distinct from this cluster's general protocol primer (Matter/Thread/Zigbee/Z-Wave overview) and local-control guide (commissioning/avoiding cloud bridges)
- Energy-management device types (inverters, batteries, heat pumps) are not new in 1.6 β those were introduced earlier, across Matter 1.3-1.5
What Changed
Matter 1.6's three headline additions are NFC-based commissioning, Joint Fabric, and Thermostat Suggestions β a focused, tooling-and-coordination release rather than a new-device-category release.
- NFC setup: the full device-commissioning exchange can now happen over NFC, rather than only QR-code scanning and Bluetooth.
- Joint Fabric: expands on the existing Multi-Admin toolkit so multiple user-authorized controllers can co-administer a single shared Matter network, making a device accessible across participating ecosystems instead of tied to whichever hub commissioned it first.
- Thermostat Suggestions: standardizes how ecosystems recommend thermostat changes β instead of sending a direct command, a controller sends a time-bound suggestion the thermostat itself evaluates.
- The revision is additive at the protocol level: it defines new things Matter *can* describe, without removing or breaking support for existing device types. Energy-management device types (inverters, batteries, EV chargers, heat pumps) were not part of this release β see this cluster's Matter inverter/heat-pump integration guide for that earlier (Matter 1.3-1.5) work.
Backward Compatibility
A device certified against an older Matter version continues to work with a hub or controller running the newer spec β you do not need to replace existing Matter devices.
- Your existing Matter lights, locks, and sensors need no changes when Home Assistant or another controller adds support for the newer spec revision.
- New device types (like energy management) are only usable if a specific product implements them β owning older Matter hardware doesn't retroactively grant it new capabilities.
- CSA's own Matter 1.6 announcement describes it as additive β no breaking changes to existing device types were mentioned in the release. As always with any spec update, check a specific device's release notes if you rely on a narrow or unusual field.
How This Differs From Other Matter Content Here
This article covers the spec revision itself; the general protocol primer explains Matter/Thread/Zigbee/Z-Wave at a conceptual level, and the local-control guide covers commissioning and avoiding cloud bridges β read all three for the full picture.
- If you're asking "what is Matter and how does it compare to Zigbee/Z-Wave," start with the general protocol primer.
- If you're asking "how do I commission a Matter device locally without a cloud bridge," see the local-control guide.
- If you're asking "what changed in the spec recently, and does my hardware need an update," this article is the one β and it points to the energy-integration guide if you're looking for the earlier (1.3-1.5) energy-management work specifically, since that isn't part of 1.6.
Frequently Asked Questions
Do I need to update my existing Matter devices?
No β existing 1.x-certified devices continue working without any update. New capabilities like NFC setup or Joint Fabric only matter if you're buying new hardware or a new controller that implements them.
What is the biggest practical change in Matter 1.6?
Joint Fabric β it lets multiple user-authorized controllers co-administer a single shared Matter network, so a device can be genuinely shared across ecosystems instead of belonging to whichever hub commissioned it first. NFC setup and Thermostat Suggestions are the other two headline additions. Energy-management device types (inverters, batteries, heat pumps) are not new in this release β see the Matter inverter/heat-pump integration guide for that earlier work.
Does this affect Thread?
Thread is the networking layer Matter often runs over; Matter 1.6 is a change to the Matter application layer, not to Thread itself. See the Thread and Wi-Fi 7 routers guide for networking-layer changes.
Is my hub software compatible with Matter 1.6?
Hub software needs its own update to support a new spec release β it isn't automatic. Home Assistant (verified 2026-07-16 against home-assistant.io's own blog) fully supports Matter 1.5.1 as of write-time, with Matter 1.6 support in active beta rather than fully released β check your specific hub's current release notes rather than assuming day-one support for the newest spec release.
How is this different from the general Matter/Thread/Zigbee explainer on this site?
That article explains the protocols conceptually and compares them. This article covers what specifically changed in Matter 1.6 β a narrower, update-focused scope.
Where can I check the current official spec version?
The Connectivity Standards Alliance (csa-iot.org) publishes and announces the current Matter specification directly β check there rather than relying on secondary sources or marketing materials for the exact version number.
Do all Matter controllers support Matter 1.6 immediately?
No β a spec release being published doesn't mean every hub implements it on day one. Home Assistant's own blog confirms 1.6 support is in active beta rather than fully released as of write-time; Apple Home, Google Home, and SmartThings each have their own independent rollout timelines that this article does not track β check your specific controller's current release notes.
Does this change how Matter devices are commissioned?
Not for existing methods β QR-code and Bluetooth commissioning still work the same way. Matter 1.6 adds NFC as an additional commissioning option; it doesn't remove or change the existing process. See the local-control guide for the commissioning walkthrough.