A plain-English guide to Matter and Thread — what they are, how they work together, and why support still depends on the selected device and ecosystem.

Understanding Matter and Thread: the future of smart-home connectivity

Originally posted 2025-06-29. Refreshed 2026-04-26.

Smart homes are evolving — and Matter and Thread are part of that change. Together, they are designed to reduce smart-home fragmentation and make supported devices easier to connect across compatible ecosystems.

If you've ever bought a "smart" device and discovered it only works with one app and one ecosystem, Matter is intended to make that experience better where the device and platform support it.

What is Matter?

Matter is a unified, open-source standard developed by the Connectivity Standards Alliance (formerly the Zigbee Alliance), backed by Apple, Google, Amazon, Samsung, and most major device makers.

Goals of Matter

🔒 Local and secure — devices talk to each other without going through the cloud.
🌉 Cross-platform intent — supported devices can be shared between compatible ecosystems, depending on the device, controller and platform support.
🧩 Simple setup — pair a device by scanning a QR code, then share it with other supported ecosystems using Matter multi-admin where the device and platform support it.
🌎 Open ecosystem — vendors collaborate, not lock in.

Matter supports a growing list of device categories, but exact device classes and features still depend on the device firmware, controller and ecosystem support.

What is Thread?

Thread is a low-power wireless mesh protocol that complements Matter.

Think of Thread as the network and Matter as the language devices speak.

Why Thread matters

📡 Mesh networking — router-capable Thread devices can extend coverage; sleepy battery devices usually preserve power and do not route traffic.
🔋 Low power design — suitable for many battery-powered sensors and controls.
🌐 IPv6-based — devices use IP networking within the Thread mesh.
🛡️ Mesh design — router-capable devices can help the network adapt, but reliability still depends on design, placement and compatible hardware.

Thread devices need a Thread Border Router to bridge between the Thread mesh and your home network. Common border-router categories include:

Selected Apple HomePod and Apple TV models
Selected Google Nest hubs and routers
Selected Amazon Echo and eero devices
Selected Akubela panels or hubs
Home Assistant with suitable Thread border-router hardware

Matter + Thread in real life

Once set up, a Matter-over-Thread device can, where supported:

Work locally without the cloud.
Respond locally without an internet round-trip for supported control paths.
Be shared with multiple compatible ecosystems through Matter multi-admin where the device and platforms support it.

For Australian homes, this can reduce lock-in, but it does not remove the need to check device class, feature support, controller requirements and local availability before buying.

Matter-related device categories we check

Brand	Type
Akubela	Selected panels, hubs and sensors
Apple	Selected hubs and border routers
Google Nest	Selected hubs and border routers
Amazon Echo / eero	Selected border routers
Nanoleaf	Selected lighting products
Eve	Selected sensors and smart plugs
Aqara	Selected bridges, sensors and switches
TP-Link / Kasa	Plugs, switches on selected models
Philips Hue	Selected lighting through compatible bridge support

Matter & Thread in Home Assistant

Home Assistant can support Matter and Thread through compatible software and hardware combinations, such as:

Home Assistant Green or Yellow appliances, depending on add-on hardware
Home Assistant Connect ZBT-1 / SkyConnect-class hardware, depending on configuration
The Matter integration/add-on plus a suitable Thread Border Router for Thread devices

This means a Home Assistant build can be designed around Matter, Thread, Zigbee and Z-Wave, but the radio hardware and integration path still need to match the protocols you want to run.

What this means for your project

Matter-over-Thread is worth considering for supported device categories because it can improve ecosystem flexibility. We check current support on the selected hub, controller and device model before specifying it.

But: not every device needs to be Matter. Older Zigbee devices can still be useful. Wi-Fi devices can still be appropriate. Matter is a useful option for selected new purchases, not a reason to rip out anything that already works.

Your cart

Matter & Thread Explained