Matter 1.6 Lets A Thermostat Say No. KNX Installers Will Recognise The Idea.

Most smart home standards are written from the app's point of view. The app wants to do something, the device does it.
Matter 1.6 has a small feature that quietly flips that. It is called Thermostat Suggestions, and it says something about where the whole industry is heading.
What the Alliance actually released
The Connectivity Standards Alliance published Matter 1.6 on 17 June 2026. It describes the release as "a focused feature release", and that is fair. There is no headline device category. Instead there are four things worth a proper look.
NFC commissioning lets a device be set up by holding a phone near it, before it is installed and without power. The Alliance's examples are bulbs and in-wall switches. Matter 1.4.1 already carried NFC setup payloads, but according to CNX Software the earlier approach still needed Bluetooth LE to finish the job. Full bidirectional NFC is the change.
Joint Fabric lets several controllers co-administer one shared network with a central datastore. The Alliance names new construction handovers, multi-platform households and professionally managed properties as the use cases.
Thermostat Suggestions is the one I keep thinking about. More on that below.
Then there is a set of core changes: devices can communicate their capabilities and limits, security sensors get an event history, smoke and CO alarms can report an unmounted state, and certificate revocation lists are now partitioned so they scale better.
The thermostat that can decline
Until now, an ecosystem told a thermostat what to do and the thermostat did it. Under 1.6, an ecosystem submits a time-bound suggestion tied to a preset. The thermostat weighs that against the user's preferences and the current context, and if it says no, it gives a standardised explanation.
Read that again. The standard now expects the device to hold its own local judgement, and to overrule the cloud, the app or the assistant when the occupant's settings say otherwise.
Anyone who has commissioned a KNX system will find this familiar. A KNX room controller does not blindly obey whatever telegram arrives. It has its own setpoints, its own operating modes, its own priorities, and a visualisation or an energy manager is one participant among several, not the boss. That design was not an accident. It is what lets a house behave sensibly when the server is off, the router has died or the app has updated itself into a different layout.
It is good to see Matter arriving at the same conclusion.
Handover is where the hard problems live
The Joint Fabric use cases are the other tell. New construction handovers and professionally managed properties are not problems a hobbyist has. They are problems integrators have, because a house passes through several hands: the electrician, the integrator, the owner, the owner's second integrator five years later.
In a KNX project that story is well trodden. The project lives in ETS, any certified integrator can open it, and the group addresses on the bus mean the same thing to everyone. I wrote about the group addressing side of that on 22 September, and the point holds here: a system is only as serviceable as the structure someone left behind.
Matter is now building the equivalent tools for the wireless world. I think that is a good thing. I also think it is early.
The caveat nobody puts in the headline
A specification is not a product. The Alliance says Matter 1.6 is available to manufacturers and platform developers, and that consumer adoption depends on each company's timeline.
MacRumors points out that Apple has not been quick with new Matter versions. Apple Home, it says, still lacks full support for Matter 1.4, which was announced in November 2024. If that is the pace for the platform most of my clients actually use, then thermostat suggestions and Joint Fabric are not something to design a house around this year.
Home Assistant is moving faster. Its Matter integration was rebuilt on matter.js and launched as Matter Server 9.0 on 23 June 2026, with support for the Matter 1.5.1 specification and 1.6 listed as coming. Home Assistant says Matter now runs in 38 percent of instances. That is real adoption, but it is a different audience from a client who wants the lights to work and never wants to hear the word firmware.
What I actually do with this
For a client who wants Apple Home or Matter devices in the mix, I still put a wired KNX backbone underneath and use a gateway like 1Home to publish what makes sense. Lighting, blinds, heating and the parts of the house that must keep working stay on the bus, on Hager, Ekinex and Berker hardware that will be serviceable long after any phone has been replaced. Matter sits on top as a convenience layer.
Matter 1.6 does not change that arrangement. It does make me more comfortable with it. A standard that lets devices push back on ecosystems, and that takes handover seriously, is a standard heading somewhere sensible.
In Johannesburg, where load shedding taught a lot of clients what happens when a house depends on something that needs to phone home, a thermostat that keeps its own counsel is not a small detail. It is the whole point.
If you are scoping a project and want a straight answer on what belongs on the bus and what belongs on top of it, get in touch.
wayne@knxlogic.co.za | 082 564 3982 | www.knxlogic.co.za
Just a conversation about what the project needs.




Comments