Hardware Matrix

Zigbee vs Z-Wave vs Matter: Choosing a Protocol

Published · figures computed from the dataset, last updated

If you are starting a smart home from scratch, the protocol decision matters more than any single device, because it decides which radio infrastructure you buy once and which device catalogue you shop from afterwards. This index currently documents 9 Zigbee, 3 Z-Wave and 8 Matter pairings, so the comparisons below link to real devices rather than spec sheets.

The short version

  • Zigbee — the biggest and cheapest device pool. Needs a coordinator radio (a USB stick on Home Assistant). Mature, boring, works.
  • Z-Wave — sub-GHz, so it penetrates walls better and never fights your Wi-Fi for spectrum. Smaller, pricier catalogue; devices are certified, which cuts both ways.
  • Matter — the newest, designed for multi-platform: one device can serve Home Assistant, Apple Home and Alexa simultaneously. Matter over Thread additionally needs a border router.

What each one asks you to buy

None of the three talks to your platform without a piece of radio infrastructure, and this is the cost people miss when comparing device prices:

  • Zigbee: one coordinator — typically a USB stick running ZHA or Zigbee2MQTT. Mains-powered Zigbee devices (plugs, bulbs) then extend the mesh for free.
  • Z-Wave: one controller stick. Same mesh principle; region-locked radios, so a EU stick will not pair US devices.
  • Matter over Wi-Fi: nothing extra — devices join your existing network.
  • Matter over Thread: a Thread border router. 5 pairings in this index run over Thread, and each device page names the border router requirement explicitly.

How the verdicts fall in this index

Protocol Pairings documented Natively supported
Zigbee 9 5
Z-Wave 3 0
Matter 8 7

"Natively supported" is this site's strictest verdict — the platform speaks to the device with no vendor bridge in between. The verdicts guide unpacks the other two.

Range and interference

Zigbee and Thread share the 2.4 GHz band with Wi-Fi and Bluetooth. In a congested apartment block that is a real constraint — channel planning helps, but you are sharing spectrum. Z-Wave sits at 800–900 MHz depending on region: lower bandwidth, but better wall penetration and a quiet band. All three are mesh protocols, so mains-powered devices relay for battery ones and range compounds as the network grows — a large network is usually more reliable than a small one.

How to actually decide

  1. If you need devices from the widest, cheapest catalogue and run Home Assistant: Zigbee, and accept the coordinator stick.
  2. If you live somewhere with saturated 2.4 GHz spectrum, or want certified locks and security devices: Z-Wave.
  3. If your household spans platforms — Home Assistant plus Apple Home, say — buy Matter where the device exists, because it is the only one of the three designed to serve several controllers at once.

And check the specific device before you order: the whole point of the compatibility matrix is that "supports Zigbee" on a box does not tell you whether the pairing is plug-and-play or an evening of YAML.

Frequently Asked Questions

Can I mix Zigbee, Z-Wave and Matter in one home?
Yes, and most established setups do. Platforms like Home Assistant treat each protocol as its own integration with its own radio, and devices from all three appear side by side as entities. The cost is one coordinator or controller per protocol, not any per-device penalty.
Does Matter replace Zigbee?
Not in the short term. Matter over Thread uses the same 802.15.4 radio hardware as Zigbee, and many manufacturers ship both variants of the same device. Zigbee currently has the larger and cheaper device pool; Matter has broader multi-platform support. A Zigbee network you own today keeps working — the protocols coexist rather than one deprecating the other.
Which protocol works without internet?
All three can run fully locally. Zigbee and Z-Wave never touch the internet at all when paired to a local coordinator. Matter devices commission with a connection available, but once paired to a local controller they operate on your LAN. The internet dependency in most smart homes comes from cloud-bridged devices, not from these protocols.

More guides

Do You Need a Thread Border Router?

What a Thread border router actually does, which devices count as one, and how to tell whether the Matter device in your basket needs one before it will pair.

I²C Address Conflicts, Explained

Why an I²C sensor goes missing in ESPHome, how to read the boot scan, and four ways past an address clash: re-strap, second bus, TCA9548A or software.

ESP32 vs ESP8266 for ESPHome: Which Board?

Choosing between the ESP8266 and the ESP32, C3, S3 and C6 for an ESPHome node: memory, serial ports, ADC and strapping pins, Bluetooth, Thread and Zigbee.

mmWave Radar vs PIR: Choosing a Presence Sensor

Why a PIR loses you when you sit still and a radar does not. How the ESPHome LD2410, LD2412, LD2420 and LD2450 components work, how to tune a radar that holds empty rooms occupied, and how to combine both in Home Assistant.

Natively Supported vs Bridge Needed: What Our Verdicts Mean

The three compatibility verdicts this site assigns, what each one commits you to in hardware and maintenance, and why "works with" on a box rarely tells you which you are getting.