Matter and Thread: the standards trying to unify the smart home
How Matter, an IP-based application standard, and Thread, a low-power wireless mesh, try to make smart-home devices from rival makers work together.
Buy a smart bulb, a smart lock and a smart thermostat from three different makers, and you can easily end up with three apps, two hubs and a nagging sense that none of it quite talks to the rest. For years that was the ordinary experience of building a smart home: plenty of clever devices, very little agreement on how they should cooperate. Matter and Thread are two attempts to fix that, and because they tend to be mentioned in the same breath, it is easy to lose track of what each one actually does.
The short answer is that they solve different halves of the same problem. This guide separates them, shows how they fit together, and is honest about how well the promise holds up in a real house today.
The problem: too many islands
A smart home is rarely bought all at once. People add a video doorbell one year, some coloured bulbs the next, a robot vacuum after that. Each device tends to arrive with its own app, and often its own small hub that plugs into the router. Underneath, the devices may speak entirely different wireless languages — some use Wi-Fi, others use older low-power radio protocols such as Zigbee or Z-Wave, and a good many rely on the maker’s own cloud service. Those choices are explained in more depth in our guide to home-automation protocols.
The result is fragmentation. A bulb bought for one platform might refuse to appear in another. A hub from one brand cannot see a sensor from a rival. Shoppers learned to hunt for “works with” badges on the box, and even then compatibility was patchy. Worse, when a company folded or switched off a cloud service, perfectly good hardware could stop working overnight. Matter was designed to break down those walls between islands, so that a device from any member manufacturer can be controlled by any compatible system.
What Matter is — and what it is not
Matter is an application-layer standard for smart-home devices. It began life in 2019 as a project called Connected Home over IP, and the first version arrived in late 2022. It is stewarded by the Connectivity Standards Alliance, the industry group that was previously known as the Zigbee Alliance. The word to hold onto is Matter, and the word to hold onto about that word is application layer.
An application layer defines the common language and data model that devices use to describe themselves and take instructions. Under Matter, a “door lock” means the same thing to every controller: the same commands to lock and unlock, the same way of reporting whether the bolt is thrown. A dimmable light exposes brightness in an agreed way. Because every certified device and every certified controller share that vocabulary, they can understand one another without a custom integration written for each pairing.
Here is the part that causes the most confusion. Matter is not a radio. It is not a wireless technology, and it does not replace Wi-Fi. It carries no signal of its own. Matter is built on the Internet Protocol (IP) — the same addressing scheme that runs the wider internet — which means it needs some underlying network to travel over. That underlying network is where Thread comes in.
What Thread is
Thread is a low-power wireless networking technology. It uses the same short-range radio hardware as Zigbee (the 802.15.4 standard), but with an important difference: Thread is built around IPv6, so every device on a Thread network has a proper internet address from the outset. Where Zigbee and Z-Wave need a hub to translate their traffic into something the rest of your network understands, a Thread device is already speaking IP. The term to keep is Thread.
Two features matter most. First, Thread is a mesh network. Mains-powered devices — a plug, a bulb, a wired sensor — relay messages for one another, so coverage grows as you add hardware rather than straining a single hub. If one node drops out, traffic reroutes around it; the network is described as self-healing. Second, because a Thread mesh runs on its own low-power radio, it needs a bridge to reach your ordinary home network. That bridge is a Thread border router.
A border router sits with one foot in the Thread mesh and one foot on your Wi-Fi or Ethernet, passing IP packets between the two. You rarely buy one as a standalone box; the role is usually built into a smart speaker, a display or a hub you already own, and a home can have several working together. Functionally it behaves like a gateway between two networks that would otherwise never meet.
The key distinction: a layer, not a transport
If you take one idea from this guide, take this: Matter is the language, and Thread, Wi-Fi and Ethernet are the roads the language travels on. Matter says what a message means. The transport moves it from one device to another. They operate at different levels, which is exactly why a single device needs both.
Matter can run over any of three transports. Low-power, battery-sensitive devices — locks, contact sensors, small bulbs — tend to use Thread, because it sips power and forms a resilient mesh. Devices that need more bandwidth, such as cameras, generally use Wi-Fi. Mains-powered hubs and bridges often sit on Ethernet. In every case the Matter language is identical; only the road underneath changes.
| Matter | Thread | |
|---|---|---|
| What it is | An application-layer standard | A wireless mesh network |
| Its job | Defines what devices say and how they are controlled | Carries the messages between low-power devices |
| Level | The language | One of the transports (with Wi-Fi and Ethernet) |
| Needs | A transport to run over | A border router to reach the home network |
| Is it a radio? | No | Yes |
In short: Matter is a shared language that lets smart-home devices from different makers understand one another, while Thread is one of the low-power radio networks that language can travel over. Matter is the layer; Thread, Wi-Fi and Ethernet are the transports. A device usually uses both — Matter to be understood, and Thread or Wi-Fi to be heard.
Commissioning: how a device joins
Adding a Matter device is called commissioning, and it leans on the same IP plumbing that makes the wider internet of things tick. You scan a QR code or type a numeric setup code printed on the device or its packaging. During onboarding the device typically uses Bluetooth Low Energy — a brief, short-range link — to hand over the credentials it needs, after which it joins the Thread mesh or the Wi-Fi network and does its everyday work there.
One genuinely useful feature is multi-admin. A commissioned device can be shared with more than one ecosystem at once, so the same lock might be controlled by two different platforms in the same household without being reset and re-added. That is the interoperability promise made concrete: the device belongs to the home, not to a single app.
The reality today
The standard has grown steadily. The first release covered a solid core of everyday categories — lighting, smart plugs and switches, thermostats and other heating and cooling controls, door locks, window coverings such as blinds, a range of sensors including contact and occupancy, plus media devices and bridges that pull older kit into the fold. Later revisions widened the net to major appliances, robot vacuums, energy-management hardware and, after a conspicuous early absence, cameras. The direction of travel is clear even if the pace is measured.
The rough edges are just as real, and pretending otherwise helps nobody:
- Border-router coordination. Early on, Thread border routers from different brands did not always pool into a single shared mesh, so a home could end up with several separate Thread networks that behaved less well than one large one. This has improved but can still trip people up.
- Feature regressions. A device controlled through Matter sometimes exposes fewer options than it does in the maker’s own app. The basics work; a bespoke lighting effect or a niche setting may not carry across.
- Setup friction. Commissioning is meant to be a single scan, and often is, but firmware quirks, stubborn codes and the occasional factory reset still happen.
- Not everything upgrades. An existing device only speaks Matter if the maker ships firmware for it or a bridge translates on its behalf. Plenty of older hardware never makes the jump.
None of this means the effort has failed. It means a broad, multi-vendor standard is being retrofitted onto a messy real-world market, and that is slow, unglamorous work.
Where this leaves you
If you are buying now, a few habits help. Look for the Matter logo on the box, and check which transport a device uses, because a Thread device will want a border router somewhere in the house while a Wi-Fi one will not. Treat multi-admin as a bonus rather than a guarantee, and expect the first setup of any given brand to be smoother than the second only after a firmware update or two. Above all, keep the two words straight: Matter decides what your devices say to one another, and Thread — alongside Wi-Fi and Ethernet — decides how the words get there. Understanding that split is the difference between a smart home that feels like one system and a drawer full of clever, lonely gadgets.