How Matter works and what it changes for smart home buyers
How Matter works: the application layer, Thread and Wi-Fi transport, controllers and multi-admin, and what it changes when you buy smart home devices.
This article covers what the Matter standard is, how a Matter device talks to a controller, and what the logo on a box does and does not promise. It does not cover setting up any specific ecosystem app, or Thread network design beyond what a buyer needs to know.
You are standing in a shop, or scrolling a listing, and the box says “Works with Matter”. The obvious question is whether that logo means the device will work with the app you already use, and whether it will keep working if the manufacturer loses interest. The short answer is yes to the first and mostly yes to the second, with a few conditions that are worth understanding before you pay.
What Matter is
Matter is an application-layer standard for smart home devices, published by the Connectivity Standards Alliance, the same industry group that maintains Zigbee. The first version appeared in late 2022 and the specification has been revised several times since, each revision adding device types that the first one left out.
The word “application layer” is the important one. Matter does not define a new radio. It defines what a device is (a light, a plug, a door lock, a thermostat), what each kind of device can do, and how a controller asks it to do those things. That description travels over ordinary IP networking, which is why Matter runs on Wi-Fi and Ethernet and on Thread, a low-power mesh radio that also carries IP.
Before Matter, each ecosystem had its own way of describing a light bulb. A bulb that supported one voice assistant needed separate integration work to support another, and the manufacturer had to keep several cloud connections alive. Matter replaces that with one shared description and one local protocol, so a device that speaks Matter can be controlled by any Matter controller without the manufacturer doing anything extra.
How Matter works under the hood
A Matter device presents itself as a set of endpoints, and each endpoint carries a set of clusters. A cluster is a bundle of related attributes and commands: the on/off cluster has an attribute that says whether the device is on and a command that toggles it; the level control cluster handles dimming; a door lock cluster handles locking, unlocking and user codes. The standard defines these clusters once, and every device type is built from them.
When you add a device, you scan a QR code or type a pairing code. That code carries a discriminator and a setup passcode. The controller finds the device, either over Bluetooth Low Energy for a device that is not yet on a network, or over the local network for one that already is, and runs a commissioning exchange. During commissioning the controller checks the device’s attestation certificate, which proves it is a certified product from a known manufacturer, and then installs its own credentials on the device. From that point the two sides authenticate each other with certificates on every session. Bluetooth is used only for this setup step: Matter does not run over Bluetooth mesh, which is a separate standard used mostly for lighting.
The set of controllers and devices that share one set of credentials is called a fabric. A device can belong to several fabrics at once, which is the feature the marketing calls multi-admin. In practice it means one bulb can be in your phone’s ecosystem and your partner’s different ecosystem and a local hub at the same time, and each can control it without asking the others.
Once commissioned, control is local. The controller sends a command over the IP network and the device acts on it. There is no requirement for either side to reach the internet. Manufacturers can still offer cloud features through their own app, but the Matter path works without them, which is the foundation of a local-only smart home.
Thread deserves a word because it is the transport most battery devices use. Thread is a mesh radio built on the same physical layer as Zigbee, but it carries IPv6 packets. A Thread network needs a border router, a device with both a Thread radio and a Wi-Fi or Ethernet connection, to move packets between the mesh and the rest of the home. Many hubs, speakers and displays include one. A Matter device that uses Thread talks to the controller through that border router, and the controller does not need to know which radio was involved.
What Matter changes for smart home buyers
The first change is choice. A device carrying the Matter logo will work with any ecosystem that has a Matter controller, which now includes the major voice assistants, the large phone platforms and the popular open-source home controllers. You no longer need to check a compatibility list for each app. You check for one logo.
The second change is that the cloud stops being load-bearing for basic control. Because the Matter path is local, a device keeps responding to your controller when your internet connection is down, and it keeps responding after the manufacturer’s servers go away. That is a real change for the category. Plenty of devices sold in the past decade became decorative when their maker shut a service down.
The third change is that switching ecosystems becomes cheaper. If you move from one assistant to another, your Matter devices come with you. You commission them into the new controller, and because multi-admin allows several fabrics, you can do it gradually rather than in one weekend.
There is a change on the manufacturer’s side too. Building one Matter implementation is less work than maintaining several cloud integrations, which is why smaller companies have been able to ship devices that work everywhere. Over time that should mean more devices at the cheaper end of the market with broad compatibility.
What Matter does not fix
Matter does not make every feature of a device available to every controller. The standard defines a set of device types and clusters, and a controller can only expose what those clusters describe. A manufacturer’s app may still be the only place to change an advanced setting, run a firmware update or configure a feature the standard has not caught up with. Read the box, or the manufacturer’s page, for which features are “via Matter” and which are “in the app”.
It does not cover every category yet. Early versions handled lights, plugs, switches, sensors, locks, blinds, thermostats and a few others. Later revisions added more, including several appliance types and energy-related devices, but there are still products that have no Matter device type and so cannot be Matter certified. Cameras were one of the notable gaps for a long time.
It does not replace your existing Zigbee or Z-Wave devices. Those radios do not carry IP, so their devices cannot speak Matter directly. What the standard offers instead is a bridge: a hub that talks Zigbee on one side and presents each Zigbee device as a Matter endpoint on the other. Several ecosystem hubs do exactly that, and a good bridge makes older devices usable from a Matter controller. Whether a specific hub bridges a specific device is something you have to check.
It does not make automations portable. Your scenes and routines live in the controller you built them in. Matter moves the device between ecosystems; it does not move the logic that uses the device.
And it does not guarantee quality. Certification checks that the device implements the specification correctly. It says nothing about whether the radio is well designed, whether the firmware is stable, or whether the manufacturer will ship updates. A poorly made device with a Matter logo is still a poorly made device.
How to check a device before you buy
Look for the Matter logo and the certification, then look past it. The listing or the box should say which transport the device uses. “Matter over Wi-Fi” means it joins your Wi-Fi directly and needs no extra hardware; it will also draw more power, which matters for anything on a battery. “Matter over Thread” means you need a Thread border router somewhere in the house, and you should confirm you have one or plan to buy one.
Check which controllers the manufacturer has actually tested. Certification means it should work with all of them; a tested list means it does. If the manufacturer names the controller you use, that is the best signal available.
Check what needs the app. If the feature you are buying the device for is only reachable through the manufacturer’s own app, then Matter has given you local basic control and nothing more for that feature. That may be fine, but decide it knowingly.
For a battery device, look for the firmware update path. A Matter device can receive updates from a controller that supports the update mechanism, but many manufacturers still push updates only through their own app. A device you never open the app for may never be updated.
Finally, if the device is a bridge or a hub, check which older protocols it bridges and how many devices it supports. The bridge is the piece that decides whether the rest of your existing home comes along.
Matter is the first standard in this category that the big platforms have all adopted at once, and that alone makes it the safest default for a new purchase. Understand the transport, know which features live in the app, and the logo will do what it promises.
Written by the IoT Crest editorial team. Facts in this article follow the editorial policy: only well-established behavior is stated and no figures are invented.