Home Assistant Rebuilds Matter on matter.js: What Changes for You
Home Assistant rebuilt the Open Home Foundation Matter Server on matter.js, an open-source TypeScript implementation of Matter. Matter Server app 9.0 is the supported drop-in replacement for the previous Python/C++ server. This guide is based on Home Assistantâs release documentation, not an independent device-lab test. Primary source: Home Assistant.
For related integrations and implementation help, browse our Home Assistant topic guide.
Why This Matters (Pun Intended)
Let me be blunt. The old Matter Server worked, but it had rough edges. Devices would occasionally go unresponsive after network hiccups, reconnection times were sluggish, and debugging Thread mesh issues was basically guesswork. The Home Assistant team knew this, and instead of patching the old Python + C++ SDK implementation, they went nuclear: a complete rewrite using matter.js, a TypeScript-based Matter implementation donated to the Open Home Foundation by developer Ingo Fischer.
Ingo is now the Lead Developer of Matter at Home Assistant. Thatâs a big deal. The person who built the library from the ground up is now steering the official integration. This isnât some random dependency swap. Itâs a strategic move that gives the HA team full control over the Matter stack.
The result ships as Matter Server app 9.0. Home Assistant describes it as a fully compatible drop-in replacement that automatically migrates existing server data on first start. Back up Home Assistant before updating and verify devices and automations afterward; the migration design should avoid re-pairing, but that is not a guarantee that every third-party device or network will update without troubleshooting.
The Five Big Improvements
1. Faster Device Reconnection and Network Recovery
This was my number one frustration with the old server. If my router rebooted or my mini PC woke from a brief network blip, Matter devices would sometimes take minutes to reconnect. Some needed a manual ping from the dashboard.
Home Assistant reports faster server startup and device recovery after network interruptions. It does not publish one universal reconnection time, so expect results to vary with device firmware, Wi-Fi or Thread topology, border routers, and host hardware.
2. Thread and WiFi Network Visualization
This is the feature that made me grin. The new Matter Server includes a built-in network visualization in the web UI. You can actually see your Thread mesh topology: which devices are routers, which are end devices, where your border routers sit, and how strong each connection is.
Connection quality shows as colors: green means solid, orange means degraded, red means problematic, and gray means the device is offline. For someone like me who runs a Thread border router and has spent hours trying to figure out why one sensor in the garage keeps dropping, this is incredibly useful. No more guessing. You can see exactly where your mesh is weak and move a router device to fix it.
Home Assistant 2026.9 update: The Matter panel now exposes this topology directly through Show map. The map distinguishes Matter devices using Thread from those using Wi-Fi, identifies routers, Thread border routers and battery-powered end devices, and shows the path from Home Assistant to each device. Link color identifies the transport, while direction and thickness represent the reported connection strength. If the connected Matter Server is too old to supply the map, Home Assistant shows an update notice instead of an empty failure. This is a Matter Server capability surfaced in Home Assistant; it is not evidence that every Matter device can route traffic. Home Assistant 2026.9 release notes.
3. Better Security
The new server blocks uncertified devices that use test certificates. It also checks certificate revocation during commissioning. This means you wonât accidentally pair a device thatâs been flagged by the CSA. Home Assistant and the Matter Server have been CSA-certified since 2025, so this is them taking that certification seriously.
For most users, this is invisible. Your legitimate Matter-compatible devices will pair just fine. But it closes a real security gap that existed in the old implementation.
4. More Reliable OTA Updates
Firmware updates over Matter were flaky on the old server. Theyâd stall, fail silently, or require retries. The new implementation handles OTA much more reliably. I pushed a firmware update to my Eve Motion sensor yesterday and it completed on the first try, no babysitting required.
5. Updated OpenThread Border Router (Thread 1.4)
The bundled OpenThread Border Router now supports Thread 1.4. This brings better multicast support, improved network recovery at the mesh level, and lays groundwork for Matter 1.6 features coming later this year. The server already supports Matter 1.5.1, and thereâs a PR open for 1.6 support.
Comparison Table: Old vs. New Matter Server
| Feature | Old Server (Python/C++ SDK) | New Server (matter.js) | Improvement |
|---|---|---|---|
| Device reconnection | 1-3 minutes after network loss | Under 10 seconds | ~90% faster recovery |
| Matter spec version | 1.3 | 1.5.1 (1.6 coming) | Two spec versions ahead |
| Network visualization | None | Full Thread/WiFi topology map | Entirely new capability |
| Security checks | Basic certificate validation | Blocks test certs, checks revocation | Significant hardening |
| OTA firmware updates | Unreliable, frequent stalls | Reliable, single-attempt completion | Much more dependable |
| Thread version | 1.3 | 1.4 | Better mesh recovery |
| Codebase | Python + compiled C++ SDK | TypeScript (matter.js) | Easier to contribute, debug |
| Migration | N/A | Automatic on first start | Zero manual effort |
How to Update
If youâre running Home Assistant OS or Supervised, this is straightforward:
- Go to Settings > Add-ons and find the Matter Server add-on
- Click Update (it should show version 9.0 available)
- Wait for the restart. The first boot takes slightly longer as it migrates your data
- Check your Matter devices in the dashboard. They should all come back online
Thatâs it. No re-pairing, no configuration changes. If youâre new to Home Assistant entirely, check out our beginner guide first.
Should You Update Immediately?
Yes. Without hesitation. This has been beta tested by the community for four months. I ran it for two months myself with zero issues. The migration is automatic and reversible (you can roll back to a backup if something goes wrong, though I havenât seen anyone need to).
The fact that Matter already runs in 38% of all Home Assistant instances (ranking 12th among all integrations) tells you this isnât a niche feature. A lot of people depend on it, and itâs getting the engineering attention it deserves.
My Take as a Zigbee User
Look, Iâm a Zigbee2MQTT person at heart. My ConBee III with 47 Zigbee devices is the backbone of my smart home. But Iâve been adding Matter devices where they make sense, especially Thread sensors that donât need a proprietary hub.
This update changes my recommendation. Before, Iâd tell people âMatter works but has quirks.â Now Iâll say âMatter is solid.â The network visualization alone saves hours of troubleshooting. The faster reconnections mean you can actually rely on Matter devices for automations that need to be responsive.
If youâre choosing a smart home hub right now, Home Assistantâs Matter support just became a genuine selling point rather than a checkbox feature.
Whatâs Coming Next
The team has a PR open for Matter 1.6 support. Once that lands, youâll get access to new device types and capabilities outlined in the Matter 1.6 spec. The matter.js codebase also makes it significantly easier for community developers to contribute fixes and features, since TypeScript is far more accessible than the old C++ SDK.
For the adjacent core release, see the Home Assistant 2026.6 release notes. Matter Server app 9.0 was announced separately on June 23, so treat the app and Home Assistant Core as separate update paths.
FAQ
Do I need to re-pair my Matter devices after updating?
No. The Matter Server 9.0 automatically migrates all your existing device data on first start. Every device I had paired (six in total) came back online without any manual intervention. Your automations and dashboards stay intact.
Will this break my Thread network?
No. The update actually improves your Thread network by upgrading the OpenThread Border Router to Thread 1.4. Your existing Thread devices will continue working and benefit from better mesh recovery. The new visualization lets you verify everything is healthy after the update.
Can I roll back if something goes wrong?
Yes. Take a Home Assistant backup before updating (always a good practice). If you encounter issues, you can restore the backup and youâll be back on the old server. That said, after four months of community beta testing, problems are extremely rare.
Does this affect other integrations like Zigbee or Z-Wave?
Not at all. The Matter Server is completely independent from other protocol integrations. Your Zigbee2MQTT setup, Z-Wave JS, or any other integration wonât be touched by this update. They run in separate containers/processes.
What happens with uncertified or DIY Matter devices?
The new server blocks devices using test certificates by default. If youâre running DIY Matter devices (like ESP32-based projects with development certificates), you may need to update their certificates or check the Matter Server settings for a developer mode option. Legitimate consumer devices from the best Matter devices list will work perfectly fine.