Matter 1.6: NFC setup, Joint Fabric and thermostat suggestions

Matter 1.6 added no device types. It changed how devices are set up, shared between controllers and told what to do, and it adds three things to watch.

By Ines Calder · · 4 min read · Comments

Matter 1.6 was announced on 17 June 2026. Unlike 1.2 to 1.5, it brings no new device types. The Alliance describes it as a focused feature release about setting devices up, sharing them between controllers, and how a device decides what to do with an instruction. This piece explains each change and what it means for someone choosing devices now.

Setting up over NFC

Matter has used a QR code and Bluetooth Low Energy for setup. Matter 1.4.1 let a device hold its setup details on an NFC tag, instead of a printed code, though the exchange itself still used Bluetooth. Matter 1.6 takes it further, with the entire commissioning exchange able to run over NFC in both directions, including before the device has full power.

The Alliance's examples show why. A bulb can be set up before it goes into its ceiling fitting, and an in-wall switch before the mains is switched on. For a larger job, several devices can be prepared in advance and brought into use where they end up. For a household, setup becomes holding a phone to the device.

What it needs: a device with an NFC tag and a phone or controller that supports the new method. The announcement does not say which products or platforms will offer it and when.

Joint Fabric

A fabric is Matter's word for one network of trust: the set of devices and controllers that share credentials. Enhanced Multi-Admin arrived in Matter 1.4 and lets platforms hand each other access to a device after a single approval by the user. Matter 1.6 adds a different route, Joint Fabric.

In the earlier approach, access is shared between separate fabrics that each belong to a platform. In Joint Fabric, several controllers that users have authorised administer one shared network, using a central datastore, and any device added to it is reachable from all of them. Controllers can be added or removed without touching the devices. A device counts a Joint Fabric membership as a single fabric against its capacity, so it can still belong to ordinary fabrics at the same time.

The Alliance suggests it suits households that run several platforms, new-build handovers and professionally managed properties. Whether a consumer platform you use will adopt it is a decision for that platform. Our guide to sharing a device between platforms covers the methods that exist today.

Thermostat suggestions

Today a platform sends a thermostat a command, and the thermostat acts on it with little context. Matter 1.6 adds a second route. A controller can send a suggestion that expires, linked to a preset that the thermostat offers, and the thermostat decides whether to follow it using the owner's preferences and what is happening now.

The announcement gives examples: a thermostat enrolled in a demand-response scheme can protect that commitment from an automation on another platform, and one adjusted by hand a moment ago can set aside a conflicting suggestion. When it does not follow a suggestion it gives a standard reason. If you run heating automations from more than one app, this is meant to stop them undoing each other.

Smaller changes

The announcement lists several core improvements:

  • Devices can report their capabilities and operating limits in a standard way, so controllers can show them more accurately.
  • Security sensors can report a history of events.
  • Smoke and carbon monoxide alarms can say they have been taken off their mounting.
  • Certificate revocation lists, added in Matter 1.4.2, can be split into smaller parts that are updated separately, which suits a growing number of certified devices.

What to take from it

  1. Nothing here changes what is in the shops today. The announcement says each company implements features on its own timeline and tells readers to look to their brands for news.
  2. No new device types. If you were waiting for a type, check the earlier releases. Our release history lists them.
  3. Check for NFC and thermostat support when they appear. They will be product-level facts, on a maker's page or a platform's list, before they are anything else.
  4. Keep your own record of the specification version a device was certified against. A 1.6 feature needs a product certified for it.

This piece is based on the Alliance's published announcements, read on 13 November 2026. We do not test devices.

I
Ines Calder

Staff writer, standards and platforms

How we work
Latest news