The First Matter Tap-to-Pair Sensor Showed Up at IFA. My Home Assistant Box Cannot Tap Anything.

A phone next to smart home sensors and a camera

There is a folder on my phone full of blurry photos, and every single one is the back of a smart home device. The QR code, the setup code printed underneath, sometimes the serial number if I was being thorough. I take them before I install anything, because I learned the hard way that the sticker you need is always on the surface that ends up facing a wall.

Matter 1.6 is quietly trying to make that folder obsolete. And this week in Berlin, the first piece of hardware that actually does it turned up on a show floor.

What Matter 1.6 actually changed

The Connectivity Standards Alliance published Matter 1.6 back in June. Joint Fabric got most of the headlines, but the change I keep thinking about is the boring-sounding one: NFC as a commissioning transport.

This is not the same as what came before. Matter 1.4.1 already let you put the commissioning payload — the thing normally encoded in that QR code — onto an NFC tag. But Bluetooth LE still had to carry the actual handshake. The tag was a convenience; BLE was the pipe. In 1.6, NFC itself is the pipe. The whole exchange runs bidirectionally over the 13.56 MHz coupling that every modern phone already has.

That has a side effect that sounds like a typo the first time you read it: the device does not have to be powered on. The commissioning data sits on the NFC chip and waits. You can pair a bulb before you screw it into the fixture. You can set up an in-wall switch before the mains is live. For anyone provisioning fifty devices in a building, you can do the whole batch on a table and then go install them.

The first hardware showed up at IFA

At IFA Berlin this week, Heiman showed an HS2HT outdoor temperature and humidity sensor sitting next to a sign reading “Matter 1.6 NFC Pairing Function” — as far as Matter Alpha reports, the first demonstrated hardware using the feature. It is an IP65 sensor, which is a nice bit of symmetry: the outdoor device is exactly the one you least want to be crouching under with a phone torch.

Heiman brought other things too. A WS6GW bridge that pulls Zigbee and Sub-GHz devices into Matter, SC3 smoke and CO alarms offered in separate Matter, Zigbee, Wi-Fi and Sub-GHz variants rather than one device with every radio crammed in, a four-in-one door and window sensor, and an HS1ZT dongle that can run as a Zigbee coordinator, a Zigbee router, or a Thread RCP. No pricing, no availability dates. So this is a “the spec is real” story, not a “go buy this” story.

Worth noting alongside it: the Open Home Foundation had its own booth at IFA for the first time, Hall 1.2, stand 1.2-153, running 4 to 8 September. An open, locally controlled smart home standing on the same floor as the ecosystems it is trying to route around is its own kind of milestone.

A hand holding a phone above a smart camera, bulbs and a sensor
Tap-to-pair moves the setup ritual from a torch and a QR code to a phone held against the device. Photo: Pexels.

My mini PC cannot tap anything

Here is where the enthusiasm meets my basement. Home Assistant spent most of this year rebuilding its Matter stack on matter.js — the old python-matter-server ended at 8.1.2 and is no longer updated. That migration slowed Matter adoption for a while, and then unblocked it: Matter 1.6 support landed in the 1.2.x Matter Server beta along with ICD battery-saving controls, wider Thread diagnostics, and multiple stored Wi-Fi and Thread credentials.

The backend supports 1.6. NFC commissioning still does not work, and the reason is physical. My Home Assistant runs bare metal on a used HP EliteDesk 800 G4 in a cupboard. It has plenty of USB ports and no NFC radio. Even if I bolted one on, the mini PC is not where the sensor is — it is two floors below, behind a door. Per the same reporting, the implementation is still an open discussion: a USB reader, or some proxy device that hands the onboarding payload to Home Assistant.

The obvious answer is the phone. The companion app already scans QR codes; it is already the thing I hold against devices. Turning it into an NFC commissioner is the natural path, but it is real work in the app and in core, and it has not happened yet. So the spec is done, one sensor exists, and the controller I actually run has no way to use it.

What it would honestly buy me

I should be careful not to oversell this to myself. I commission a new device maybe once a month. Scanning a QR code on my kitchen table, with the device in my hand and good light, is completely fine. Tap-to-pair would save me four seconds.

The cases I actually remember being annoyed by are all the same case: the device was already mounted. The sensor on the outside wall. The bulb in the stairwell fixture. The switch I installed before I understood that I would want to re-pair it two years later. For those, commissioning something that is not yet powered and not yet on the wall is a genuinely better order of operations. In January, in Switzerland, on a ladder, with cold hands, “pair it at the table first” is worth more than four seconds.

Batch pre-provisioning, the feature everyone leads with, is an installer feature. In a normal house it is close to irrelevant. I would rather say that plainly than pretend my seven-room flat is a commissioning bottleneck.

The question I want answered before I get excited

The Matter setup passcode has always been physically printed on the device, so NFC does not obviously change the threat model — you need to be standing next to the thing either way. But a printed sticker can be covered with tape, photographed once, and forgotten. A chip keeps answering for as long as it is in the device. I would like to understand how the window behaves after a device is already commissioned, and I have not had a demo unit in my hands, so I am not going to pretend I have tested it.

What I do like: none of this involves a cloud. Commissioning is a conversation between my phone, the device, and my controller, and that is the whole reason I care about Matter at all rather than another vendor app.

What I am doing about it: nothing, yet

There is no product to buy and no setting to enable. What actually changed this week is smaller and more useful than a tap demo: Home Assistant is back on a fast Matter cycle. The 1.6 spec shipped in June and support was in a server beta by July, in the same release window as ICD controls, Thread diagnostics and the groundwork for Matter cameras. Before the matter.js rewrite, that gap was measured in a lot longer than a month.

So I will keep watching the Matter Server changelog, and I will keep taking blurry photos of stickers. But it is a good sign when the most interesting thing at a consumer electronics show is a temperature sensor that you pair by touching it.

Leave a Reply

Your email address will not be published. Required fields are marked *