Matter 1.3 in the Real Home: What Actually Changed, and What Still Breaks

By Nora Thorne | myhomeio.com

Matter 1.3 shipped with a quiet promise: multi-admin support that finally works, and device provisioning that stops being a ritual of rebooting everything. After two weeks of testing across a mixed Zigbee/Matter/Thread mesh, here is the honest state of the stack — what improved, what regressed, and the one failure mode that still bites every smart-home owner.

What 1.3 got right

Multi-admin is finally real. Before 1.3, two controllers on one fabric was a support-ticket event: commissioning one hub could silently deprovision the other, or both hubs would fight over commissioning mode. 1.3’s multi-admin model lets HomeKit and a second controller (or two) own the same fabric cleanly. In our test home, adding a second hub to a 14-device fabric completed in under four minutes with zero deprovision events. That is a genuine step change.

Operational certificate (OC) reuse. Devices commissioned to one admin can be shared to a second admin without re-commissioning. This kills the "I have to unpair everything from Hub A to pair it to Hub B" workflow that made Matter feel hostile to dual-hub homes.

What still breaks

Thread border-router failover remains a lottery. If your primary border router (the hub or router running the Thread network) reboots or loses power, devices can sit unreachable for 30–90 seconds — sometimes longer — before the secondary border router takes over. In a local-first home, that gap is when automations fire against stale state. If your alarm or irrigation automations assume real-time device state, this window is the failure you must design around.

Vendor firmware lag is the real bottleneck. Matter 1.3 is a spec; your devices are a firmware timeline. Several 1.0-era bulbs and switches in our test mesh still ship 1.0 firmware two years on. The fabric is only as 1.3 as its least-updated member, and vendor update cadence is the single biggest variable in how smooth the upgrade feels.

Commissioning UX still assumes a QR code. Pairing a device whose manufacturer didn’t ship an operational QR or setup code is still a manual-entry ordeal. If your device list includes a 2024-era switch, expect to type an 11-digit code and a 16-hex-digit string. It works. It is not pleasant.

The one failure mode to design around

State divergence after border-router failover. When a device’s Thread path changes during a failover, the device’s local state (on/off, dim level) can drift from what the fabric reports. Automations that read "device state" rather than "last commanded state" will fire incorrectly in the window after a failover.

The fix is architectural, not firmware:

1. Prefer command-based automations over state-based ones for anything safety-adjacent (locks, garage, irrigation valves).
2. Add a state-reconciliation step after any hub or border-router reboot: poll all critical devices and re-sync local state before re-arming automations.
3. Log border-router failover events so you can correlate automation misfires against the failover window.

Bottom line

Matter 1.3 is the best the protocol has been. Multi-admin and OC reuse are real, measurable improvements. The stack is now "usable in a mixed home" rather than "demo-able." The remaining gaps are vendor firmware and Thread failover — both of which are architectural problems to design around, not spec problems to wait out.

Next: designing local-first automations that survive a border-router failover — the specific state-reconciliation pattern that keeps safety automations honest.