Matter, Two Years On: Did the One-Standard Promise Arrive?

Matter launched in October 2022 with the backing of Apple, Google, Amazon and the Connectivity Standards Alliance, and the pitch was the biggest one the smart-home industry has ever made in unison: buy a Matter-certified device, and it works with whichever ecosystem you already own — HomeKit, Google Home, Alexa, SmartThings — without checking compatibility lists first, and without a vendor’s cloud outage taking your lights with it. Two years on, with well over a thousand certified devices on the market and every major platform shipping Matter support, the standard has genuinely arrived in the sense that it exists and works. Whether it arrived as the thing that was promised is a more complicated answer, and the gap between the two is exactly the kind of promise-vs-reality read this desk exists for.

What Matter actually is, briefly

Matter is an application-layer protocol, not a radio — it can run over Wi-Fi, Ethernet or Thread, with Thread being the low-power mesh radio most relevant to battery sensors and small devices. Devices are provisioned once (via a QR code and Bluetooth Low Energy) and then can be shared across multiple “fabrics” simultaneously, meaning a single Matter light bulb can genuinely be controlled from Apple Home and Google Home and Home Assistant at once, without picking one as the sole owner. That multi-admin design is the standard’s single most useful technical decision, and it’s the part that’s held up best in practice.

Where the promise landed

The core interoperability claim is real for devices built as Matter-native from the start. Nanoleaf’s Matter-certified light panels, Eve’s Thread-based sensors, and Aqara’s newer hub-and-sensor combinations pair to Apple Home, Google Home and Home Assistant with the same QR-code flow each time, and multi-admin genuinely works — control a Nanoleaf panel from an iPhone and an Android tablet simultaneously with no bridging app in between. Home Assistant’s own Matter server integration, covered from the automation side in the Zigbee vs Wi-Fi comparison, has matured from an early rough edge to a genuinely reliable controller, arguably the most complete open-source Matter implementation available to a home user.

Local control, the second pillar of the pitch, is also real where devices are Thread-native. A Thread-based sensor talks to a Thread border router on the local mesh with no cloud round trip required for basic state changes, which is the same local-first argument made in the cloud-free smart plug guide — Matter simply formalises it as a certification requirement rather than leaving it to individual vendors’ goodwill.

Where the promise hasn’t landed

The most common gap in the wild is “Matter-enabled” rather than “Matter-native.” A large share of devices carrying the Matter logo on a shelf today are existing Wi-Fi products with a Matter bridge added in firmware — the underlying device still phones home to the manufacturer’s cloud for its own app’s features, with Matter support layered on top purely for the multi-platform pairing story. That’s not dishonest exactly, since the Matter commissioning genuinely works, but it means the local-control and cloud-independence half of the pitch doesn’t apply to that device even though the box says Matter. Distinguishing “Matter-over-Thread, locally controlled” from “Matter-over-Wi-Fi, cloud-backed, Matter-bridged” requires reading past the logo to the actual radio spec, which most retail listings don’t make easy.

Certification fragmentation is the second real gap. Matter 1.0 shipped without support for several device categories buyers actually wanted — robot vacuums, thermostats with advanced scheduling, and security cameras were all absent or minimally supported at launch, arriving only in later 1.1-1.4 spec revisions through 2023 and 2024. A buyer shopping in 2022 expecting Matter to cover their whole smart-home wishlist immediately hit categories the spec hadn’t reached yet, and some of those categories — full-featured robot vacuum control being the clearest example — are still thinner in practice than the marketing implied two years in.

Thread border router availability was the third friction point, though it’s the one that’s improved the most. Early on, a Thread network needed a dedicated border router — an Apple TV, HomePod mini, Google Nest Hub, or a standalone unit like an Eero with Thread built in — and households without one of those already in the house found the “just works” pitch required an unplanned extra purchase. That’s now a smaller problem: most current-generation smart speakers and streaming boxes from Apple, Google and Amazon include a Thread radio by default, quietly solving the bootstrapping problem for anyone buying normal replacement electronics rather than committing to a dedicated router purchase — the specifics of which routers are worth buying versus which come free are covered in the Thread border router buying guide.

Multi-border-router networks are the detail that made Thread’s reliability story better than early sceptics expected. Because any certified border router on a network can extend the same Thread mesh, a house with an Apple TV in the living room and a HomePod mini in the bedroom automatically gets two mesh extension points cooperating rather than competing, and battery sensors route through whichever is closer without any manual configuration. That self-healing mesh behaviour is inherited from Thread’s underlying 802.15.4 heritage — the same radio family Zigbee uses — rather than being a novel Matter invention, but Matter’s certification requirements are what pushed manufacturers to actually ship the border-router radio in mainstream consumer electronics rather than leaving it a niche feature.

The materials and firmware honesty check

