← All stories

The rise of Thread and Matter: a more open smart home

Thread and Matter are making a more connected smart home possible. Here is what each does, why recent changes matter, and where good engineering still counts.

Photo by Debby Hudson / Unsplash

A smart home should be able to grow one useful device at a time. Adding a light, sensor or switch should not force you to rethink the whole system. Thread and Matter are helping move that idea closer to everyday reality.

Two standards, different jobs

Thread is a low-power, IPv6-based mesh network. It suits small connected devices, including battery-powered sensors. A Thread Border Router connects that mesh to the rest of your home network; the role can be built into a smart speaker or another existing device.

Matter defines how devices describe their capabilities and respond to commands across compatible platforms. It can run over Thread, Wi-Fi or Ethernet. A Matter device therefore does not necessarily use Thread, and a Thread device does not necessarily support Matter.

Why the momentum matters

The appeal is greater choice: devices from different manufacturers can participate in a shared system, with local communication at its core. For a product developer, that creates room to focus on the device’s usefulness while building on common networking and control standards.

The standards are also addressing practical friction. Thread 1.4 introduced standardized credential sharing to help compatible Border Routers join an existing network, alongside better diagnostics. These are useful foundations for homes that accumulate devices from several brands.

Matter 1.6, announced in June 2026, added NFC-based commissioning and Joint Fabric, a way for participating controllers to administer one shared Matter network. Both target familiar frustrations: getting devices connected and managing them across ecosystems.

Progress still needs good engineering

A specification release does not instantly update the devices in your home. Support depends on the product, firmware and platform. Matter over Thread also needs a suitable Border Router, and a local protocol alone cannot guarantee that every product feature works without the cloud.

Our view: the most promising part of this shift is the chance to make connected products easier to live with. That still takes careful work on radio coverage, power consumption, recovery after outages and software updates. Shared standards provide the foundation; thoughtful engineering turns them into a dependable experience.