Matter 1.3 and later: what changed for real deployments
Matter 1.3 and the releases after it moved the standard from "smart bulbs and plugs" toward the rest of the house: energy management, EV chargers, larger appliances, water and environmental sensors, plus steady reliability work on the Thread mesh and the commissioning flow.
What's genuinely better
| Area | Change | Why it matters |
|---|---|---|
| Device types | Energy, EV charging, appliances, water/air sensors | The categories where lock-in hurt most now cross ecosystems |
| Thread reliability | Border-router and mesh fixes | Fewer "device unreachable" failures, the top complaint |
| Commissioning | Smoother multi-admin pairing | One device, multiple ecosystems, less fiddling |
What's still rough
- Beyond-spec features don't cross over. A vendor's proprietary mode still needs the vendor's app.
- Migrating an existing non-Matter home is still work — you're re-pairing devices one by one.
- Border-router quirks still cause setup failures on specific hub/router combinations.
If you're buying now
Buy Matter-over-Thread for anything battery-powered (sensors, locks, bulbs) and Matter-over-Wi-Fi for anything that moves data. Check the device lists it against your existing hub, and expect the core function to be portable while the extras stay in the vendor app.
What would move the needle further
Broader appliance-maker adoption (the big white-goods brands shipping Matter by default) and a clean migration path for existing homes. Until then, Matter is a strong choice for new devices and a poor reason to rip out working ones.
Related Intelligence
- GlossaryWhat is Matter in smart home devices?
- GlossaryWhat is unified memory, and why does it matter for AI?
- GlossaryWhat is VRAM, and how much do you need for local AI?
- GuideHow to build a local AI server with used GPUs: the RTX 3090 & Tesla P40 guide
- GuideBuilding a Tesla P40 rig for local AI: what you're really signing up for