Smart Home Interoperability Is Better Than It Was and Still Not What Buyers Were Promised

Matter arrived with a clear promise: one application-layer standard, backed by Apple, Google, Amazon and Samsung, so that a smart home device would work with any ecosystem the buyer already owned. Measured against the situation it replaced — a market of incompatible hubs, proprietary radios, and cloud accounts that stopped working when a vendor pivoted — it delivered on the core of that. Pairing across ecosystems generally works. A Matter-certified plug, bulb, or sensor bought without checking the box for ecosystem compatibility will, in the ordinary case, join whichever platform the buyer uses. The gap that persists is between "supported" and "fully functional," and it is structural rather than a bug. Matter standardizes device types and their common capabilities; anything a manufacturer builds beyond that shared baseline has no standard representation. So a robot vacuum exposes start, stop, and status through Matter while its mapping, room selection, and cleaning modes remain in the vendor app. A premium thermostat exposes temperature setpoints while its scheduling logic does not travel. The buyer's experience is a device that connects immediately and then turns out to need the manufacturer's app anyway for the features that justified the price difference over the cheap model. Thread, the low-power mesh networking layer many Matter devices use, has its own version of the same pattern. The mesh works, and battery-powered sensors on it behave far better than the Wi-Fi devices they replaced. But Thread requires border routers, those border routers are built into ecosystem hardware — smart speakers, hubs, streaming boxes — and a home that accumulates border routers from different vendors can end up with multiple Thread networks that do not merge. The standards work to make that seamless has progressed, but the practical advice given to buyers is still ecosystem-shaped: pick one vendor's border routers, which is precisely the lock-in the standard was meant to dissolve. What has actually improved for buyers is the failure mode rather than the feature ceiling. A Matter device that loses cloud support does not become a brick, because local control does not depend on the manufacturer's servers continuing to exist — a meaningful change in a category with a long history of hardware disabled by a discontinued service. For a buyer evaluating a smart home purchase in 2026, the realistic expectation is basic functions that work everywhere and survive the vendor, advanced functions that stay in the vendor's app, and a strong reason to standardize on a single ecosystem for anything more complex than switching things on and off.