Because Matter is a software-layer certification rather than a hardware spec, the “materials eye” for this piece isn’t a teardown of one device — it’s checking whether certified products’ underlying radios match what the certification implies. The Connectivity Standards Alliance’s public certification database lists each device’s actual transport (Wi-Fi, Thread, or both) alongside its Matter version support, and it’s a genuinely useful five-minute check before buying anything marketed primarily on the Matter logo: a device certified against Matter 1.0 with Wi-Fi-only transport is a fundamentally different local-control proposition from a Matter 1.3 device over Thread, even though both boxes may carry an identical black-and-white Matter sticker.

The case against rushing to replace working kit

None of the above is an argument for ripping out a working Zigbee or proprietary Wi-Fi setup to chase Matter certification for its own sake. A Hue bulb on Zigbee with a Hue Bridge already gets multi-platform control through each ecosystem’s own bridge integration, and Philips (Signify) has been steadily adding native Matter support to existing hubs via firmware rather than requiring new hardware — meaning a lot of the promised benefit arrives as a free update to kit already installed, not a reason to buy again. The households genuinely well served by an early Matter purchase are the ones starting from nothing, where picking Matter-certified from day one avoids locking into a single app ecosystem later. For an existing setup that already works, the honest read is: check whether the vendor is adding Matter via firmware before spending money replacing hardware that isn’t broken.

The standard’s governance is also worth a clear-eyed note, since “backed by every major platform” cuts both ways. The same size and diversity of membership that gives Matter its interoperability claim also makes the spec move slower than a single-vendor standard would — the multi-year gap before robot vacuums and thermostats got proper category support is a direct consequence of needing agreement across competing companies with their own product roadmaps, not a technical failure so much as the predictable cost of building a standard by committee rather than by fiat. That’s a reasonable trade for the interoperability gained, but it means expecting Matter to move at a single company’s product-release pace is the wrong expectation to bring to it.

Real-world reliability, not just the pairing demo

The pairing flow is the part every review demos, but day-to-day reliability is the part that actually matters after week one. Community reports across Home Assistant’s forums and Reddit’s smart-home communities through 2024 describe a genuinely uneven picture: some Matter devices — particularly Thread-native sensors from Eve and Aqara — report as rock-solid, with uptime and responsiveness matching or beating their Zigbee predecessors. Others, especially early Matter-over-Wi-Fi bridge implementations from smaller manufacturers rushed to market for the certification badge, show intermittent dropped commands and slower state reporting than the same device’s original proprietary app offered — a regression that undercuts the entire pitch for anyone who experiences it. The pattern that emerges is subtler than “Matter is unreliable”: certification alone fails to guarantee implementation quality, and a manufacturer’s Matter firmware is only as good as the engineering effort actually put behind it, same as any other software layer.

Where things stand for a new buyer today

For someone building a smart home from scratch in 2026, Matter is worth treating as the default assumption rather than a nice-to-have — buying Matter-certified where a genuine choice exists costs nothing extra in most categories now that certified devices have reached price parity with their non-certified equivalents, and it removes the ecosystem-lock-in risk that dominated smart-home buying for the previous decade. The caveat is checking Thread support specifically for battery sensors, where the local-mesh benefit is real, and not assuming the Matter logo alone answers the cloud-dependency question covered in the plug guide above.

The category gaps that remain today

Two of the categories that lagged at launch are still worth a specific caveat rather than a blanket “it’s fixed now.” Robot vacuum support arrived in the Matter 1.2 specification but remains thin in practice — most current robot vacuums, including market leaders like Roborock and Ecovacs, still ship their own proprietary app as the primary control surface, with Matter support (where present at all) limited to basic start/stop/dock commands rather than the mapping, no-go-zone and scheduling features that are the actual reason to buy a robot vacuum with an app in the first place; the robot vacuum buying guide covers what those apps do that Matter doesn’t yet replace. Security cameras are further behind still — the video-specific Matter extension only reached a usable specification stage in 2024, and camera manufacturers have been slow to adopt it compared with the speed simple sensors and plugs moved, likely because video streaming and local recording raise bandwidth and storage questions the original sensor-focused spec wasn’t built to answer quickly.

The verdict

Buy into Matter as a baseline expectation for new smart-home purchases, but verify the specific transport rather than trusting the logo alone. The interoperability promise — one device, multiple ecosystems, no vendor lock-in — is genuinely delivered for Thread-native devices from committed manufacturers (Nanoleaf, Eve, Aqara’s newer line), and Home Assistant’s Matter support makes it a credible open-source alternative to trusting any single Big Tech ecosystem. The local-control promise is real only where the underlying transport is Thread, not Wi-Fi-with-a-bridge, and that distinction isn’t yet obvious from packaging alone — it takes checking the CSA’s certification database or a teardown report to confirm. Two years on, Matter is worth buying into at zero price premium over equivalent non-Matter hardware; it is not yet worth paying a premium for the badge itself, since the badge doesn’t guarantee the local-first behaviour that was the actual point of the standard.