Every few weeks someone asks me some version of the same question: "Should I go Matter, Thread or Zigbee?" Usually they've just bought a couple of smart bulbs, noticed three different logos on the box, and assumed they need to pick a side.
I get why. I asked the same thing when I started building out my own setup. But after a couple of years of running Home Assistant at home with a mix of Wi-Fi, Zigbee and now a few Thread devices, I've landed on a fairly simple answer: you're not choosing between them. They do different jobs.
Let me explain how I think about it.
The mental model that made it click for me
I stopped being confused the day I separated three things in my head: the radio, the network, and the language.
Zigbee is a full mesh stack sitting on the IEEE 802.15.4 radio at 2.4 GHz. It's been around for two decades, runs its own proprietary networking, and needs a coordinator — a hub, or in my case a USB dongle plugged into the Home Assistant box. What Zigbee has that nothing else does is sheer breadth. Thousands of certified devices, including the weird stuff — irrigation valves, garage relays, cheap ₹500 contact sensors — that the newer standards still haven't caught up on.
Thread uses the same 802.15.4 radio but does networking differently: native IPv6. Devices form an IP mesh and reach the rest of your LAN through a border router instead of a proprietary hub. A lot of smart speakers and hubs sold today have one built in. The part I like most is that it's all local — pull the internet cable and Thread devices keep talking to each other.
Matter is the one people misunderstand the most. It's not a radio. It's not a mesh. It's an application-layer standard — a shared dictionary for what "lock the door" or "dim to 40%" actually means, so a device from brand A can be driven by brand B's app. Matter runs natively over Thread, Wi-Fi and Ethernet. Zigbee is not a native Matter transport. Zigbee devices only show up in Matter through a bridge that translates between the two.
Once you see it this way, the "which one" question mostly dissolves.
What this looks like in my house
Here's roughly how it plays out in a real setup:
- My Zigbee sensors talk to the Zigbee coordinator on the HA box. Home Assistant can expose those as a Matter bridge, so they become visible to any Matter controller I want.
- A Thread bulb joins the same Matter fabric directly through a border router. No extra hub.
- Both end up under one controller, and I can write an automation where a Zigbee door sensor turns on a Thread bulb without thinking about which radio is doing what.
Two or three years ago that cross-protocol automation meant glue code and a lot of patience. Anyone who's been on the Home Assistant forums for a while will remember. In 2027 it's close to the default experience.
What's changed recently that's worth knowing
A few things moved through 2026 that actually affect buying decisions:
- Zigbee 4.0 added a sub-GHz mode (branded "Suzi") — 800 MHz in Europe, 900 MHz in North America. Lower frequency means better range and wall penetration. Not a huge deal in a city flat, but for anyone with a bungalow, farmhouse or outbuilding, it matters.
- Thread 1.4 (originally 2024) became the only certification path for new border routers from January 2026. If you've got an older border router, expect it to get left behind.
- Matter 1.5 brought cameras and energy management into the spec. Matter 1.6, released June 2026, was less about new device types and more about faster onboarding and playing nicer across ecosystems. Adoption is patchy though — some platforms are still months behind on the current spec.
So what would I actually buy?
Starting from zero? Go Matter over Thread. You get cross-brand interoperability plus a low-power local mesh, and you're aligned with where everything is heading. One caveat: check that the specific device type you need exists as a native Matter/Thread product. Some categories still don't.
Already running Zigbee? Keep it. This is the advice I give most often. A working Zigbee network loses almost nothing by staying put and bridging into Matter. Tearing it out to "upgrade" is money spent for no functional gain, and Zigbee still covers device types Matter hasn't reached.
Big property? Look at Zigbee 4.0 sub-GHz for the range. Usual caveats about placement and interference apply.
Quick reference
| Matter | Thread | Zigbee | |
|---|---|---|---|
| Role | Application-layer interoperability | Low-power IPv6 mesh | Low-power proprietary mesh |
| Radio | Thread / Wi-Fi / Ethernet | IEEE 802.15.4 | IEEE 802.15.4 (2.4 GHz, now sub-GHz too) |
| Needs | A Matter controller | A Thread border router | A Zigbee coordinator / hub |
| Strength | Works across brands | Local IP, no proprietary hub | Massive device catalogue |
| Sweet spot | Multi-brand control | Sensors, locks, battery devices | Existing setups, niche devices |
Two mistakes I keep seeing
- "Matter replaces Zigbee." It doesn't. Zigbee gets into Matter through a bridge, never natively. Different layers.
- "It has the Matter logo, so it'll just work." Certification means the device speaks the standard. It does not mean every feature works the same on every platform. Controller support and firmware still decide what you actually get. I've been bitten by this.
Where I think this is going
Nobody's going to "win". The more interesting thing is that the connectivity layer is slowly disappearing. As bridges, border routers and Matter itself keep maturing, the best smart home will be the one where you never have to think about which radio is carrying the signal — you just add the device and it works.
That's the setup I'm building towards. If you're starting now, you'll get there faster than I did.