Update status: Available in Home Assistant 2026.9, announced 2 September 2026. Last verified: 25 September 2026 against Home Assistant’s release notes and documentation. This is a documentation-based owner briefing; WesternTechy has not independently tested the feature on physical hardware.
A Matter device that drops offline can be maddening because “it is connected” conceals two quite different networks: Matter-over-Wi-Fi and Matter-over-Thread. Home Assistant’s September release brings its existing Matter network visualization into the ordinary Matter panel. Instead of switching to a separate Matter Server interface, an administrator can see the network around Home Assistant, the route through a Thread border router or Wi-Fi access point, and details the devices actually report. The benefit is a more specific question to investigate—not a guarantee that the graph identifies the cause of every outage. Home Assistant’s official 2026.9 release notes describe the change.
The short version
- Where: Settings → Connectivity → Matter → My network → Show map, if your installation meets the prerequisites.
- What you see: Matter devices, the reported connection paths, router/border-router or access-point roles, device status and signal details where available.
- What you need: Home Assistant administrator rights plus Matter Server app 9.2.0 or newer; a separately managed Matter server must be version 1.4.0 or newer, according to the current Matter integration documentation.
- What this is not: an automatic Wi-Fi optimizer, an all-protocol inventory, proof that an “offline” device is physically defective, or a reason to reset an entire smart home.
What changed in September—and what already existed
Home Assistant’s Matter Server moved to the matter.js-based architecture in June 2026. That rollout introduced a network visualization in the server’s own web interface. The 2026.9 Core release added a Show map button directly inside Home Assistant’s Matter panel. These are two different milestones: installing the new server is not the same as updating the main interface that exposes its map. The June Matter announcement calls the new server a compatible replacement for its predecessor, with an automatic migration on first start, but that is not a substitute for backing up your own system.
The 2026.9 release also reorganized protocol settings under Settings → Connectivity. Older instructions that say to look for Matter directly on the Settings root may no longer match your screen. The current documentation’s map prerequisites are more specific than the original June announcement: the app must be at least version 9.2.0, or the independently run server at least 1.4.0.
Check eligibility before troubleshooting the missing button
| Check | Expected condition | If it fails |
|---|---|---|
| Home Assistant interface | Core 2026.9 or a later release that includes the integrated map | Review your actual installed Core release; the old server web UI and the integrated panel are different interfaces. |
| Permissions | You are signed in as a Home Assistant administrator | Use an authorized administrator account; do not share someone else’s login. |
| Matter Server app | 9.2.0 or newer for the Home Assistant app | Update the app using the supported route and review its release notes and backup state. |
| Self-hosted Matter server | 1.4.0 or newer | Update the server you manage, not an unrelated Home Assistant app. |
| Device reporting | Topology data has been received from online devices | An empty or incomplete map can reflect unavailable data rather than a pairing failure. |
How to open and read the map
From an administrator session, open Settings → Connectivity → Matter. Under My network, choose Show map. Home Assistant places itself at the center and shows Matter devices around it. Search can identify a node by name, manufacturer, model or node ID. Selecting a known device can open its device page; a border router, Wi-Fi access point or unknown node may not have a device page.
Use the legend instead of memorizing colors: theme colors can change. A Thread router forwards traffic for other Thread devices; a Thread end device does not. A border router bridges a Thread network into your home IP network. Wi-Fi Matter devices appear with their access point when that information is available. Ethernet Matter devices can appear without a graph connection. Those appearances are not evidence that Ethernet connectivity is broken.
A connection’s detail panel can expose the network type and signal strength in both directions when reported. If a connection is known only through a Thread routing table, Home Assistant may show an overall signal indication rather than separate directional measurements. This distinction matters: a pretty line is not a calibrated, universal RF reading.
Three practical ways to use it
Case 1: one Thread sensor appears offline
Suppose a battery-powered sensor has stopped updating while nearby devices still respond. First record the last-seen time and whether the device is truly unreachable. Look at the map’s reported route and the status of the surrounding Thread router and border router. Compare the symptom with the sensor’s own battery, manufacturer diagnostic and placement guidance. A map can tell you what Home Assistant knows about the path; it cannot prove the sensor’s battery is bad, that a wall causes interference or that you need another router.
Case 2: a Wi-Fi Matter plug responds intermittently
Check whether the graph identifies its Wi-Fi access point and whether any directional signal details are available. Then compare the access point’s own diagnostics, device power and recent network changes. Matter does not make the Wi-Fi transport immune to weak coverage, overloaded equipment or network configuration mistakes. Before replacing a plug, test it where the manufacturer allows, verify the correct network, and rule out an ordinary power issue. Avoid exposing your router login, Wi-Fi password or device pairing codes in screenshots sent to support.
Case 3: the map looks incomplete after an update
This is not necessarily a device failure. A message saying that the connected server does not support topology points to the server version prerequisite; a message saying topology data is not yet available means Home Assistant has not received that detail. Read the actual message and check versions before taking action. The Refresh topology action asks every online Matter device for network detail and can take a few seconds. Use it when the view seems stale, not as a constant polling habit.
What the graph does—and does not—cover
| It helps with | It does not establish |
|---|---|
| Which reported Matter device communicates over Thread or Wi-Fi | That every Zigbee, Z-Wave, Bluetooth or cloud-linked device belongs on this Matter map |
| The route Home Assistant knows, plus available device/link details | An exact cause of packet loss or a validated wireless site survey |
| Identifying an offline node or a missing topology response | That a device is defective or that a factory reset is necessary |
| A starting point for comparing border-router, access-point and end-device paths | That an announced Matter device type is already supported by your specific controller and hardware |
A Matter logo identifies an interoperability framework, not proof that every controller exposes every optional feature. The separate Matter Server announcement discusses progress toward newer specification support; do not infer that a new camera, closure or doorbell category will automatically work in your existing software and firmware combination. Verify a model’s current certification, controller support and vendor documentation before buying.
A careful update path for a working home
- Document the current state: installed Core and Matter Server versions, current Matter devices, any pre-existing unavailable nodes and one or two critical automations.
- Back up first: use the backup method appropriate to your installation and confirm the backup finishes. Home Assistant recommends a recent backup before updating; see its configuration and backup guidance.
- Read both release notes: Core and the Matter Server component are separate update surfaces. Do not update merely to clear a missing map without checking the required version and release guidance.
- Retest a small set: a Thread sensor, a Wi-Fi device, one routine depending on each, and a manual fallback. If an entry looks odd, compare actual device function with the graph rather than making a destructive change from a visualization alone.
- Record the result: version, checked date, device model, actual symptom and whether the issue persists after ordinary non-destructive checks.
Why it matters to renters, homeowners and local-control users
For a renter, being able to distinguish a battery end device from a Thread router can help plan placement without resorting to permanent wiring or mounting. A homeowner adding rooms can compare routes and verify whether new devices actually report topology. A household using Home Assistant for local control gets a clearer diagnostic view of Matter devices, but the map itself does not turn a cloud-only product into a local device or change the building’s electrical requirements. Keep manual operation and the installation’s existing safety constraints intact.
If you are planning a first setup, our room-by-room smart-home planning worksheet captures controller, power and network requirements before purchase. For an existing installation, the smart-home setup Guide explains the overall sequence. The map is a diagnostic companion, not a substitute for planning.
Before you contact support: a compact issue record
| Field to record | Example of a useful, non-sensitive entry |
|---|---|
| Software | Home Assistant Core version; Matter Server app or self-hosted server version |
| Device | Brand, exact model, firmware, Thread or Wi-Fi where known |
| Symptom | Offline since a specific date; physical/manual control still works or fails |
| Map state | Offline node, unknown route, server unsupported or no topology data message |
| What changed | Updated app, router placement, replacement access point, power cycle |
| Result | Whether the device recovered; details of a nondestructive check |
Do not include Matter setup codes, private network credentials, access tokens, camera footage or sensitive household details in a public troubleshooting thread.
Official sources and verification record
- Home Assistant 2026.9 release notes — official announcement dated 2 September 2026: embedded map, settings reorganization and other release changes.
- Home Assistant Matter documentation — map instructions, server minimum versions, network legend, availability messages and refresh behavior.
- June 2026 Matter Server announcement — matter.js migration and the earlier standalone visualization.
- Home Assistant configuration and backup guidance — backup-before-update guidance.
Editorial note: This report distinguishes documented product behavior from hypothetical troubleshooting examples. WesternTechy has not performed a hands-on performance comparison, measured radio signals or guaranteed any device’s compatibility. Release and server-version information was verified 25 September 2026 and should be rechecked against the official documentation when you use it.