The boxes in the smart home aisle carry three logos that look like rivals: Zigbee, Thread and Matter. Only two of them compete. Zigbee and Thread are radio networks that move small messages between low-power devices. Matter is a language devices use to describe themselves and accept commands, and it runs on top of Thread, Wi-Fi or Ethernet. Once you separate "how the bits travel" from "what the bits mean", most buying decisions get easier.

Three layers, not three rivals

Think of a smart home device as having two jobs:

  1. Getting a message from A to B. This is the network: Wi-Fi, Ethernet, Zigbee or Thread.
  2. Agreeing on what the message means. "Turn on", "brightness 40%", "temperature 21.5 °C". This is the application layer: Zigbee's own device definitions, Matter, or Apple HomeKit.

Zigbee covers both jobs in one standard. Thread covers only the first. The Home Assistant documentation puts it plainly: Thread "by itself does not allow controlling devices: It is just a communication protocol", and a higher-level protocol such as Matter or HomeKit is needed on top. Matter covers only the second job and borrows the first from IP networks.

Zigbee: a complete, closed-off mesh

Zigbee is a low-power mesh network built on the IEEE 802.15.4 radio standard, typically in the 2.4 GHz band. Mains-powered devices such as bulbs and plugs act as routers and pass messages along; battery-powered sensors sleep most of the time and talk to a nearby router.

Two properties matter in practice:

  • It is not IP. A Zigbee device has no IP address. Your phone, router and Home Assistant cannot talk to it directly. Everything goes through a coordinator, the one device that starts and manages the network: a USB adapter, a vendor hub such as a Hue Bridge, or a smart speaker with a Zigbee radio.
  • The coordinator owns the network. Devices are paired to that one coordinator. Move to a different hub and you pair everything again.

Zigbee is not standing still. The Connectivity Standards Alliance (CSA) released Zigbee 4.0 on 18 November 2025. It stays backward compatible with Zigbee 3.0 and adds stronger security (dynamic link keys, a "device interview" before a device is let in, protection against replay attacks), standardized network-level retries and better polling for sleepy battery devices. It also adds Zigbee Direct, which lets a phone set up and control devices over Bluetooth LE without a hub, and "Trust Center Swap Out", which allows the main controller to be replaced without re-pairing every device. Alongside it the CSA launched Suzi, the brand for Zigbee in the sub-GHz bands (800 MHz in Europe, 900 MHz in North America) for longer range. Certification for Suzi products opened in September 2026. How quickly these features reach products you can buy is up to manufacturers, so treat them as something to look for, not something to expect.

Thread: an IP mesh that needs a border router

Thread uses the same 802.15.4 radio as Zigbee, so the hardware is often identical, but it carries IPv6. Every Thread device has a real IP address, and a Thread border router connects the Thread mesh to your Wi-Fi or Ethernet network. According to the Home Assistant docs, the border router only forwards packets and does not look at their contents or control devices.

What this changes for you:

  • No single hub owns the devices. A Thread network can have several border routers, from different brands, which adds coverage and removes a single point of failure.
  • You probably already own a border router. Home Assistant's list includes the HomePod mini, HomePod (2nd generation), recent Apple TV 4K models, the Nest Hub (2nd gen), Nest Hub Max, Nest Wifi and Nest Wifi Pro, and the Google TV Streamer. Home Assistant itself can become one with a Connect ZBT-1, ZBT-2 or Yellow running the OpenThread Border Router app.
  • IPv6 has to work. Home Assistant's troubleshooting section calls Thread an IPv6-only protocol. If IPv6 is missing anywhere between the border router and the controller (the host, a virtual machine, Docker, the router), devices may join the mesh and still be unreachable.

The main practical problem with Thread has been fragmentation. Each vendor tends to create its own Thread network, so a home with Apple, Google and Home Assistant gear can end up with three separate meshes that do not share devices. Thread 1.4, published in September 2024, makes credentials sharing mandatory for certified border routers: an existing border router can hand its network credentials to another ecosystem through a one-time passcode, so new border routers join the existing mesh instead of starting a new one. Older border routers will not gain this unless their makers update them.

Matter: one language, several networks

Matter is an application-layer standard that runs over IP. A Matter device can use Wi-Fi, Thread or Ethernet. During setup the phone usually reaches the device over Bluetooth LE, passes it the network details, and then the controller takes over. Matter 1.6, released on 17 June 2026, adds a way to do the whole setup over NFC, even before a device has mains power, which is aimed at in-wall switches and ceiling lights.

The feature most people buy Matter for is multi-admin. One device can belong to several ecosystems at once, for example Apple Home and Home Assistant, each with its own "fabric" (its own set of security credentials). The specification requires every certified device to support at least five fabrics. You add the device once in the first app, then use that app to open a sharing window that produces a new pairing code for the second.

Matter also defines bridges: a hub that exposes its non-Matter devices as Matter devices. Several Zigbee hubs, the Philips Hue Bridge among them, have been updated to do exactly that, which is how a Zigbee bulb behind a vendor hub can appear in a Matter controller.

Device coverage has grown in steps. Matter 1.5 (20 November 2025) added cameras and video doorbells using WebRTC streaming, plus closures such as garage door controllers, soil sensors and more energy management features. Matter 1.6 added "Joint Fabric", where several controllers share one network rather than each running its own. As with Zigbee 4.0, a new spec version does not mean your controller or device supports it yet; check both.

Same radio, same channels

Zigbee and Thread share the 2.4 GHz 802.15.4 channels 11-26, which overlap with 2.4 GHz Wi-Fi. Home Assistant's Thread documentation notes that channel 26 is the least likely to suffer Wi-Fi interference. If you run both a Zigbee and a Thread network, put them on different channels and keep both away from your busiest Wi-Fi channel.

Because the radio is the same, many USB adapters can run either Zigbee or Thread firmware. Home Assistant's own Connect ZBT-1, ZBT-2 and Yellow ship running Zigbee; switching to Thread is a firmware change. One adapter normally runs one network, so if you want both, plan for two adapters.

So which should you choose?

There is no single winner, but the choice follows from a few questions.

You already have a Zigbee network that works. Keep it. Zigbee 3.0 devices are not going away, Zigbee 4.0 is backward compatible, and an open coordinator (Zigbee2MQTT or ZHA in Home Assistant) gives you the same local control Matter promises. If you want those devices in Apple Home or Google Home, a hub that bridges to Matter covers it.

You are starting from scratch and want to use Apple Home, Google Home or Alexa, possibly more than one. Matter devices are the natural choice, because multi-admin lets each household member use the app they prefer. For battery sensors, locks and anything that should keep working when Wi-Fi is busy, prefer Matter over Thread. For plugs and other mains-powered devices, Matter over Wi-Fi is fine as long as your Wi-Fi is solid.

You care most about price and device selection for sensors. Zigbee still has the deepest catalogue of cheap battery sensors, buttons and switches. With a USB coordinator the network stays entirely local.

You want everything controlled locally from Home Assistant. All three work. Zigbee needs a coordinator, Thread needs at least one border router and working IPv6, and Matter needs the Matter server app.

A few habits help whichever way you go:

  • Check what a "Matter" logo actually means on the box. A Thread logo with "requires border router" means the device has no Wi-Fi at all.
  • Before buying a Thread device, check whether your existing border routers already form a network you can join, rather than creating another one.
  • Do not mix up a Zigbee device with a Matter bridge and a native Matter device. The first needs the hub to stay online; the second does not.