Z-Wave
Z-Wave is a sub-GHz mesh protocol (908.4 MHz in North America, 868.4 MHz in Europe) governed by the Z-Wave Alliance, known for strict certification, strong cross-brand interoperability, and zero Wi-Fi interference. Devices pair to a Z-Wave controller (SmartThings, Hubitat, Home Assistant with a USB stick, Homey), and it is the incumbent standard for locks, security sensors, and professionally installed systems.
The sub-GHz band is Z-Wave’s defining trait: it penetrates walls better than 2.4 GHz and never contends with Wi-Fi, Bluetooth, Zigbee, or Thread, at the cost of lower bandwidth and region-specific frequencies (a US device will not join an EU network). Every certified device must pass Alliance interoperability testing and expose standard command classes, so cross-brand compatibility is more dependable than Zigbee’s — a certified device works with any certified controller, at least for its standard features.
The trade-offs are a smaller, pricier catalog and a slower release pace than the Zigbee/Matter world; our dataset tracks 2,311 Z-Wave devices via the open-source Z-Wave JS project, versus 5,405 for Zigbee. Classic Z-Wave meshes are limited to 232 nodes and four routing hops — figures the newer Z-Wave Long Range mode rewrites entirely (see that entry).
| North American frequency | 908.42 MHz, with a second channel at 916 MHz for the 100 kbit/s rate |
|---|---|
| European frequency | 868.42 MHz; Australia and New Zealand use 921.42 MHz, and other regions differ again |
| Data rates | 9.6, 40, and 100 kbit/s — a fraction of Zigbee’s 250 kbit/s, and enough |
| Classic mesh limits | 232 nodes per network, four routing hops maximum |
| Devices in this dataset | 2,311, from the open-source Z-Wave JS configuration database |
| Hubs with the radio | Hubitat C-8 and C-8 Pro, Aeotec Smart Home Hub, SmartThings Hub v2, Homey Pro and Bridge, Ring Alarm Pro, Home Assistant with a USB stick |
What the sub-GHz band actually buys — and costs
Radio physics does the work. At 908 MHz the wavelength is roughly 33 cm against 12 cm at 2.4 GHz, and longer waves diffract around obstacles and pass through plasterboard, brick, and floors with less loss. In a two-storey house with a Z-Wave lock in a metal-framed door, that difference is not marginal — it is the difference between a device that reports reliably and one that reports when it feels like it.
The band is also nearly empty. Wi-Fi, Bluetooth, Zigbee, Thread, wireless headphones, and microwave ovens all crowd 2.4 GHz; sub-GHz in a residential setting carries almost nothing but Z-Wave and a few weather stations. In an apartment block with thirty visible Wi-Fi networks, this is the single strongest argument for Z-Wave and the reason installers still specify it for security devices.
You pay for it in three ways. Bandwidth is 100 kbit/s at best, which is fine for switches and sensors and useless for anything resembling streaming. The catalogue is smaller and dearer — 2,311 devices in this dataset against 5,405 Zigbee ones, at noticeably higher prices. And frequencies are regional, so hardware bought in the wrong market is scrap.
The regional frequency trap
Z-Wave radios are built for a band and cannot be moved to another one. A North American 908.42 MHz dimmer will never join a European 868.42 MHz controller, no firmware update will change that, and there is no adapter. Australia and New Zealand are on 921.42 MHz, and Japan, India, Hong Kong, and several other markets each have their own allocation.
This catches people in two places. Second-hand marketplaces are the first: a bargain Z-Wave lock shipped from a US seller to a European buyer is a paperweight, and listings almost never say so. Global marketplace listings are the second, where the same model number is sold in several frequency variants and the region is buried in a suffix — EU, US, ANZ — that is easy to skim past.
Before any Z-Wave purchase, match the region code on the device to the region of your controller. Our Z-Wave device pages carry the frequency variant, and the Z-Wave in 2026 guide sets out the full table.
Certification is the product
The reason Z-Wave interoperability feels different from Zigbee’s is that the Z-Wave Alliance tests it. Every certified device must implement standard command classes and pass interoperability testing before it can carry the badge, and manufacturers cannot route core functionality through private extensions the way Zigbee vendors routinely do. A certified sensor works on a certified controller, and that claim survives contact with reality far more often than the Zigbee equivalent.
Backward compatibility is enforced with unusual discipline. Chip generations run 300, 500 (Z-Wave Plus, 2013), 700 (2019), and 800 (2021 onward), and all of them interoperate on the same network — a switch from 2010 joins an 800-series controller today. From the 700 series on, S2 security and SmartStart are mandatory rather than optional, which is why current Z-Wave hardware is encrypted by default in a way most Zigbee hardware is not.
The structural weakness is concentration. Silicon Labs has been the only volume supplier of Z-Wave silicon since it bought the business from Sigma Designs in 2018. The specification was opened in 2020 and alternative implementations have been in progress since, but one vendor setting the roadmap explains both the consistency and the price.
The mesh, and what Z-Wave JS changed
A classic Z-Wave network holds up to 232 nodes and routes across at most four hops. Mains-powered devices route; battery devices do not, with the exception of some FLiRS devices such as locks that listen on a beam. Routes are discovered and repaired automatically through explorer frames, but a network reorganised heavily — many devices moved or removed — benefits from a route rebuild, ideally overnight, since it is chatty.
Four hops is a real ceiling in a long building. If the far end of the house is five relays away, no amount of adding devices will help; that is the scenario Z-Wave Long Range exists for, and the reason its star topology matters more than its headline range figure.
For DIY users, the Z-Wave JS project reset the picture. It is an open-source driver with a community-maintained configuration database covering the 2,311 devices we track, it powers Home Assistant’s Z-Wave integration, and with zwave-js-ui it exposes inclusion, S2 handling, parameter editing, and firmware updates in a web interface. Running a Z-Wave network on a USB stick with no vendor hub used to be an expert activity; it is now roughly as approachable as Zigbee2MQTT.
Frequently asked questions
Is Z-Wave dead in 2026?
No, but it is a specialist choice rather than a default. New devices keep certifying, the 800-series silicon and Long Range are recent, and Z-Wave still dominates professionally installed locks and security sensors. What has changed is that Apple, Google, and Amazon have no Z-Wave path at all, so it now lives inside hubs — Hubitat, SmartThings, Homey Pro, Ring Alarm Pro, Home Assistant — rather than in mainstream ecosystems.
Which hubs still support Z-Wave?
A short list: Hubitat Elevation C-8 and C-8 Pro, the Aeotec Smart Home Hub and older SmartThings Hub v2, Homey Pro and Homey Bridge, and Ring Alarm Pro. Home Assistant supports it through a USB stick running Z-Wave JS. Nothing from Apple, Google, Amazon outside Ring, Aqara, or IKEA has a Z-Wave radio, and the SmartThings Station dropped it.
Will a US Z-Wave device work in Europe?
No. The radios are band-specific — 908.42 MHz in North America against 868.42 MHz in Europe — and this cannot be changed in firmware. The device will simply never be seen by the controller. Always match the region code, and be especially careful with second-hand purchases and international marketplace listings, which is where nearly all of these mistakes happen.
How many Z-Wave devices can one network handle?
A classic mesh supports 232 nodes with a maximum of four routing hops between the controller and any device. In practice the hop limit bites first in long or multi-storey buildings. Z-Wave Long Range replaces the mesh with a star topology and raises the ceiling to roughly 4,000 nodes, but both the controller and each device must support it.
Can Z-Wave devices work with Matter, Apple Home, or Alexa?
Only through a hub that re-exports them. Z-Wave has no native Matter path and no Apple, Google, or Alexa radio support. A Home Assistant or SmartThings setup can present its Z-Wave devices to Matter ecosystems as bridged devices, which is how a Z-Wave lock ends up in Apple Home. Expect basic functions to carry over and everything else to stay in the hub.