The Zigbee vs Wi-Fi smart home decision, with Z-Wave as the third contender, shapes battery life, reliability and how much you spend on hubs. This comparison explains how each radio behaves in a real house, where each one fits, and exactly how its devices reach an MQTT broker, so you can mix them on one data backbone instead of being locked into a single ecosystem.
The Three Radios in One Paragraph Each
Zigbee is a low-power mesh protocol based on IEEE 802.15.4 at 2.4 GHz. Mains-powered devices such as plugs and bulbs act as routers and extend the mesh; battery devices such as door sensors sleep most of the time and last a long time on a coin cell. A USB coordinator on a computer or hub forms the network.
Z-Wave is also a low-power mesh, but it runs in the sub-GHz band (frequencies differ by region, around 868 MHz in Europe and 908 MHz in North America). Lower frequency means better wall penetration and no competition with Wi-Fi. Devices must be certified, which keeps interoperability high but prices higher. Z-Wave Long Range adds a star topology for devices far from the controller.
Wi-Fi devices join your existing network directly. No hub is needed, bandwidth is plentiful, and every device can speak MQTT itself. The cost is power consumption, which makes Wi-Fi a poor fit for small battery sensors, and load on your access points as the device count grows.
Thread, the low-power IPv6 mesh used by Matter, is a fourth option; we cover it in Matter vs MQTT.
Zigbee vs Wi-Fi Smart Home Comparison Table
| Aspect | Zigbee | Z-Wave | Wi-Fi |
|---|---|---|---|
| Frequency | 2.4 GHz | Sub-GHz (regional) | 2.4 GHz and 5 GHz |
| Topology | Mesh, mains devices route | Mesh, mains devices route; Long Range star | Star around access points |
| Battery sensors | Excellent | Excellent | Poor without deep sleep tricks |
| Hub or coordinator | Required (USB coordinator) | Required (USB controller) | Not required |
| Interference with Wi-Fi | Possible, choose channels carefully | None | Shares the band with everything else |
| Device cost | Low | Higher | Low to medium |
| Interoperability | Good with Zigbee2MQTT, varies by vendor | High, certification required | Depends on firmware |
| Path to MQTT | Zigbee2MQTT | Z-Wave JS UI | Native (Tasmota, ESPHome, Shelly, DIY) |
| Local control without cloud | Yes | Yes | Yes with open firmware, often not with vendor firmware |
How Zigbee Reaches MQTT: Zigbee2MQTT
Zigbee2MQTT runs next to a USB coordinator and translates every Zigbee device into MQTT topics. A door sensor named hallway/front-door publishes JSON to zigbee2mqtt/hallway/front-door, and you control a bulb by publishing to zigbee2mqtt/kitchen/ceiling-light/set. It supports thousands of device models from many vendors, which is why Zigbee has become the favourite of MQTT-minded homes.
Pointing Zigbee2MQTT at a broker is a few lines in configuration.yaml. For a quick test with the public broker:
mqtt:
base_topic: connectmq/demo/z4r8s2/zigbee2mqtt
server: mqtt://broker.connectmq.com:1883
client_id: z2m-z4r8s2
serial:
port: /dev/ttyUSB0
For your real home, use TLS and the credentials generated for your private broker:
mqtt:
base_topic: zigbee2mqtt
server: mqtts://broker.connectmq.com:8883
user: YOUR_USERNAME
password: YOUR_PASSWORD
client_id: YOUR_CLIENT_ID
serial:
port: /dev/ttyUSB0
Our Zigbee2MQTT setup guide covers coordinator choice and pairing, and Zigbee2MQTT with a cloud broker explains the remote access advantages.
Zigbee tips
- Keep the coordinator on a USB extension cable, away from the computer's USB 3 ports and Wi-Fi router, which cause interference.
- Choose a Zigbee channel that does not overlap your busiest Wi-Fi channel.
- Add mains-powered routers (plugs, bulbs that stay powered) early so battery devices have strong parents.
How Z-Wave Reaches MQTT: Z-Wave JS UI
Z-Wave JS UI (formerly Zwavejs2Mqtt) drives a USB Z-Wave controller and includes a built-in MQTT gateway. In its settings you enable MQTT, enter the broker host, port, credentials and a topic prefix, and choose how topics are named. With named topics, a dimmer in the hallway publishes its level under a path such as zwave/hallway/dimmer/38/0/currentValue, and you write to the matching targetValue/set topic.
Typical MQTT settings in the Z-Wave JS UI web interface:
Name: zwave-gateway
Host url: mqtts://broker.connectmq.com
Port: 8883
Auth: enabled, YOUR_USERNAME / YOUR_PASSWORD
Client ID: YOUR_CLIENT_ID
Prefix: zwave
Gateway type: Named topics
Payload type: JSON Time-Value
Retain: enabled
Many users run Z-Wave JS UI with the Home Assistant WebSocket integration and MQTT at the same time, using MQTT for everything outside Home Assistant. The Z-Wave JS UI MQTT guide walks through both modes.
How Wi-Fi Reaches MQTT: Natively
Wi-Fi devices can connect straight to the broker. Open firmware makes this easy:
- Tasmota on plugs and relays: set the host and topic in the console.
- ESPHome with its
mqtt:component instead of, or alongside, the native API. - Shelly devices have a built-in MQTT option.
- DIY ESP32 sensors publish with a few lines of code; see our ESP32 MQTT tutorial.
Tasmota configuration from its console, using the public broker for a first test:
Backlog MqttHost broker.connectmq.com; MqttPort 1883; MqttClient plug-z4r8s2; Topic plug1; FullTopic connectmq/demo/z4r8s2/%topic%/%prefix%/
Standard Tasmota builds do not include TLS; use a TLS-enabled build when connecting to port 8883. The Tasmota MQTT guide covers topics and commands in detail.
The downside of Wi-Fi at scale is that every device holds its own connection to the broker. Fifty Wi-Fi plugs mean fifty connections, while fifty Zigbee devices behind Zigbee2MQTT use one. Keep that in mind when choosing a broker plan: the free Serverless plan on ConnectMQ allows up to 25 connections, which is plenty for a bridge-heavy home but can be tight for an all-Wi-Fi one.
Choosing per Device Type
There is no single winner. Most good setups mix radios by device role:
| Device | Recommended radio | Reason |
|---|---|---|
| Door and window contacts | Zigbee or Z-Wave | Years on a coin cell, tiny form factor |
| Motion and temperature sensors | Zigbee | Low power, cheap, huge selection |
| Smart plugs and relays | Zigbee or Wi-Fi | Mains-powered; Zigbee plugs strengthen the mesh |
| Door locks | Z-Wave or Zigbee | Low power, mature security profiles |
| Energy monitors and heat pumps | Wi-Fi | More data, mains power, often native MQTT |
| Cameras | Wi-Fi or Ethernet | Bandwidth |
| Outbuildings and thick walls | Z-Wave | Sub-GHz penetrates better |
A Common Topic Layer on Top
Whatever the radio, everything ends up as MQTT topics, which is the real benefit of this approach. Give Zigbee and Z-Wave devices friendly names that follow your room/device scheme, keep DIY Wi-Fi devices under your own root, and your automations can treat all of them the same. The smart home MQTT topic structure guide shows a layout that works across bridges.
Picking a Broker for a Mixed-Radio Home
Zigbee2MQTT, Z-Wave JS UI and Wi-Fi devices all need a broker that is always on. Running Mosquitto on the same small computer works until that computer is the single point of failure for the whole house, or you want secure access from your phone without opening ports. A managed MQTT broker such as ConnectMQ gives every bridge the same TLS endpoint inside or outside the home. If you want to read about hosted options more broadly, see our cloud MQTT broker guide, and for more projects browse the IoT automation guide.
Get Started with ConnectMQ
Create a free Serverless broker at app.connectmq.com, no credit card required, paste the generated credentials into Zigbee2MQTT, Z-Wave JS UI or your Wi-Fi devices, and watch all three radios land in one topic tree in the ConnectMQ live topic explorer.
Frequently Asked Questions
Is Zigbee or Wi-Fi better for a smart home?
Zigbee is better for battery sensors and large numbers of small devices because of its low power and mesh. Wi-Fi is better for devices that need bandwidth or have mains power and native MQTT support.
Is Z-Wave better than Zigbee?
Z-Wave has better wall penetration and stricter certification, while Zigbee is cheaper with a larger device selection. Both are excellent for low-power sensors, and both bridge cleanly to MQTT.
Do Zigbee and Wi-Fi interfere with each other?
They share the 2.4 GHz band, so they can. Pick a Zigbee channel away from your main Wi-Fi channel and keep the coordinator away from the router.
How many MQTT connections does a Zigbee network use?
One. Zigbee2MQTT holds a single broker connection and publishes for every device in the mesh, which keeps connection counts low.
