Matter vs Zigbee vs Z-Wave: Controllers, Radios and Bridges

Z-Wave vs Matter is not a like-for-like fight: Z-Wave is a complete sub-GHz wireless stack, Matter is an application layer over Wi-Fi, Ethernet or Thread, and Zigbee is a complete stack that mostly lives on 2.4 GHz. Buy Matter for multi-ecosystem devices, Zigbee for cheap sensors and bulbs, and Z-Wave for locks and noisy 2.4 GHz buildings.

That category error is where most Matter vs Zigbee vs Z-Wave comparisons go wrong. Zigbee and Z-Wave are complete stacks: a radio, a mesh, and an application language, sold as one thing. Matter is only the top layer. The CSA’s own FAQ says it “natively supports Wi-Fi, Ethernet, and Thread” and uses Bluetooth Low Energy for setup. So the real decision is two questions stacked on each other: which radio carries your devices, and whether a standard application layer sits on top. Answer them separately and the comparison stops being confusing.

The spec table

Nothing here comes from a bench. The figures are from the standards bodies, the chip vendor that owns the Z-Wave silicon, and the Home Assistant integration docs, because those pages are where the limits that actually bite are written down.

The Zigbee figures are from the CSA Zigbee FAQ, except the 32-direct-child limit, which the ZHA docs attribute to the zigpy library rather than the Zigbee standard; the Thread figures are from OpenThread; the Z-Wave figures are from a Silicon Labs Long Range presentation dated March 2021, which is a vendor slide deck and should be read as one. Z-Wave frequencies come from the ZWA-2 spec listing; the 1.5-mile figure comes from CE Pro’s background on Long Range, which calls it a theoretical distance with no walls or structures in the way, not from the CES 2026 device announcement.

Z-Wave vs Matter, head to head

Pick Matter when a device has to work in Apple Home, Google Home, Alexa and Home Assistant at the same time. Pick Z-Wave when range through walls, a quiet sub-GHz band and a mature lock catalog matter more than ecosystem reach. They do not compete at the same layer, so plenty of houses run both and join them at the controller.

Ecosystem reach is the difference most buyers feel. A Matter device joins each controller’s fabric directly, with the Home Assistant Matter docs setting a floor of five fabrics per device. Matter 1.6, released 17 June 2026, adds Joint Fabric, which “allows multiple user-authorized controllers to co-administer a single shared Matter network.” Z-Wave has one primary controller, and other platforms see its devices only if that controller exports them. The multi-admin sharing guide covers the Matter side.

Getting Z-Wave into Matter is harder than the marketing suggests. The CSA’s bridge definition covers Z-Wave, but Home Assistant’s Matter documentation states that “Home Assistant is not a bridge itself,” so it will not present a Z-Wave lock to Apple Home as a Matter device. The Z-Wave Alliance still lists “bridging Z-Wave with Matter” among its 2026 priorities. Home Assistant’s working route to Apple Home is its HomeKit Bridge integration, which speaks HomeKit rather than Matter and caps each bridge at 150 accessories.

Radio and range favour Z-Wave; bandwidth favours Matter. Long Range adds its own channels (912 and 920 MHz in the US, 864 and 866 MHz in the EU, per the ZWA-2 listing), and CE Pro counted 125 certified Long Range devices in January 2026, from door locks to security panels. Z-Wave’s 100 kbit/s ceiling suits a lock and rules out a camera, which Matter 1.5 standardised over WebRTC. For a lock or a sensor at the far end of the garden, pick Z-Wave; for anything that must appear in more than one app, buy Matter.

Where Zigbee wins

Zigbee wins on catalog and price. The CSA describes a “self-organizing, self-healing mesh topology” with “hundreds of nodes per network” and transmission distances of “10 to 100 meters, depending on power output and environmental characteristics.” Every mains-powered bulb and plug becomes a router, so coverage fills in as you buy things.

It loses on spectrum and on single points of failure. It shares 2.4 GHz with your Wi-Fi, which is why the ZHA docs tell you to place the coordinator “away from any Wi-Fi access points,” to use “an adequately long shielded USB extension cable connected to a USB 2.0 port,” and to stick to channels 15, 20 or 25. The same docs are blunt that there is “only one Zigbee coordinator per network” and that the coordinator’s 32 direct-child limit makes routers mandatory past a handful of devices. Lose the coordinator’s backup and you re-pair everything. Zigbee PRO 2023 added a Dynamic Link Key and trust-center swap-out, but the devices already on your shelf mostly predate it.

Zigbee 4.0, announced 18 November 2025, adds “the European 800 MHz and North American 900 MHz PHY” and stays “fully backward compatible with Zigbee 3.0.” Its sub-GHz mesh brand, Suzi, only opened product certification on 2 September 2026, so treat long-range Zigbee as a roadmap item rather than something to shop for.

Where Z-Wave wins

Z-Wave wins the moment 2.4 GHz is crowded, which in an apartment block is always. It runs in region-specific sub-GHz bands rather than the 2.4 GHz band used by many Wi-Fi and Thread devices. Certification is mandatory, which is why the Z-Wave Alliance can claim products “work seamlessly between brands and versions” and why locks are the classic Z-Wave category.

