Smart home protocols used to be a fairly simple topic. You picked Wi-Fi as the default and carried on.
Then the smart home started to grow. More lights, more sensors, a few controllers. Most of the time you didn’t even know what protocol they were using. Wi-Fi? Zigbee? Z-Wave? Bluetooth? RF? You just set up the hub they came with and put it next to all the other vendor hubs.
Before long, what started as a simple setup turned into a protocol nightmare, with devices all needing to talk to different apps, hubs, and services just to do basic things.
Smart homes stopped being a handful of gadgets and started becoming pockets of mini systems, each with their own apps, hubs, and rules.
That’s where a lot of frustration has crept in. Most of the time it comes down to devices and ecosystems that don’t talk to each other well, devices that only behave properly inside one app, and setups that feel harder to maintain every year rather than easier.
Matter exists because this approach eventually stopped making sense.
This article builds on Smart Home Protocols Explained. That one focuses on what the main protocols are and how they differ. This one looks forward, at where smart home connectivity is heading and why Matter, particularly when paired with Thread, is becoming the centre of gravity for new development.
This isn’t about declaring winners or telling you to rip out what already works. It’s about understanding the direction things are moving, so the choices you make now still make sense a few years down the line.
Why the industry is converging (finally) #
For a long time, smart homes grew by accident rather than design. You’d add a device because it looked useful, then another because it worked with the app you already had. Over time, that usually meant multiple apps, different setup methods, and devices that only really behaved when everything lined up just right.
As homes added more devices, this became harder to live with. Simple things like adding a new sensor or switching platforms started to feel riskier than they should. Something that worked fine on its own could stop behaving properly once it had to interact with other brands or systems.
At a certain point, that approach stopped making sense.
Matter exists to address that problem.
Rather than each brand inventing its own way of doing the basics, Matter defines a shared foundation for how devices are set up, identified, and controlled locally. The idea isn’t to remove choice or lock things down. It’s to make the everyday stuff predictable, so devices can work together without special tricks or workarounds.
That shared foundation is why so many major platforms support it. It makes it easier for devices to work across Apple, Google, Home Assistant, and others without you having to rebuild your setup each time you change direction.
It doesn’t solve every smart home problem, but it does signal a clear shift away from isolated ecosystems and towards something that’s easier to live with long term.
Matter in plain terms (what it is and what it isn’t) #
A helpful way to think about Matter is as a shared set of road rules, rather than a new type of vehicle.
Wi-Fi, Zigbee, and Thread are the ways data actually moves around your home. They handle things like range, speed, power use, and reliability. Matter sits above them and defines how devices identify themselves, what they can do, and how they respond when something asks them to act.
Without shared rules, every device needs special handling. A switch from one brand talks differently to a light from another. Each platform has to learn those differences and work around them. That’s how smart homes ended up with so many apps, bridges, and custom integrations.
Matter changes this by defining a common language for devices. A Matter light describes itself the same way regardless of who made it. A Matter sensor reports its state in a predictable way. Platforms don’t need to guess or translate nearly as much as they used to.
What Matter does not do is replace the underlying transport. It doesn’t magically improve range, battery life, or reliability. Those things still depend on whether a device uses Wi-Fi, Zigbee, or Thread underneath.
Once that distinction is clear, the rest of the Matter conversation becomes much easier to understand.
Thread’s role in the Matter ecosystem #
If Matter defines the common language, Thread is one of the transports that fits that language particularly well.
Thread is a low-power, wireless mesh protocol designed specifically for smart home devices. Like Zigbee, it’s built for reliability rather than speed, and it’s meant to keep working quietly in the background. Where Thread differs is that it’s IP-based, which means devices can be addressed directly using modern networking standards.
That IP foundation is why Thread pairs so naturally with Matter.
Because Matter devices are IP-addressable, they don’t need the same kind of protocol translation that older technologies rely on. Devices can talk to each other more directly, with fewer moving parts in between. This reduces complexity and makes it easier for different platforms to share the same devices.
Thread is not a replacement for Wi-Fi, and it isn’t trying to be. It’s just doing a different job.
That’s why Matter is often paired with Thread in practice, especially for devices that benefit from low power use and predictable behaviour.
Why Matter over Thread is leading (for now) #
When people talk about Matter becoming “the future”, what they usually mean in practice is Matter over Thread. Not because Thread is the only option, but because it aligns most closely with what Matter is trying to achieve.
Matter is designed around local control, predictable behaviour, and devices that can work across ecosystems without special handling. Thread supports those goals by being low power, mesh-based, and IP-native. Together, they remove a lot of the friction that has historically made smart homes feel fragile.
One of the biggest practical advantages is that Matter over Thread does not rely on vendor-specific gateways. Devices can join a Thread network and be shared across platforms without needing a separate hub for each brand. That reduces points of failure and makes multi-platform setups much easier to live with.
You can see this shift playing out in real products now. Vendors that previously relied on Zigbee-only ecosystems are starting to move new devices to Matter over Thread. IKEA is a good example. Rather than treating Matter as an add-on, newer releases are being designed around it from the start. That kind of change only happens when vendors believe the underlying direction is stable enough to build on.
There’s also a longer-term angle. Because Thread is built on modern networking standards, it fits more naturally with where platforms are already heading. It’s easier to extend, easier to support consistently, and easier to reason about as systems grow.
That doesn’t mean Matter over Thread is perfect. Feature sets are still evolving, and some advanced or vendor-specific capabilities can be limited compared to mature Zigbee integrations. But as a foundation, it currently strikes the best balance between simplicity, reliability, and flexibility.
That balance is why new development is increasingly centred around this combination, even if the rollout hasn’t always been smooth.
Matter over Wi-Fi, where it fits and where it doesn’t #
Matter doesn’t replace Wi-Fi, and it doesn’t change what Wi-Fi is good or bad at. As covered in Smart Home Protocols Explained, Wi-Fi has real disadvantages for low-powered devices. Matter doesn’t remove those limitations, because underneath it is still Wi-Fi doing the work.
Wi-Fi makes sense for devices that are mains powered, need higher bandwidth, or are expected to be online continuously. In those cases, using Matter over Wi-Fi can be a good thing. You get better local control and easier cross-platform support without forcing a device onto a protocol that doesn’t suit its job.
Where Wi-Fi continues to struggle is with large numbers of small, low-power devices that communicate frequently. Power usage, airtime contention, and overall reliability don’t magically improve just because a device supports Matter.
This is why smart homes are settling into two clear paths:
-
Battery-powered devices that talk often and need to be quietly reliable
→ Zigbee, Z-Wave, or Thread -
Devices that need bandwidth or are already permanently powered
→ Wi-Fi
Matter sits across both paths. It improves compatibility, but it doesn’t erase the underlying trade-offs.
Where Zigbee and Z-Wave fit in this future #
Zigbee and Z-Wave aren’t going away. They’re both mature, well-understood protocols that have proven themselves in real homes over many years. For a lot of people, myself included, they’re the reason their smart home works as reliably as it does today.
They were designed in a time when cross-platform standardisation wasn’t a priority.
Matter doesn’t run natively over Zigbee or Z-Wave. When these devices are exposed to Matter ecosystems, it’s done through a bridge. That translation works, but it can limit access to some device-specific features and adds another dependency into the system.
Because of this, Zigbee and Z-Wave are best seen as strong local protocols that will continue to serve existing setups well, especially where mature integrations and fine-grained control matter. They remain excellent at what they do, even if they aren’t the convergence point for future standards.
What you actually need to support Matter and Thread #
One of the reasons Matter has gained traction so quickly is that many homes already have part of what’s required. What you need depends mainly on which ecosystem you’re using and how much control you want over your setup.
If you’re using Apple Home or Google Home, the entry point is relatively simple. Recent Apple TVs, HomePods, and Google Nest hubs already act as Thread border routers. In these setups, Matter and Thread support is effectively built in.
More advanced platforms require a bit more intent.
With systems like Home Assistant, Homey, Hubitat, or SmartThings, Matter support is available, but Thread support needs to be provided explicitly. That usually means having a compatible Thread radio or border router available to the platform. Thread should be treated as its own network alongside any existing Zigbee setup, not combined with it for convenience.
Matter over Thread devices do not connect directly to your Wi-Fi or Ethernet network. Instead, they communicate over a Thread mesh. A Thread border router connects that mesh into your wider home network.
Because of this, the border router needs a solid foundation underneath it. Matter and Thread are IP-based, which means IPv6 support is required on the network the border router connects to. In many homes this capability already exists, but it’s often disabled or unused by default.
In more segmented networks, such as those using VLANs, device discovery relies on local discovery traffic like mDNS being able to cross the right boundaries. If this isn’t handled correctly, Matter and Thread setups can feel flaky or inconsistent, even when everything else looks fine.
Matter doesn’t require anything exotic, but it does assume modern networking basics are in place.
A quick “healthy smart home” sanity check #
In most homes, the foundations that tend to matter are fairly simple, and they’re usually the things everything else ends up relying on:
- A stable network foundation that supports IPv6
- Wi-Fi coverage that’s reliable where Wi-Fi devices are actually used
- A rough sense of which devices belong on Wi-Fi, and which are better suited to a low-power protocol
For beginner-friendly setups, things usually go more smoothly when:
- You’re using a supported ecosystem, such as Apple or Google, with built-in Thread support
- Devices are chosen based on what fits the job, not just brand recognition or price
In more advanced setups, reliability often comes down to:
- A primary platform that supports the radios you actually need
- Separate coordinators where that makes sense, rather than trying to force everything into one place
And if you’re using Zigbee, Z-Wave, or Thread:
- Mesh networks rely on enough mains-powered devices to stay healthy
- Coverage works best when it’s planned deliberately, not built up by accident
(This is a high-level snapshot, not a full assessment. I’ll be publishing a separate detailed checklist article later on.)
If some of this isn’t in place yet, it doesn’t mean your smart home is wrong or broken. It just highlights where friction tends to appear over time as systems grow and standards continue to evolve.
Closing: Direction, not urgency #
Smart home standards don’t change overnight, and they rarely change cleanly. What’s different this time is that the direction is clearer than it’s ever been.
Matter provides a shared language. Thread provides a transport that fits that language well. Wi-Fi, Zigbee, and Z-Wave continue to do what they’ve always done best.
In my own home, that means a mix. I’m running devices across Wi-Fi, Zigbee, and now Matter over Thread as well. Nothing has been ripped out to make room for something new. What already works is still doing its job.
Where this direction matters most is over time. As devices eventually need replacing, or when something genuinely new is added, I’m simply leaning towards Matter over Thread or Matter over Wi-Fi where it makes sense. Not because it’s urgent, but because it keeps the overall system simpler as it evolves.
That’s the real value here. Fewer workarounds later, not more changes now.
The takeaway #
Smart home protocols aren’t being replaced so much as re-aligned.
Matter reduces friction between ecosystems by providing a shared language. Thread fits that model well for low-power, always-on devices. Wi-Fi, Zigbee, and Z-Wave still have clear roles, and they’re not suddenly wrong choices.
You don’t need to rebuild a working smart home to follow this direction. But understanding where things are heading helps you make changes more deliberately, only when they’re actually needed.
The goal isn’t chasing standards. It’s ending up with a smart home that quietly keeps working.
Try this next #
- Revisit Smart Home Protocols Explained to reinforce how Wi-Fi, Zigbee, Z-Wave, and Thread differ
- Take stock of which devices in your home rely on Wi-Fi versus a low-power protocol
- Check whether your primary platform already supports Matter and Thread, even if you’re not using them yet
- Watch for the upcoming Healthy Smart Home Checklist article for a deeper, step-by-step look
