A protocol, not a radio
Matter is a smart-home standard backed by Apple, Google, Amazon, Samsung and hundreds of device makers under the Connectivity Standards Alliance. Its promise: buy a device with the Matter logo and it works with every major ecosystem, locally, without a vendor cloud.
A Matter device reaches your network over one of:
- Wi-Fi — joins your normal wireless network
- Ethernet — same, wired
- Thread — a low-power mesh radio (§ 02)
Either way, control traffic is local IP — UDP over link-local IPv6, discovered via mDNS/Bonjour, the same multicast machinery as AirPlay and HomeKit. No cloud round-trips, no vendor app needed for control. It also means Matter assumes a flat residential network: one subnet, multicast allowed. Routers and VLANs are where it stops working.
Thread, and what it has to do with anything
Thread is one of the transports Matter can run over: a low-power, self-healing mesh radio (802.15.4 — the same silicon family as Zigbee) built for battery devices that can’t afford Wi-Fi’s power budget — sensors, buttons, locks.
Thread devices can’t talk IP to your LAN directly; they need a Thread Border Router to bridge the mesh onto your network. You probably already own one — by 2026 almost every ecosystem hub is a TBR:
- Apple — HomePod mini, HomePod 2, recent Apple TV 4K
- Amazon — Echo 4, Echo Hub, Echo Studio, recent Echo Shows, eero
- Google — Nest Hub 2, Nest Hub Max, Nest Wifi Pro
Two distinctions that save a lot of confusion:
- Thread ≠ Matter. Thread is plumbing; Matter is the language. Some Thread devices speak HomeKit-over-Thread or proprietary protocols instead.
- A Matter Wi-Fi device needs no border router at all. It’s just another client on your LAN.
Commissioning, and why Bluetooth is in it
Pairing a brand-new Matter device is called commissioning, and the very first step usually happens over Bluetooth LE: the commissioner sends the device your Wi-Fi credentials (or the Thread network key) over BLE, the device joins the network — and BLE is never used again. Everything after that is plain IP.
That’s why phones and ecosystem hubs make good first commissioners: they have BLE radios and, for Thread, the network credentials to hand out. It is also why the printed QR code on the box is a one-shot: a commissioning passcode is single-use. Adding a second controller later needs a freshly generated code, from an enhanced commissioning window the first controller opens on request.
Which raises the obvious question: why would you add a second controller at all?
Fabrics & multi-admin: one device, many controllers
A Matter fabric is a controller’s trust domain — a set of cryptographic credentials a controller installs on a device. The crucial design choice in Matter is that a device can belong to several fabrics at once. The spec floor is five — and since each fabric slot costs the device persistent storage, the floor is also what most devices ship. Treat five as your planning number. Each controller talks to the device directly and locally; none of them knows or cares about the others.
A single plug can happily serve four admins simultaneously — an ecosystem app, a home automation controller, the vendor’s own app, and something like Home Assistant — with no cross-interference. Removing one fabric leaves the others untouched; only a factory reset on the device wipes them all.
Multi-admin is the single feature everything in these notes is built on: it is what lets an ecosystem you already own do the hard first step, and something else join afterwards over plain IP. That story is № 2 — The controller.
Attestation, and the word “uncertified”
Matter devices carry a certificate issued against a Vendor ID the manufacturer holds from the CSA. At commissioning the process runs one way: the commissioner checks the device’s certificate. A device whose certificate doesn’t chain to a production CSA vendor is flagged — Apple Home, Alexa and Google Home all show some version of “this accessory is not certified”, with a proceed-anyway option.
The specification reserves test vendor IDs (0xFFF1–0xFFF4) for
exactly this: development, and software that isn’t a shipped product. Every open-source
bridge and controller you have heard of uses one, because a real vendor ID means paid CSA
membership plus per-product certification.
Two consequences show up later in these notes, and both are expected behaviour rather than bugs:
Bridges
A Matter bridge is a device that presents things which aren’t Matter — Zigbee bulbs, proprietary RF sensors, whatever a hub already speaks — as Matter endpoints behind one accessory. Aqara, SwitchBot and Hue hubs all do this, and so does software: Homebridge’s Matter successors, Home Assistant, and this plugin’s own export half all publish a bridge rather than a fleet of individual devices.
From the network’s point of view a bridge is just a Matter device with a lot of endpoints. Everything above — fabrics, multi-admin, attestation — applies to it unchanged. That symmetry is the whole reason this plugin can work in both directions.