The smart home has suffered from fragmentation since it began. Devices from different manufacturers used different protocols, worked with different platforms, and frequently couldn't be controlled from one place.
Industry standards were developed to address this. The result, so far, is that the situation is more complicated in the short term.
What the pieces are
The terminology confuses people because the components operate at different layers.
Thread is a networking protocol — a low-power mesh network for devices to communicate. It handles how data moves, not what the data means.
Mesh networking means devices relay for each other, extending range without a central hub reaching everything. Mains-powered devices typically act as routers; battery devices don't, to preserve power.
Matter is an application layer standard — it defines what messages mean, so a light from one manufacturer can be controlled by a system from another.
Matter runs over several networks including Thread, Wi-Fi and Ethernet.
Border routers connect a Thread network to your main network. Many smart speakers and hubs include this function.
What was promised
Devices from any manufacturer working with any platform. Local control without cloud dependency. Simple setup. An end to checking compatibility before buying.
What actually happened
Partial delivery, with specific friction points.
Incomplete device type coverage. The standard defines device types and capabilities, and coverage has expanded over successive versions. Categories not yet covered can't be represented, which means manufacturers use proprietary extensions for anything distinctive.
The practical effect: a device may work for basic functions through the standard while its distinctive features require the manufacturer's own app.
Varying implementation quality. Certification indicates a device meets requirements, and implementations differ in reliability and in which optional features they support.
Setup complications. The commissioning process involves scanning a code and can fail for reasons that are difficult to diagnose — network configuration, IPv6 requirements, border router issues.
Multi-admin, allowing a device to be controlled by several platforms simultaneously, works and adds complexity to setup.
Border router requirements. Thread devices need one. Which one you have affects behaviour, and having several from different vendors has historically produced complications, though interoperability between them has improved.
Existing devices. Products predating the standard mostly don't support it. Bridges exist for some ecosystems and coverage is partial.
Why it's harder than it looks
Some sympathy is warranted for the difficulty.
The standard must accommodate devices from hundreds of manufacturers, across many categories, at many price points, with different capabilities.
Defining a common representation for a light is straightforward. Defining one for every appliance with distinctive features is not, and any standard general enough to cover everything loses the specificity that makes devices distinctive.
There's also a commercial tension. Manufacturers benefit from ecosystem lock-in, and a standard that makes devices fully interchangeable removes a competitive advantage. Support that is technically compliant while steering users towards a proprietary app is a predictable response.
Where it works well
For basic device categories — lights, plugs, switches, sensors, locks — support is reasonably mature and the experience is genuinely better than before.
Local control is a real benefit, addressing the cloud dependency problem for supported devices.
And Thread's mesh networking is a genuine improvement over Wi-Fi for battery devices, both for power consumption and for not loading the main network with dozens of devices.
Practical guidance
Check specific device support, not the logo. Whether a particular device works with your particular platform, for the functions you want, is a question the certification doesn't fully answer.
Prefer devices that work without the manufacturer's app. If setup or core function requires it, the dependency remains.
Establish a good border router. The foundation for Thread devices, and problems here manifest as unexplained unreliability.
Consider a local automation platform. Open-source home automation software supports the standard alongside many proprietary protocols, which handles both new and legacy devices and keeps control local.
Buy incrementally. Test one device before committing to a house full, since compatibility surprises are common.
Where it's going
Successive versions have expanded device type coverage and addressed setup friction, and the trajectory is towards the situation the standard promised.
The realistic expectation is continued gradual improvement rather than a moment when everything works. Standards adoption in consumer electronics has historically taken years, and this is following the pattern.
Which means it's worth adopting for new purchases and not worth replacing working equipment for.
What to do with existing devices
Since most people have accumulated a mixture rather than starting fresh.
Bridges exist for several older ecosystems, exposing existing devices to newer platforms. Coverage varies and functionality is frequently partial — basic control works, advanced features do not.
A local automation platform handles this better than any single manufacturer's hub, because it can speak to multiple protocols at once and does not require everything to conform to one standard.
The practical approach for most households: keep what works, adopt the standard for new purchases, and accept a transitional period of running two systems. Replacing functioning equipment to achieve tidiness is rarely worth the cost.