Direct answer: If Home Assistant 2026.9 does not show the Matter network map—or the map says the server is unsupported—do not reset or recommission your Matter devices. First confirm that Home Assistant Core is updated, the Matter integration is loaded, and the Matter Server is new enough to provide topology data. The map is a diagnostic view, not the control path itself: a missing map does not prove that your fabric, Thread credentials, or paired devices are broken.
Quick diagnostic
Time: 10–15 minutes. Risk: Low if you stay in read-only checks. Have ready: Home Assistant Core version, Matter Server version, installation type, one working Matter device, and whether that device uses Wi-Fi or Thread.
Fastest safe check: Open Settings → Devices & services → Matter. If the Matter integration and devices work but Show map is absent or reports an old server, update the supported Home Assistant components in the normal order, allow them to finish starting, and check again.
Do not do yet: Do not delete the Matter integration, remove a fabric, reset a border router, erase Thread credentials, or factory-reset devices merely to make the map appear.
What changed in Home Assistant 2026.9
Home Assistant 2026.9 brought the Matter Server’s network topology into the Home Assistant interface. The Matter panel can now show how devices connect: Wi-Fi versus Thread, routers and border routers, end devices, recognizable access-point or host names, and links whose appearance represents transport and reported signal information. Before this release, similar topology data could exist in the Matter Server’s own interface while remaining out of sight for most Home Assistant users.
The official release notes also state that when the Matter Server is too old to support the feature, the page should explain that instead of silently failing. That distinction matters. “Unsupported” is primarily a version or capability message. It is not evidence that the device must be recommissioned.
The network map closes an observability gap, but it does not change the fundamentals of Matter. Operational traffic still relies on local IPv6, permitted routing, discovery, a functioning Matter Server, and—when the device uses Thread—at least one usable Thread border router connected to the Home Assistant LAN.
Symptoms this guide covers
You may see no Show map button in the Matter panel, a message saying the Matter Server does not support the map, an empty or incomplete map, devices appearing without expected routes, Thread devices absent while Wi-Fi Matter devices appear, or a map that loads while one device remains unavailable. These symptoms belong to different layers and should not be treated as the same failure.
This guide does not assume that the map itself caused a device outage. If every Matter device became unavailable after an update, begin with service, network, IPv6, and border-router health. If the devices still respond and only the visualization is missing, preserve the working system and troubleshoot the map separately.
Failure matrix
No Show map control: confirm Home Assistant 2026.9 or later, the correct Matter panel, and that the frontend finished updating. Unsupported-server message: check the Matter Server version and update it through the supported installation path. Map loads but is empty: confirm devices are commissioned to this Matter fabric and allow topology data time to populate. Wi-Fi devices appear but Thread devices do not: inspect the Thread integration, border routers, preferred network, and local IPv6. One device is missing: check that device’s current availability and transport instead of rebuilding the entire fabric.
1. Confirm the version boundary
Record the Home Assistant Core version shown in Settings → System → Repairs or the system information page. The Matter network map is a Home Assistant 2026.9 feature. If the installation is older, the absence of the new control is expected. Update only through the supported process for your installation type, and make a current backup first.
If Core is already on 2026.9, install the latest available patch release rather than remaining on the initial .0 release. As of September 27, 2026, the official release page lists Home Assistant 2026.9.4. Patch releases contain bug fixes, so the exact patch level belongs in every useful problem report.
After an update, allow the frontend and integrations to load fully. Refresh the browser once. If another device or browser displays the new interface correctly, a stale client cache is more likely than a server-side Matter problem. Do not use cache clearing as the first explanation when server logs show an actual exception.
2. Separate Home Assistant Core from Matter Server
Home Assistant Core supplies the interface and integration, while the Matter Server handles Matter communication and topology data. Updating Core does not automatically prove that every supporting component is current in every installation type. Home Assistant OS and supervised installations typically manage the official Matter Server app through the normal app/update interface. Container and custom deployments require their own supported version management.
Open the Matter integration and inspect the available version and diagnostic information without exposing fabric credentials. If Home Assistant explicitly says the server is too old for the map, update the Matter Server through the supported channel. Avoid replacing it with an arbitrary development image merely to gain a feature.
After the Matter Server restarts, wait for the integration to reconnect. Verify an ordinary Matter command before evaluating the map. This establishes that the operational layer is healthy. If control fails after the server update, collect the Matter Server and Home Assistant logs before restarting additional components.
3. Confirm you are looking at the correct Matter fabric
A Matter device can participate in more than one ecosystem through multi-admin commissioning. The device shown in Apple Home, Google Home, or a manufacturer app is not automatically proof that it belongs to the Home Assistant Matter fabric. The Home Assistant map can only describe topology known to the connected Matter Server and its fabric.
Check the device list inside Home Assistant’s Matter integration. If the device does not exist there, the missing map node is expected. Do not remove it from another ecosystem blindly. Use the manufacturer’s and Home Assistant’s supported multi-admin flow if you intend to share the device with Home Assistant.
If the device exists and responds in Home Assistant but its map details are incomplete, allow time for data collection and compare again. Battery devices sleep to conserve power, and network information may not appear with the immediacy of a mains-powered router.
4. Distinguish Wi-Fi Matter from Matter over Thread
Matter is the application standard; Thread and Wi-Fi are network transports. A Wi-Fi Matter device communicates through the local IP network and access point. A Matter-over-Thread device depends on the Thread mesh plus a border router that forwards encrypted Matter traffic between Thread and the local IPv6 network.
Home Assistant’s 2026.9 map uses different link information to help distinguish these paths. If Wi-Fi Matter devices appear but Thread devices do not, concentrate on the Thread layer. If both transports are missing, first check the Matter Server, integration, and map capability rather than assuming every radio path failed simultaneously.
The official Matter documentation recommends keeping Matter devices, border routers, and Home Assistant on compatible local networks. Router or access-point options that claim to optimize multicast can interfere with discovery. A complex VLAN design can also violate the local-network assumptions Matter expects.
5. Check the Thread integration without changing credentials
Go to Settings → Connectivity → Thread. Confirm that the expected Thread networks and border routers appear. Home Assistant’s Thread documentation explains that the integration tracks Thread networks and credentials; it also notes that the preferred-network behavior is still not complete in every commissioning path because a mobile device’s preferred Thread network can influence onboarding.
Document which network Home Assistant marks as preferred, which network the phone uses, and which border routers are visible. Do not delete unknown credentials simply because multiple networks appear. Apple, Google, and Home Assistant border routers can create distinct Thread networks with different credentials.
If the OpenThread Border Router app is used, verify that it is running and inspect its logs. A serial or radio configuration problem can affect the Thread path even when the Matter Server itself is healthy. If the border router recently changed, preserve the prior configuration until the new path is verified.
6. Verify local IPv6
Thread is IPv6-only. Home Assistant’s Thread documentation specifically warns that a device can join the Thread mesh yet remain unreachable beyond it when IPv6 connectivity or forwarding is missing. Internet-provider IPv6 is not the same requirement; local IPv6 communication still matters even when the household has no globally routed IPv6 service.
Confirm that the Home Assistant host has local IPv6, that the router permits the required local path, and that container or VLAN layers do not discard IPv6 or multicast discovery. Avoid broad firewall exceptions. Make narrow, documented tests, and restore any rule that does not change the result.
If a device is controllable in Home Assistant, operational IPv6 for that path is already working at that moment. Do not redesign the network just because the visualization is incomplete. Use the map as supporting evidence, not as the only health test.
7. Interpret an incomplete map
An incomplete diagram can reflect sleeping devices, unavailable nodes, data that has not populated, a device on another fabric, or a server capability gap. It does not automatically identify weak signal. Compare the map with actual device availability, command success, event updates, and the Thread or Wi-Fi diagnostics available for that device.
Look for patterns. If all Thread end devices disappear but border routers remain, inspect the Thread mesh and credentials. If one battery sensor is absent while everything else works, wake or operate it using the manufacturer’s normal method and check again later. If the map itself never loads, focus on frontend, integration, and Matter Server logs.
8. Diagnose a map that loads while a device is unavailable
A topology line is not proof that application communication succeeds. The map may show the last known route while a device is currently asleep, powered off, blocked, or failing subscriptions. Open the device page and compare its entity update times, diagnostics, and command behavior.
For a Wi-Fi Matter device, confirm power, Wi-Fi association, local IPv6, VLAN rules, and mDNS behavior. For a Thread device, confirm border-router health, mesh coverage, and the network credentials used at commissioning. Avoid recommissioning until you have established that the current fabric relationship is actually lost.
Use Troubliq’s Matter device pairs but shows unavailable guide when device control is the problem rather than the map itself.
9. Safe restart order
Collect evidence first. Then reload the Matter integration if that control is available. If the server remains disconnected, restart only the Matter Server through its supported interface and wait for it to become ready. Restart Home Assistant once only when logs or integration state justify it. Rebooting the host, router, border routers, access points, and devices together destroys the evidence needed to identify the responsible layer.
After each change, verify one ordinary Matter command, one state update, and the map. Record what changed. If a server update fixes the map but not device availability, treat those as separate problems.
10. What to include in a useful problem report
Record Home Assistant Core version and patch, Matter Server version, installation type, whether the affected device uses Wi-Fi or Thread, device brand and model, border-router models, network layout, exact visible message, and the time of the last failure. Include sanitized logs from the Matter Server and Home Assistant.
Never publish setup codes, QR codes, fabric credentials, Thread credentials, authentication tokens, public addresses, or unredacted diagnostics. Troubliq’s Home Assistant Log Sanitizer can remove common private values locally in the browser before a log is shared.
Verification checklist
The Matter integration loads normally. An ordinary Matter command succeeds. State changes return to Home Assistant. The Matter Server meets the version required for the 2026.9 topology feature. The Show map control opens without an unsupported-server message. Expected Wi-Fi and Thread paths appear over time. Missing devices are investigated individually rather than erased from the fabric.
Rollback and recovery
If a supported Matter Server update introduces a new operational problem, preserve logs and use the recovery path documented for that installation type. Do not restore an entire Home Assistant backup solely because a visualization is absent. A full restore can roll back unrelated configuration and credentials.
If you changed a firewall or VLAN rule during diagnosis, restore the original rule when it did not help. If you restarted a border router, allow the mesh time to settle before drawing conclusions. If a device was accidentally removed, follow the manufacturer’s supported commissioning or multi-admin process; do not copy credentials from public examples.
Prevention
Keep Home Assistant Core and the official Matter Server on supported stable versions. Review release notes before monthly upgrades. Maintain a current backup. Record border-router ownership and Thread network names. Avoid unnecessary Thread channel changes and broad network changes. Keep Matter, Thread, and local IPv6 documentation with the household’s recovery notes.
Treat the map as a diagnostic aid. The best health check remains successful control, timely state updates, stable subscriptions, and predictable recovery after an ordinary restart.
Related Troubliq resources
Use the Smart-Home Diagnostic Decision Tree when the failing layer is unclear. Use the Device Unavailable Diagnostic for a protocol-neutral first pass. Check Home Assistant Problems Right Now for current version-specific notes.
Official sources and review record
Home Assistant 2026.9 release notes; Home Assistant Matter documentation; and Home Assistant Thread documentation.
Last reviewed: September 28, 2026. Testing disclosure: Troubliq synthesized current official documentation and documented platform behavior. We did not claim hands-on testing with every Matter device, Matter Server build, border router, router, VLAN, or Thread topology.