Zigbee, Z-Wave, Wi-Fi, Bluetooth or Matter? Explained simply
The short answer: you don’t have to settle on a single protocol – a good system uses several at once, each for the job it does best. Rule of thumb: battery-powered sensor → Zigbee or Z-Wave, in-wall switch and relay → Zigbee, Z-Wave or Wi-Fi, cameras and high data traffic → Wi-Fi or cable, buying a new device → check whether it supports Matter.
A protocol is the “language” smart devices use to talk to each other. It’s more than a technical detail: it determines how many years a battery lasts, how reliable the system is, and whether it works without the internet.
The main players in brief
Zigbee
A low-power radio protocol that builds its own mesh: most mains-powered (not battery-powered) devices pass the signal on to the others. The more smart plugs and switches you have, the better the coverage. The choice of devices is wide and prices are reasonable. The trade-off is that it runs on the 2.4 GHz band, which much of your Wi-Fi also uses – in a crowded environment this can cause interference, so the channels need to be chosen carefully.
Best for: sensors, smart bulbs and switches – where you need lots of devices and price matters.
Z-Wave
Also low-power and also a mesh, but in Europe it runs on 868 MHz – so it doesn’t clash with Wi-Fi. Its range through walls is typically better, and its certification is stricter, so devices from different manufacturers work together more predictably. Today’s devices are built on 700 and 800 series Z-Wave Plus chips, with S2 encryption and SmartStart pairing. The trade-off: the devices cost more and the choice is narrower.
Best for: in-wall modules and blind control – where reliability matters more than price.
Wi-Fi
The one you already know. High bandwidth and no separate hub needed – but every device adds load to your router, and battery-powered devices drain their batteries quickly. On top of that, most cheap Wi-Fi smart devices work through the manufacturer’s cloud: if the internet or the manufacturer’s server goes down, the device goes silent.
Best for: cameras, speakers, EV chargers – where there’s a lot of data traffic anyway and mains power is available.
Bluetooth
Almost everyone owns a Bluetooth device, so many people think of it first for the smart home too. It’s low-power (Bluetooth Low Energy), cheap and already built into your phone – that’s its big advantage. For a smart home, however, it’s not ideal: in practice it communicates point to point, its indoor range is typically 10–15 metres, and there’s nothing to relay the signal. A mesh variant (Bluetooth Mesh) does exist, but it’s rare in home devices. To control a Bluetooth device remotely or from an automation, you need a gateway nearby – without one, the device can only be reached when you’re standing close to it with your phone.
What it is excellent for is initial pairing and setup. Many devices – including a large share of Matter devices – receive their first settings from your phone over Bluetooth (for example, the Wi-Fi or Thread network details), because it makes configuration straightforward and quick. After that, they carry on working on their own dedicated network.
Best for: initial pairing and setup, and direct, close-range control (for example, opening a smart lock from your phone). We don’t recommend it as the backbone of a system.
Matter and Thread – what do they solve?
This is where most of the misunderstandings are, so we’ll look at it separately:
- Matter isn’t a radio, it’s a common language. It defines how a device describes itself and its functions so that hubs from different manufacturers can understand it – and a single device can be used in several ecosystems at once (multi-admin), for example in Apple Home and Google Home in parallel. It can run over Wi-Fi, over a cable and over Thread. It’s backed by the biggest players in the industry – including Apple, Google, Amazon and Samsung, as well as manufacturers such as IKEA and Philips Hue – so it has a good chance of becoming the common language of a huge number of smart home devices in the future.
- Matter over Wi-Fi: the device speaks Matter over your existing Wi-Fi network. For mains-powered devices (plugs, relays) this is a fully fledged solution. With battery-powered devices and large numbers of devices, however, it has limits: it uses more energy, and lots of Wi-Fi devices put a load on the network.
- Thread is the radio. A low-power, mesh-building radio layer – similar in principle to Zigbee, but IP-based, so each device is a full member of the network. Thread devices need a border router, which is already built into many smart speakers, media players and hubs – for example several Apple TV 4K models, the HomePod mini, the 2nd-generation Google Nest Hub and the Homey Pro hub.
What does this mean in practice? A Matter-certified device is more likely to keep working if you later switch hubs or ecosystems. That’s a real benefit. What’s worth knowing, though, is that Matter is still evolving: the range of devices and supported functions keeps growing, but in many areas it’s still incomplete today. And Matter isn’t a magic word: it doesn’t cover every function – more complex, manufacturer-specific features are often only available in the manufacturer’s own app. That’s why, for a new device, Matter support is a strong plus rather than the only thing to consider.
What about Tuya or eWeLink? Not protocols, but cloud platforms
Many people know the Tuya name (or its Smart Life app), or the eWeLink app used with Sonoff devices, and they’re often mentioned in the same breath as the protocols above. Yet they’re something quite different: they’re cloud platforms on which a huge number of low-cost smart devices – often sold under many different brand names – are built.
The difference is in the basics of how they work. Zigbee, Z-Wave and Thread devices are controlled by a local hub inside your home; the cloud is only an add-on, for example for remote access. With Tuya and eWeLink Wi-Fi devices it’s the other way round: the cloud itself is the basis of control. If the internet or the service goes down, the device stops working, and so does any automation built on it. Its long-term operation also depends on whoever runs the platform.
The situation is similar with many other Wi-Fi device families that rely on their own app – such as Meross, Govee or Broadlink – except for their models that are Matter/HomeKit-compatible or also allow local control.
So if it matters to you that your home keeps working without the internet, we don’t recommend cloud-based devices as the foundation of your system. If you already have devices like these, we’ll check during the site survey which ones can be kept: Tuya and Sonoff Zigbee devices, for example, can often – though not always – be added to a local Zigbee hub, and some Sonoff models can also be controlled over the local network.
Google Home, Amazon Alexa, Siri – not protocols either
Voice assistants are also often confused with protocols. Google Home, Amazon Alexa and Apple Siri are the control interface – an ecosystem with a voice assistant – not the language the devices speak. Underneath, the devices still communicate over Zigbee, Z-Wave, Thread or Wi-Fi (often with Matter compatibility), and the voice commands are typically processed by the cloud. We’ll also cover voice control in a separate article.
Comparison table
| Criterion | Zigbee | Z-Wave | Wi-Fi | Thread (Matter) | Bluetooth |
|---|---|---|---|---|---|
| Frequency | 2.4 GHz | 868 MHz (EU) | 2.4 / 5 GHz | 2.4 GHz | 2.4 GHz |
| Power consumption | low | low | high | low | low |
| Battery life of battery-powered devices | years | years | months | years | months to years |
| Builds a mesh network | yes | yes | no | yes | typically no |
| Susceptibility to interference | medium (shares the band with Wi-Fi) | low | – | medium | medium |
| Device choice | wide | medium | very wide | growing | wide |
| Price | affordable | higher | mixed | medium | affordable |
| Works without the internet | yes | yes | depends on the device, often not | yes | yes, but only at close range |
| Needs a hub | yes | yes | no | needs a border router | needs a gateway for remote access |
What really matters when you choose
1. Does control stay local? This is the most important question, and it isn’t actually about the protocol. If the automations run on a hub inside your home, your heating, lighting and scenes keep working during an internet outage. If they run in the manufacturer’s cloud, they don’t. We build for local operation.
2. Is the device battery-powered or mains-powered? For battery-powered devices, don’t choose Wi-Fi. The battery in a Wi-Fi door/window sensor typically lasts a few months – about a year at best – while in a Zigbee or Z-Wave sensor it lasts for years.
3. How dense is your mesh? Zigbee and Z-Wave build a mesh, but only mains-powered devices relay the signal. If all you have is battery-powered sensors, there’s nothing to strengthen the signal – in that case adding one or two smart plugs or relays improves coverage more than any antenna.
4. What are your walls made of? There’s a huge difference between reinforced concrete and plasterboard. We measure this during the site survey rather than guessing.
What if it’s a mix?
That’s the normal state of affairs – and it isn’t a problem. A multi-protocol hub running locally (for example the Homey Pro) handles Zigbee, Z-Wave, Wi-Fi and Matter/Thread devices all at once, and it also links them into shared automations: a Zigbee door/window sensor can switch off the Wi-Fi air conditioner, and a Z-Wave blind module can follow the time of day.
One thing is worth knowing in advance, though: day-to-day use can be brought together in one app, but not everything goes into it. The camera’s live view and recording management stay in their own system, with its own logs. This isn’t a limitation but a deliberate choice: that’s the right place for searching recordings and managing access rights. The overview screen shows that an event happened, with a link to it.
Frequently asked questions
Which is the best protocol?
There isn’t one. The ideal choice differs from task to task, and a good system uses several at once.
Zigbee or Z-Wave?
If you need lots of sensors at an affordable price, Zigbee. If reliability and range through walls matter more – for example with in-wall modules – Z-Wave. Often both work side by side in the same system.
So does Matter solve all compatibility problems?
No. It improves things a lot and is worth looking out for in new devices, but more complex, manufacturer-specific functions are often left out. Matter is a good foundation, but not a complete guarantee.
Do I need a separate hub?
For Zigbee and Z-Wave, yes; for Thread you need a border router to connect it to the rest of the network. Most hubs also act as border routers, so you don’t need two separate units – one device covering the functions you need is enough.
Do I have to throw away my existing Wi-Fi devices?
Usually not. Many of them can be brought into the system and kept in use (the cloud-dependent models only through the manufacturer’s cloud), but it’s worth expanding the system with a low-power protocol from here on.
I have Tuya, Smart Life or eWeLink devices. What about those?
These aren’t protocols but cloud platforms: their Wi-Fi devices are controlled via the cloud, so they typically stop working during an internet outage. We don’t recommend them as the foundation of a locally running system. We’ll review the ones you already have during the site survey – some of the Zigbee models can also be moved over to a local hub.
Does it work without the internet?
Zigbee, Z-Wave and Thread do, if they’re controlled by a local hub. Cloud-dependent Wi-Fi devices typically don’t. That’s why we ask at every site survey what needs to keep working during an internet outage.
What would work in your home?
That’s decided by your walls, the number of devices and the functions you expect – not by the name of the protocol. During the site survey we measure coverage throughout, then recommend a system that runs locally and can be expanded later.
Request a site survey · Details: Smart home design, installation and integration
Updated: September 2026. The Matter ecosystem changes quickly; we always check support for the specific device before purchase.





