Wi-Fi, Zigbee, Z-Wave, Thread and Matter Explained

Why this matters

A customer hands you a leak sensor they bought online and asks you to "just add it" to the system you installed last year. Whether that takes 2 minutes or cannot be done at all depends on which radio the sensor speaks, which radio your system speaks, and whether anything in the house translates between them. A tech who reads the box and knows what the protocol logo means can answer at the door. A tech who does not will spend half an hour tapping "add device" in an app that was never going to see it.

This card explains the five names on the box in the terms that matter in the field: how far the signal goes, what powers it, whether it needs a hub, whether devices relay for each other, and what each one means when pairing fails.

The first distinction: a radio versus a language

Four of the five names are radios: Wi-Fi, Zigbee, Z-Wave and Thread each describe how bits travel through the air. Matter is not a radio. It is a common language that devices from different makers speak so that one app or one controller can run all of them, and it travels over Wi-Fi, Thread or a wired Ethernet connection.

That distinction resolves the most common confusion in the field. "It's a Matter device" tells you which apps can control it. It does not tell you what radio it uses, so it does not tell you whether it will reach. The box will say "Matter over Thread" or "Matter over Wi-Fi," and the second half is the part that decides range and hub requirements.

Bluetooth Low Energy (BLE) appears on many boxes too. In most connected-home devices it is used only during setup, to hand the device its network credentials from a phone held nearby. It is rarely the radio the device uses afterward.

The four radios in one table

Read the "relay" row carefully. In Zigbee, Z-Wave and Thread, a device plugged into wall power (a smart plug, a wired switch, a powered hub) usually acts as a router, passing messages along for devices farther away. A battery device usually does not, because listening all the time would flatten its battery. So the network is a mesh: the more powered devices in the house, the farther it reaches. A house whose only devices are battery sensors has no mesh at all, just a star of sensors each trying to reach the hub directly.

Wi-Fi does not work this way. Every Wi-Fi device talks straight to a router or a mesh node. A "mesh Wi-Fi system" means the routers relay for each other, not the devices; see related: Mesh Systems, Extenders and Dead Zones.

Each one, in the terms that matter at the door

Wi-Fi. The device joins the customer's home network like a phone does. No hub, which is why it is popular, but it inherits every problem the home network has: the wrong band, a changed password, a weak signal at the equipment, a router that went down. Many connected devices only use 2.4 GHz because it carries farther through walls; the phone setting them up may be on 5 GHz, which is the root of many failed setups. Wi-Fi fundamentals have their own card; see related: Home Wi-Fi for the Trades.

Zigbee. A low-power mesh on 2.4 GHz that needs a coordinator, the hub that forms and runs the network. It shares the 2.4 GHz band with Wi-Fi, so a Zigbee network on a channel overlapping a busy Wi-Fi channel can drop messages. Devices from different makers often pair to a coordinator but may not expose every feature, which is why "it paired but the app shows it as a generic switch" is a Zigbee classic.

Z-Wave. A low-power mesh on a sub-GHz band (around 908 MHz in North America, around 868 MHz in Europe). The lower frequency passes through walls and floors better than 2.4 GHz and never collides with Wi-Fi. Two things to know: a Z-Wave device is built for one region's frequency, so a unit bought from an overseas seller will not talk to a North American controller at all; and classic Z-Wave limits how many hops a message can take through the mesh (four), so a device far from the controller needs powered devices placed along the path. A long-range variant uses a direct star link instead of the mesh and reaches much farther, but only to a controller that supports it.

Thread. A low-power mesh on 2.4 GHz built on internet addressing (IPv6), so every device has a real network address. There is no single hub. Instead the Thread network reaches the home network through a border router, a role built into some smart speakers, displays and hubs. A house can have several border routers and they share one Thread network, which makes it resilient. A house with none cannot use a Thread device at all, however close it is to the Wi-Fi router.

Matter. The shared language. A Matter device is added ("commissioned") by scanning a QR code or typing a numeric setup code printed on the device or its box, usually with the phone close enough to reach it over Bluetooth. Matter supports multi-admin: one device can be controlled from more than one ecosystem at once, each of which adds it separately. Bridges exist that make older Zigbee or Z-Wave devices appear as Matter devices. As of 2026 the range of device types Matter covers is still widening and support differs between controllers; check what the customer's controller supports in its current documentation, not from memory.

When pairing fails: what the protocol tells you to check

The "already claimed" row catches techs who have never met it. A Matter device that was commissioned before, by a previous owner or a returned-merchandise sale, may refuse a new commissioning until it is factory reset. The box looks new and the device is not.

Worked example: the basement leak sensor that would not join

The customer has a whole-house water shutoff your shop installed, controlled by its own hub. They bought a Matter-over-Thread leak sensor for the crawlspace hatch and want it to trigger the shutoff. It will not add.

Layer 1, the language. Does the shutoff's hub speak Matter as a controller? The tech checks the hub's current documentation: it does not. It runs its own sensors on its own radio and accepts no outside sensors. So no amount of pairing will make this sensor close this valve directly. That is the answer to the customer's actual request, and it took 3 minutes of reading.

Layer 2, could it work another way? The customer also has a smart speaker that is a Thread border router and a Matter controller. The sensor could join that ecosystem, and that ecosystem could send an alert. It still could not close a valve whose hub does not listen to it. The tech explains: the new sensor can send an alert to their phone; the shutoff will still only close on its own sensors.

Layer 3, the customer wants the alert anyway. The tech tries commissioning from the customer's phone with the speaker's app. It fails at "connecting to device." The tech works the protocol table:

• Radio: the box says Matter over Thread. So a Thread border router is required, and the speaker is one.
• Border router online? The speaker is upstairs, about 35 ft and one floor from the crawlspace hatch. It is online.
• Path through the mesh? The house has no other Thread devices, so there are no routers between the speaker and the hatch. The sensor is a battery device; it does not relay. It must reach the speaker directly, through a floor and a foundation wall. That is the likely failure.
• Setup code used before? The box was sealed. Unlikely.

The tech moves the sensor (still in setup mode) to the top of the basement stairs, about 15 ft from the speaker, and commissions it. It joins in under a minute. Then the tech carries it back to the hatch. The app shows it offline within a few minutes.

The fix, explained to the customer: a mains-powered Thread device (a smart plug that is a Thread router is the cheap version) on an outlet near the basement stairs gives the sensor something to reach. The customer buys one; on the return visit it goes in a hallway outlet, joins the Thread network, and the sensor at the hatch stays online through a 24-hour check on the app.

What would have flipped the answer: if the box had said Matter over Wi-Fi, the fix would have been a Wi-Fi signal problem at the hatch, a different sibling's territory. If the sensor had been Z-Wave, the region check would have come first, and if it were right, the sub-GHz radio would likely have reached through the floor without help, which is the one practical advantage Z-Wave holds in basements and crawlspaces.

The failure to watch for

The most expensive mistake in this subject is promising integration based on a logo. "Works with Matter" on two devices means they can both be added to the same controller. It does not mean one will trigger the other's hardware, and it does not mean your installed system is a controller at all. Before quoting any "add this to what you have" job, write down three things for both devices: the radio, the controller each needs, and whether the installed system accepts outside devices. If you cannot fill all six blanks, you do not yet know whether the job is possible.

References

• Connectivity Standards Alliance, published materials on Zigbee and the Matter standard (the body that maintains both)
• Thread Group, published overview of Thread networking and border routers
• Z-Wave Alliance, published materials on Z-Wave regions and certification
• See related: Home Wi-Fi for the Trades
• See related: Mesh Systems, Extenders and Dead Zones