Twenty-Three Gadgets Later: What Matter Still Gets Wrong in a Real House
Photo: smart home thread border router Matter devices on shelf, via ugc.futurelearn.com
Matter was supposed to be the end of the app roulette. One logo, one setup, one local fabric, and every bulb, lock, and sensor would show up in whatever ecosystem you already use. I wanted to believe it. I have 23 Matter devices in a real house now: bulbs, plugs, door sensors, motion sensors, two locks, a few bridges, and three Thread border routers. After living with Matter 1.4 and the updates that followed, the honest scorecard is: better, not fixed.
The basic promise works. A Matter bulb pairs with a QR code, joins a Thread network, and responds to on/off and dimming from Apple Home, Google Home, and Home Assistant. A Matter plug does plug things. A Thread door sensor reports open and closed without a vendor cloud. When it works, it is genuinely nice. Local control is fast, and the device does not care whether the internet is up.
The problem is that 'works' is doing a lot of lifting.
Bridges are where features go to die
A bridge is a translator. It takes a vendor's proprietary protocol and exposes a Matter version of it. That is great for keeping old gear. It is terrible for feature parity. My Hue bridge exposes bulbs to Matter, but not the fun stuff: power-on behavior, effects, adaptive lighting, or firmware updates. The lock bridge exposes lock and unlock, but not user codes, auto-lock timing, or the audit log. You get the lowest common denominator, and the vendor app still owns the good parts.
If you want the full device, you are back in the vendor app. That is not a Matter failure exactly. It is a bridge limitation. But it means the logo on the box does not tell you what you will actually get. A native Thread device usually exposes more than a bridged device, and a native device with a local API is still the gold standard.
Multi-admin is still a group project
Multi-admin is the feature that lets one device show up in more than one ecosystem. In theory, you commission once and share the device. In practice, it is a negotiation between fabrics. Thread credentials, IPv6 prefixes, and mDNS all have to line up. Sometimes they do. Sometimes you factory reset a sensor because Apple Home and Google Home disagree about who owns the fabric. Sometimes the device is visible in one app and 'unavailable' in another until you reboot the border router.
The border router situation has improved. Thread 1.4 and later firmware have made credential sharing less painful. But 'less painful' is not 'invisible.' If you have three border routers, you have three chances for a topology change to confuse a sleepy sensor. I keep a Thread sniffer around for the bad days. A logic analyzer on the module's UART is still the fastest way to see whether the radio is even talking to the host.
Locks are the stress test
Locks are where the sober view hits hardest. Matter lock support covers lock, unlock, and basic state. It does not cover the things people actually care about: managing PIN codes, setting schedules, reviewing who opened the door, or handling firmware updates across ecosystems. Those features live in the vendor app or a proprietary bridge. If you want a smart lock that is fully local and fully featured, you are often choosing a vendor ecosystem, not Matter.
That does not make Matter locks useless. A Matter lock that works locally with Home Assistant is a good lock. But do not buy one expecting the certification to erase the app. It will not.
What Matter actually does well
Matter is very good at simple, local, low-risk devices. Bulbs, plugs, sensors, and switches are the sweet spot. Commissioning is more consistent than the bad old days of per-vendor hubs. Multi-admin works often enough to be useful for lights. Thread is a solid low-power mesh for battery sensors. If your goal is 'the lights turn on without a cloud round trip,' Matter delivers.
It is also good at giving makers a target. If you build a device with a Matter stack, you can expose it to the major ecosystems without writing three integrations. That is real progress. The catch is that the stack is not a magic wand. You still need to test commissioning, multi-admin, and recovery after a power cut.
Why local control beats the logo
The most reliable devices in my house are not the ones with the most certifications. They are the ones with a local API and a documented way to talk to them. Matter helps by making local control the default for basic functions. But it does not guarantee that every function is local, or that the device will keep working without the vendor's cloud for setup and firmware.
My advice after 23 devices: buy Matter for the simple stuff, keep the vendor app for firmware, and run a local hub you control. Test multi-admin before you commit to a device. If a bridge hides a feature you need, assume it will stay hidden. And keep a sniffer and a logic analyzer in the drawer. Matter 1.4 made the house less dumb. It did not make it plug-and-play.