The ten radio and application-layer standards behind almost every smart home device, from mesh sensors to line-of-sight remotes. Each explainer covers what it actually does, where it fits, and which hubs speak it — see the Hubs section for the controllers.
A standard from the Connectivity Standards Alliance that defines what a device means and how it's controlled, so one certified device works across Alexa, Google Home, Apple Home, and SmartThings. It doesn't replace a radio protocol — it runs on top of Wi-Fi, Thread, or Ethernet.
An IEEE 802.15.4-based mesh protocol running on 2.4 GHz, with the largest installed base of any smart home radio — sensors, bulbs, and plugs from Aqara, IKEA, Philips Hue, and many others.
A mesh protocol on sub-1 GHz frequencies (region-specific: 868 MHz in the EU, 908 MHz in the US), which avoids competing with 2.4 GHz Wi-Fi traffic. The Z-Wave Alliance enforces strict interoperability certification across brands.
An IPv6-based, low-power mesh protocol purpose-built for battery devices and as the backbone radio for Matter. Needs at least one Thread border router on the network, often built into modern speakers and set-top boxes.
A simple, often one-way radio protocol still used by many older and budget European plugs, blinds, and remotes (including KlikAanKlikUit/CoCo). Typically unencrypted and non-meshed, with no delivery confirmation back to the sender.
A short-range protocol common in locks, sensors, and wearables. Bluetooth Low Energy (BLE) also supports its own mesh profile, and phone-proximity features (auto-unlock, presence detection) almost always rely on it.
A one-way, line-of-sight protocol used by most TV, air conditioner, and AV remotes. Hubs add IR support via a separate "IR blaster" accessory to control legacy devices that have no other smart connectivity.
Devices connect directly to your existing router rather than a separate mesh. Simple to set up, but each device draws more power than a mesh radio, which is why most battery sensors avoid it in favor of Zigbee, Z-Wave, or Thread.
A wired backbone connection used by hubs, border routers, and some fixed devices for the most reliable, interference-free link on the network — important for anything you don't want dropping out during Wi-Fi congestion.
Not a device radio, but the local IP network your hub and devices share. Local-network discovery (mDNS/SSDP) and local API control are what let a hub keep working during an internet outage — a key factor in the "local vs. cloud" comparisons on our Hubs page.
Press play, or tap the door sensor, to follow one message through a mixed-brand home.
Matter and Thread are often mentioned in the same breath, and they are easy to confuse. They do different jobs. Matter is the language a device speaks: it says what a device is (a contact sensor, a lock, a light) and how to control it, the same way for every brand. Thread is the road that messages travel on: a low-power wireless mesh that carries Matter traffic between small, battery-powered devices and your home network.
Common mix-up: Thread and Zigbee use the same kind of radio (IEEE 802.15.4 at 2.4 GHz), but they are not compatible. A Zigbee device cannot join a Thread network, and the other way round. See the stack below for how they differ above the radio.
A Thread border router is the gateway between the Thread mesh and the rest of your home network. Thread devices cannot talk to Wi-Fi or Ethernet directly, so without a border router they can talk to each other but not to your phone or hub. It is the one piece of hardware you need for any Matter-over-Thread device.
Many everyday devices already include a Thread border router, so you may own one. Typical places are smart speakers and displays, streaming boxes, some Wi-Fi routers and some hubs. Not every model has the radio, so check the spec sheet for “Thread border router”. You can also add a dedicated one, for example a Thread-capable radio stick on a Home Assistant system.
Matter over Wi-Fi is the simplest way to run Matter. The device joins your existing Wi-Fi network, just like a phone or a laptop, and speaks Matter on top of it. There is no mesh to build and no border router to buy. You only need a Matter controller to add and manage it. The price is power: a Wi-Fi radio uses far more energy than a Thread radio, so this link suits devices that plug into the wall.
| Matter over Wi-Fi | Matter over Thread | |
|---|---|---|
| Power use | High Best for mains-powered devices | Very low Suits batteries that last for years |
| Extra hardware | None beyond a Matter controller | A Thread border router |
| Network shape | Each device connects to the router | Self-healing mesh that grows with each mains-powered device |
| Data rate | High: video and streaming work | Low: small status and control messages |
| Load on your router | Every device counts as a Wi-Fi client | Light: only the border router joins your network |
| Typical devices | Plugs, bulbs, light strips, cameras, robot vacuums, appliances, displays | Door and window sensors, locks, buttons, blinds, thermostats |
A Matter bridge is a translator. It sits between devices that do not speak Matter, such as Zigbee or Z-Wave sensors and bulbs, and your Matter ecosystem, and makes each of them appear as an ordinary Matter device. That means the lights and sensors you already own can show up in Apple Home, Google Home, Alexa or SmartThings without replacing them. For most homes the bridge is the realistic way to adopt Matter step by step.
| Role | What it does | You need it when | Often built into |
|---|---|---|---|
| Matter controller | Adds devices, keeps the device list and runs automations | Always, for any Matter device | Smart speakers and displays, hubs, phones and tablets |
| Thread border router | Connects the Thread mesh to your home network | You use Matter-over-Thread devices | Speakers, streaming boxes, some routers and hubs |
| Matter bridge | Makes non-Matter devices appear as Matter devices | You want existing Zigbee, Z-Wave or other devices in a Matter ecosystem | Zigbee and Z-Wave hubs, lighting bridges |
Rough figures for a typical home. Walls, materials and interference change real-world range a lot, and some protocols are not a radio at all.
| Technology | Role | Frequency / medium | Typical range | Mesh? | Power use | Data rate | Needs |
|---|---|---|---|---|---|---|---|
| Matter | Application layer | Uses Wi-Fi, Thread or Ethernet | As the link it runs on | Via Thread | Depends on the link | Depends on the link | A Matter controller; a border router for Thread devices |
| Zigbee | Mesh + application | 2.4 GHz (sub-GHz variants exist) | 10–20 m per hop | Yes | Very low | Up to 250 kbit/s | A Zigbee coordinator (hub) |
| Z-Wave | Mesh + application | Sub-1 GHz (868 MHz EU, 908 MHz US) | ~30 m per hop indoors; Long Range much further | Yes Long Range is star | Very low | 9.6–100 kbit/s | A Z-Wave controller (hub) |
| Thread | Network layer (IPv6 mesh) | 2.4 GHz | 10–20 m per hop | Yes | Very low | Up to 250 kbit/s | A Thread border router |
| 433 MHz | Simple one-way radio | 433 MHz (868 MHz variants) | Tens of metres, much less through walls | No | Very low | Very low, one-way | A remote or an RF bridge |
| Bluetooth / BLE | Short-range radio | 2.4 GHz | 10–30 m | Optional Bluetooth Mesh | Very low | 1–2 Mbit/s | Your phone, or a hub for always-on control |
| Infrared (IR) | Line-of-sight signal | Infrared light | A few metres, line of sight | No | Very low | Very low, one-way | An IR blaster |
| Wi-Fi | IP network radio | 2.4 / 5 / 6 GHz | 20–50 m indoors | No Mesh Wi-Fi extends the router | High | From tens of Mbit/s to Gbit/s | Your router |
| Ethernet | Wired link | Cable | Up to 100 m per cable run | No | Low PoE can power the device | 100 Mbit/s to multi-Gbit/s | A switch or router |
| LAN | The home network itself | Wired and Wi-Fi | Whole home | n/a | n/a | Set by your router | A router |
“Zigbee or Matter?” is the wrong first question, because they do not sit at the same level. Every smart home connection is a stack of five layers. Different protocols fill different layers, and a choice on one layer changes what you need on the others.
| Layer | Zigbee sensor | Matter-over-Thread sensor | Matter-over-Wi-Fi plug |
|---|---|---|---|
| 1. Application | Zigbee clusters | Matter | Matter |
| 2. Network | Zigbee mesh | Thread (IPv6 mesh) | IP over your Wi-Fi network |
| 3. Radio | 802.15.4, 2.4 GHz | 802.15.4, 2.4 GHz | Wi-Fi |
| 4. Onboarding | Pairing mode, sometimes an install code | QR code and Bluetooth LE | QR code and Bluetooth LE |
| 5. Controller | Zigbee coordinator or hub | Border router plus Matter controller | Matter controller |
The takeaway: Matter standardises the top of the stack and the onboarding step, and leaves the radio to Wi-Fi, Thread or Ethernet. That is why it can sit on top of Thread but does not replace Zigbee or Z-Wave, which are complete stacks of their own. Compare the full path from device to controller, not a single logo on the box.