The pitch for Matter, when the Connectivity Standards Alliance published the 1.0 specification in October 2022, was that the smart home would stop being a series of walled gardens. One certification, any controller, no more checking the fine print on a box to find out whether a $40 bulb would talk to the speaker already in the room.

Four years is long enough to judge that. Since last autumn we have run a deliberately mixed household — 34 devices, four controller platforms, three brands of Thread border router — and logged every failure. The short version is that Matter delivered on its promise for the simple half of the smart home and has not yet delivered on the complicated half. That is a more useful outcome than it sounds, because the simple half is most of what people actually buy.

What we ran

The test household holds 11 Matter-certified light bulbs and fixtures from three brands, six smart plugs, four wall switches, five contact and motion sensors, two locks, two thermostats, a robot vacuum, an air purifier, a video doorbell, and an indoor camera. Nine older Hue bulbs joined through the Hue bridge rather than natively.

All of it was commissioned into Apple Home and Google Home, most of it additionally into Alexa, and a subset into SmartThings, to exercise the multi-admin path that the standard’s early releases handled poorly. Border-router duty was shared, on purpose, by an Apple TV, a Nest hub, and an Echo — a configuration nobody would recommend and quite a lot of households end up with.

We recorded every commissioning attempt, every device that stopped responding, and every occasion when a feature required the manufacturer’s own app. Our general approach is described in How we test.

What works now

Lights, plugs, switches, and sensors are solved. This is the headline. Every certified bulb, plug, and switch in the household commissioned on the first or second attempt, appeared in all four platforms, and stayed reachable for the duration. Response latency on local control was consistently under half a second, and — the part that matters more — it did not depend on the internet. Cutting the household’s WAN connection left every Matter light and plug fully controllable from any platform in the house. That was not true of most of these brands’ pre-Matter products.

Multi-admin is real. Sharing one device across Apple Home and Alexa simultaneously works, and it works well enough that a two-platform household is no longer a hardware problem. The flow is still the clumsiest part of the setup experience on every platform — each does it differently, and the terminology is different again — but once done, it holds.

Locks mostly work. Both locks exposed lock, unlock, and battery state to every controller. Neither exposed its full feature set, of which more below.

Bridges are a legitimate answer to legacy hardware. The nine Hue bulbs behind a bridge behaved, from every controller’s point of view, like native Matter devices. Anyone with a substantial investment in a pre-Matter ecosystem should look for a bridge before considering replacement.

What does not

Firmware updates. Not one device in the household could be updated through a Matter controller. Every single firmware update required the manufacturer’s app, and in two cases required an account login the device had not otherwise needed. This is the most consequential gap in the standard as it exists today, because it means the vendor app is never actually optional — it is merely dormant.

Cameras. Camera support entered the specification in the 1.5 release cycle, and the certified-device reality has not caught up. The doorbell and indoor camera in our household appeared in Matter controllers as little more than a live stream and a motion event. Detection zones, package and person distinction, event history, and clip retention all lived in the vendor app, and clips continued to travel to the vendor cloud regardless of which app was displaying them. Readers weighing that trade-off should read our reporting on what your smart-home camera is actually sending to the cloud; Matter does not change that calculus yet.

Robot vacuums and multi-function appliances. The vacuum exposed start, stop, dock, and battery through Matter. Floor plans, room-by-room cleaning, no-go zones, and scheduling — the reasons a person buys an expensive vacuum rather than a cheap one — were vendor-app only. The air purifier exposed fan speed and nothing about filter life, which is the one number an owner needs; our air-purifier roundup covers why that matters more than it sounds.

Thermostats, partially. Setpoint and current temperature came through cleanly on both units. Scheduling, adaptive pre-heating, and humidity control did not, and one of the two silently rejected setpoint changes made from a non-native controller during an active vendor schedule, which is a genuinely confusing failure to debug.

The border-router problem

Twenty-two of the household’s 34 device failures over the test window traced to Thread, and nearly all of those to having more than one brand of border router in the house.

Thread is the low-power mesh radio that a growing share of Matter devices use instead of Wi-Fi, and it is good — low latency, low power, self-healing. The border router bridges that mesh onto the home network, and modern households acquire border routers accidentally: an Apple TV is one, a HomePod is one, several Echo and Nest devices are one, and an increasing number of Wi-Fi routers are one too.

The specification has supported merging multiple border routers into a single Thread network for several releases now. In practice, across three vendors, ours did not merge cleanly. Devices ended up distributed across two meshes with different coverage, and a device at the edge of the house would migrate between them and become briefly unreachable. Nothing in any of the four controller apps surfaced this; the user-visible symptom was “the hallway sensor is unresponsive again.”

The workaround that fixed it for us was inelegant and effective: pick one vendor’s border routers and disable Thread on the others. That is the opposite of what an interoperability standard is supposed to require, and it is the clearest remaining evidence that Matter is not finished.

For readers doing this deliberately, the choice of Wi-Fi hardware matters less than the number of Thread radios you leave switched on — see our Wi-Fi 7 router testing for the network side of the question.

How to buy in 2026

Buy Matter-certified for the boring things. Bulbs, plugs, switches, contact sensors, motion sensors, and locks. Here the logo means what it says, and it protects you from an ecosystem decision you have not made yet.

Ignore the logo on cameras, vacuums, and appliances. Buy those on the merits of the manufacturer’s own app and cloud policy, because that is where you will be using them. Treat Matter support as a small bonus for basic remote control, not as a promise of feature parity.

Standardize your border routers. One vendor, and turn Thread off on the rest. This single decision eliminated most of our failures.

Do not replace working devices. Matter’s value accrues at purchase time. A working bulb is a working bulb, and a bridge will usually get older hardware onto the new standard without spending anything.

The specification’s release cadence has been steady and the direction has been right — every release since 1.2 has widened device coverage rather than merely tidying up. The remaining gaps are not really technical arguments any more; they are commercial ones. A vacuum manufacturer that exposes floor plans over Matter gives up the reason customers open its app, and no standards body can compel it to want that. Whether the complicated half of the smart home ever arrives depends less on the CSA’s engineering than on whether buyers start treating a stripped-down Matter implementation as the defect it is.