Almost every guide to smart home protocols presents Zigbee, Matter, KNX, and WiFi as four options competing for the same slot, then gives you a table of ranges and frequencies.
The table is not the problem. The framing is. These four are not alternatives to each other, and the single most useful thing you can learn about smart home protocols is why.
The distinction that makes everything else make sense
There are two different jobs happening, and they get discussed as if they were one.
Some protocols are the radio. They determine how a signal physically gets from a sensor to a hub: what frequency, how far, how much battery it costs, whether devices relay for each other. Zigbee, Thread, WiFi, and Z-Wave are radios.
Some protocols are the language. They determine what a device says once the signal arrives: how it describes itself as a light, what "set brightness to 40%" looks like, how it is paired and secured. Matter is a language.
So "Zigbee vs Matter" is a category error. Matter runs over radios — WiFi, Ethernet, or Thread. A Matter light is usually a WiFi or Thread light that speaks a standard vocabulary. Zigbee, by contrast, is both a radio and its own older vocabulary bundled together.
And KNX is neither of these things, because it is mostly not wireless at all.
Once that clicks, the rest is straightforward.
The radios
Zigbee is a low-power 2.4 GHz mesh. Every mains-powered device relays for its neighbours, so coverage improves as you add devices. Battery sensors last months to years. It needs a coordinator — a hub — and it is the most common protocol in cheap sensors, which is exactly why it matters. Its weakness is that 2.4 GHz is crowded, sharing space with WiFi and Bluetooth, and older devices had genuine cross-vendor compatibility problems.
Thread is the newer low-power mesh, built on the same underlying radio as Zigbee but speaking IPv6, so devices are addressable like anything else on your network. There is no single coordinator to bottleneck; instead you need a border router to bridge Thread to your normal network. Thread is the radio Matter was designed to shine on. Worth knowing: since January 2026, new border routers must be certified to Thread 1.4, which was largely about making multi-vendor Thread networks behave when several ecosystems are present — historically a real source of pain.
WiFi needs no hub and carries lots of data, which makes it the right answer for cameras and anything streaming. It is also power-hungry, so it is the wrong answer for a door sensor running on a coin cell. Fill a house with WiFi devices and you will meet your router's client limit sooner than you expect.
Z-Wave runs on sub-GHz frequencies, which is genuinely useful: less congestion than 2.4 GHz and better wall penetration, at the cost of lower bandwidth. Certification is stricter, so cross-vendor behaviour tends to be more predictable.
Bluetooth LE is mostly for setup and proximity, not for running a house. 433 MHz is legacy, often one-way, and still worth supporting because plenty of older kit uses it.
Matter, and what it does and does not fix
Matter is the industry's attempt to stop every ecosystem inventing its own vocabulary. A Matter device should pair and work across ecosystems without a vendor bridge in the middle.
It has taken longer than the announcements implied. Matter reached 1.4 in late 2024 and has continued iterating since; ecosystems have adopted it at very different speeds, so it is entirely normal in 2026 to find two Matter devices whose supported feature sets do not quite line up. It is meaningfully better than it was, and it is not yet the universal solvent it was sold as.
The practical point when buying a hub: "supports Matter" is an incomplete claim. Matter runs over WiFi, Ethernet, and Thread. A hub that speaks Matter over WiFi but has no Thread radio cannot talk directly to a Thread-only Matter device. Both hubs will say "Matter" on the box. Ask which transports.
Curious whether Nexop fits your home?
Book a live demo — one of the founders runs it, not a salesperson — or join the waitlist and hear from us the day it ships.
KNX, the outlier
KNX is in a different conversation, and it is worth understanding even if you will never buy it.
It is a wired bus. A twisted-pair cable runs to every switch, sensor, and actuator, carrying both data and power. There are radio and IP variants, but wired is the heart of it. It is an international standard, and it has been in buildings for decades.
The architectural difference is that KNX is decentralised. Devices hold their own logic and talk to each other directly on the bus. There is no hub whose failure takes down the lights. A KNX installation from twenty years ago still works, which is a sentence you cannot say about much smart home equipment.
The costs are real: it has to be planned and wired during construction or a serious renovation, devices cost far more than their wireless equivalents, and it is programmed by trained installers using dedicated software rather than a phone app.
This is why KNX dominates European commercial buildings and premium residential, and is nearly absent from retrofits. If you have it, you have serious infrastructure and you are unlikely to rip it out. What KNX historically lacks is a good modern software layer on top — which is a gap, not a flaw in the protocol.
Working out what your house actually has
You probably do not need to choose. Most homes are already mixed.
Look at what you own. Battery sensors and cheap bulbs are usually Zigbee. Cameras, TVs, and speakers are WiFi. Anything sold in the last couple of years may be Matter, over WiFi or Thread. If your house was wired for automation during construction, especially in Europe, check for KNX.
Then check what needs a bridge today. If you have a Philips Hue bridge, an Aqara hub, and a SmartThings hub all plugged in, those are three Zigbee networks that could often be one.
Then ask what is missing. Usually it is not a protocol — it is that nothing is coordinating across them.
What this means when choosing a hub
Four questions, in order of how often they are answered badly:
Which radios are physically in the box? Software cannot conjure a radio. A hub without a Z-Wave chip will never speak Z-Wave, whatever a firmware update promises. Check whether protocols are built in or need a USB dongle — Home Assistant Green, for instance, needs an add-on dongle for Zigbee and Thread.
Which Matter transports? See above. WiFi-only Matter and Thread-capable Matter are different products.
Does it work if the vendor's cloud goes away? A hub that translates protocols locally keeps working. One that round-trips through a server does not.
Can one hub replace the bridges you already run? Consolidating three vendor bridges into one is usually a bigger practical win than gaining an extra protocol.
Where Nexop stands, including the gaps
Nexop natively supports Zigbee, KNX, Matter, and WiFi. That combination is deliberate: Zigbee because it is what most existing sensors actually use, WiFi because it is what most existing appliances use, Matter because it is where new devices are heading, and KNX because wired installations have excellent hardware and have been badly served by software.
The honest gaps: Z-Wave, Thread, infrared, and 433 MHz are not supported at launch, and our Matter support is over WiFi and Ethernet rather than Thread. If your home runs on Z-Wave, or is built around Thread devices, Homey Pro covers more radios than we do today and we would rather tell you that here than have you discover it after buying.
The bet we are making is not that we will win on radio count. It is that once devices are connected, the useful problem is no longer transport — it is that nothing is proposing automations instead of waiting for you to write them.
If you want to see that running on a real home, book a demo. If you are still working out whether a local hub is the right category at all, the FAQ covers the common objections.