It loses on cost, speed and geography. Data rates of 9.6, 40 or 100 kbit/s are fine for a switch and hopeless for anything richer. The classic mesh is capped at 4 hops and an 8-bit node address, so “200+ nodes” is the ceiling. Radios are region-locked: devices and the controller must support the same region, and the Home Assistant Z-Wave docs make you pick a region for the controller. Those docs recommend an 800-series adapter with firmware 7.23.2 or newer, prefer S2 over S0, and name a USB extension cable as the first troubleshooting step.

Z-Wave Long Range changes the network’s shape rather than fixing the mesh: a star topology, a 12-bit address space for 4000 nodes, up to +30 dBm and about a mile line of sight, but also “Routing: not supported” and “direct inclusion only.” That is an upgrade for the far shed and a downgrade for everything that used to hop.

Where Matter wins

Matter wins on who gets to be the controller. The Home Assistant Matter docs note that “each device should be able to at least support 5 different fabrics simultaneously,” so Home Assistant, Apple Home and Google Home can all own the same bulb at once with no bridge or cloud in the middle. Neither Zigbee nor Z-Wave has an equivalent; each network has one boss. The spec also keeps growing into categories the older stacks never standardised: Matter 1.4 added solar, batteries, heat pumps and water heaters, and Matter 1.5, released 20 November 2025, added cameras over WebRTC, closures, soil sensors and tariff data. Matter 1.6 followed in June 2026 with setup and sharing changes, including commissioning entirely over NFC. Controller support for those features must be checked separately.

It loses on operational fuss, and the losses are all network-layer. A Thread device needs a border router, and OpenThread caps a partition at 32 routers. IPv6 and mDNS have to flow freely between the controller and the devices, which is precisely what an IoT VLAN breaks; if you segment, the IPv6 requirements guide covers the discovery and routing constraints. The HA docs also warn that OTA updates do not work through Apple border routers, that “the official Hue integration brings all Hue unique features” where Matter exposes only the basics, and, in a line worth framing, “Don’t assume Matter support when you see a Thread logo on a device.” Matter is also local-only, so remote access still needs “an internet-connected controller” in the house; the offline limits post covers what keeps working when the connection drops.

Bridging is the escape hatch

The three are not exclusive because Matter was designed to absorb the other two. The CSA defines a bridge as a device that “translates from one protocol to another, allowing non-Matter smart home devices (such as those using Zigbee or Z-Wave) to connect to a Matter Fabric via the Bridge.” A Hue Bridge is the obvious example: Zigbee bulbs on one side, a Matter fabric on the other. An existing Zigbee or Z-Wave estate is not a sunk cost. It is a bridged one, with the Z-Wave caveats noted above.

What to actually build on

For a Home Assistant house starting from scratch, the boring answer is a Zigbee coordinator plus a Thread border router, and Matter for new purchases when its supported device features and multi-admin access are useful. Choose Thread for suitable low-bandwidth devices and Wi-Fi or Ethernet for video. Zigbee gets the cheap bulk: bulbs, plugs, contact sensors. The Thread vs Zigbee comparison walks through why the two meshes should not share a coordinator, and the border router guide covers how many you need. Settle the controller before any radio; what a Matter controller is explains which hubs already contain one.

Each protocol needs its own radio, and Nabu Casa’s adapters set the price floor on Home Assistant:

The ZBT-2 limit catches people: CNX Software notes “you can’t use Zigbee and Thread at the same time” on it, so a house running both meshes needs two radios. The ZWA-2 launched at $69 in August 2025.

Add Z-Wave only for specific jobs: locks, anything in a building where 2.4 GHz is unusable, or an outbuilding where Long Range’s mile actually matters. Do not build a whole house on it in 2026 unless price is no object, and do not buy Z-Wave hardware from another region on the used market.

Skip Matter entirely if you run one ecosystem, never intend to change it, and every device you want has a good native integration. Multi-admin is one reason to adopt Matter. A working native integration can remain useful, and Matter over Wi-Fi does not require a Thread border router. The Matter over Wi-Fi vs Thread comparison covers the transport choice. If pairing goes wrong once you commit, the pairing failures guide maps each symptom to its layer.

FAQ

is z-wave better than matter

Neither is better outright, because they work at different layers. Z-Wave is the better choice for locks, long range and buildings where 2.4 GHz is crowded, thanks to its sub-GHz radio and mandatory certification. Matter is better when one device has to work in Apple Home, Google Home, Alexa and Home Assistant without a bridge.

can z-wave devices work with matter

Only through a bridge, because Z-Wave is not one of Matter’s transports. A hub has to translate each Z-Wave device onto a Matter fabric, and the Z-Wave Alliance still lists that bridging work among its 2026 priorities. Home Assistant runs Z-Wave and Matter side by side, but its documentation says it is not a bridge itself.

will matter replace zigbee and z-wave

No, not soon. Matter has no radio of its own, and both older standards are still moving: Zigbee 4.0 arrived in November 2025 with sub-GHz support, and Z-Wave Long Range reached 125 certified devices by January 2026. Matter’s design assumes coexistence, absorbing Zigbee and Z-Wave estates through bridges instead of forcing replacements.

do i need a hub for zigbee, z-wave or matter

In practice yes, all three need one, but a different kind. Zigbee needs a single coordinator, Z-Wave needs a controller whose radio matches your region, and Matter needs a controller such as a smart speaker hub or Home Assistant. Matter devices on Thread also need a border router, which many smart speaker hubs already include.