Short Answer: Open Matter Server, Then Check the Device and Its Link
On Home Assistant OS, open Settings > Apps > Matter Server, select Open Web UI, and choose Thread or WiFi. Matter Server is Home Assistant's local controller app for Matter, the common smart-home standard. If a tab is missing, confirm that at least one Matter device of that type is already added, or commissioned. A Thread border router—the powered bridge between Thread's low-power mesh and the home network—can exist without being a Matter accessory on this map.
Start with one rule: the color of the device shape describes device status, while the color of a connection describes the reported link. A red device is considered offline. A red connection is weak. Those are not the same diagnosis. Click the affected device, refresh its connection data, test whether Home Assistant can control it, and compare what its online neighbors report before moving or resetting anything.
Thread's powered routers choose and change paths automatically. The Wi-Fi view includes commissioned Matter-over-Wi-Fi devices, while link details depend on what each device reports. The map narrows the search; it does not prove that every missing line is a broken route. This guide decodes that evidence. Use Tara's Thread range guide for placement changes and the Matter Server 9 recovery guide when the app itself will not stay online.
Version note: This guide was checked on July 10, 2026 against the official Matter Server app 9.0.4, which bundles matterjs-server 1.1.7. Later versions may refine labels or refresh behavior, so keep the node-versus-link distinction and check the current legend.
What the Device Colors Mean
The official dashboard calls each device or discovered participant a node. That simply means one item on the map. Its main color answers “what does Matter Server know about this item?”
| Node color | Plain-English meaning | What to do |
|---|---|---|
| Gray | Online and commissioned—meaning added—to Home Assistant's Matter fabric. A fabric is the secure controller relationship between Matter Server and the device. | No action from color alone. Inspect its connections only if control is slow or unreliable. |
| Blue | The node you selected in the dashboard. | Use the detail panel to read its role, neighbors, signal, and refresh controls. |
| Red | Matter Server currently considers the commissioned device offline or not responding. | Refresh, test the device, check power or battery, and look for a shared failed path before resetting it. |
| Orange | Unknown or external to Home Assistant's Matter fabric, but seen in Thread neighbor data. | Do not remove anything. Identify whether it belongs to Apple, Google, HomeKit, a border router, or stale data. |
Orange does not mean intruder, defective device, or failed pairing. It means this Matter controller cannot fully query that node. One Thread mesh can carry devices controlled by several Matter fabrics, plus Thread infrastructure that is not a Matter accessory at all.
What the Connection Lines Mean
For Thread, line color is based on Link Quality Indicator (LQI), a small radio-quality score. For Wi-Fi, it uses RSSI, a signal measurement in decibels; a number closer to zero is stronger. Do not compare a Thread LQI number directly with a Wi-Fi RSSI number.
| Map evidence | Thread meaning | Wi-Fi meaning | Homeowner takeaway |
|---|---|---|---|
| Green line | Strong reported link, normally LQI 3. | Reported RSSI stronger than -70 dBm. | Good signal evidence, but not proof that the device software or controller is healthy. |
| Orange line | Medium reported link, LQI 2. | Reported RSSI from -70 to -85 dBm. The current view can also show unknown RSSI as orange and label it RSSI: Unknown. | Watch for repeated failures before changing placement; an orange Wi-Fi line may mean the signal value is missing. |
| Red line | Weak reported link, LQI 1. | Reported RSSI at or below -85 dBm. | Check placement, interference, and alternate routes. A red line is not the same as a red device. |
| Gray or no usable line | LQI 0 means stale, dead, or unusable neighbor data. In the current stable graph, some LQI-0 edges are omitted instead of drawn. | Gray is not a normal Wi-Fi link color in the current stable view. A device that reports no access-point ID may have no access-point edge. | A missing line alone does not prove the device is offline. |
| Dashed line | One endpoint is offline or external, or only one side reports a usable link. | The commissioned Wi-Fi Matter node is offline. | Refresh the online Thread endpoints or troubleshoot the offline Wi-Fi node; look for a pattern, not one snapshot. |
| Arrow | Only one side reports seeing the other; the arrow points from the reporting node. | Not the normal Wi-Fi star view. | Possible range imbalance or stale table. No arrow usually means both Thread nodes report each other. |
Clicking a Thread connection can expose signal and routing details. Cost is a cumulative path score: lower is generally preferable, while extra hops or weaker links can raise it. Bidir is the quality seen in both directions for router links. One measurement is not a service history, so refresh and compare it with actual device behavior.
What the Thread Role Badges Mean
- Amber crown — Leader: the router currently coordinating Thread network decisions. This is not the same as Home Assistant “owning” the device, and another router can become Leader later.
- Blue swap arrows — Router: an always-listening Thread node forwarding traffic for other devices.
- Small dot — End Device or REED: an end device, or a router-eligible end device that Thread may promote if the mesh needs it.
- Zzz — Sleepy End Device: usually a battery sensor, button, or lock whose radio sleeps to save power. Sleeping is normal; it is not an offline warning by itself.
- No badge: the role is unspecified or cannot be queried, especially for an external node.
A known Thread border router uses a crown when it is also Leader or a wireless-router icon when it is not. A teal star marks the primary Backbone Border Router, an internal role that coordinates Thread traffic across the home-network backbone. It is separate from the Leader role, and the star alone requires no homeowner action. None of these icons tells you where automations live or whether an Apple, Google, Alexa, SmartThings, or vendor feature needs cloud service.
Use the Map as Evidence, Then Take One Safe Step
Protect essential devices first. For locks, garage doors, alarms, HVAC, leak shutoffs, and plugs powering critical equipment, keep manual control available and use a maintenance window. Do not power-cycle, remove, or reset a safety-relevant device merely to improve the map.
| What you see | What it may mean | Safe next step |
|---|---|---|
| One red node | That device is not responding to Matter Server; power, battery, device software (firmware), or its current route may be the cause. | Refresh it, test control, and safely wake or power-cycle only that device if its manual allows. To save a report, open Settings > Devices & services > Matter, open the menu, and select Download diagnostics. |
| Several red nodes behind the same area or router | A shared powered Thread router, border router, access point, or network path may be down. | Check the common powered equipment before touching the battery devices. |
| Online node with a red or one-way link | The device still works, but one reported path is weak or asymmetric. | Refresh with connected neighbors, observe whether Thread chooses another route, then change placement only if failures repeat. |
| Zzz device with old-looking data | A sleepy battery device has not checked in recently. | Test its real sensor or button action. Wake it according to the manual only if needed; do not expect constant radio traffic. |
| Orange Unknown or External node | Another Matter fabric, HomeKit-only device, border router, range extender, changing radio address, or stale neighbor entry. | Refresh and compare network names or known hubs. Do not factory-reset a working ecosystem to make the map prettier. |
| Expected device is missing | It may not be commissioned to this Matter Server, may not be classified as a Thread or Wi-Fi Matter device, or may use Thread without Matter. Missing diagnostics normally causes sparse connections, not a missing commissioned node. | In the same Matter Server Web UI, open Nodes. Then check Settings > Devices & services > Matter > Devices before re-pairing anything. |
| Thread map looks fragmented | Neighbor reports can be incomplete, stale, or different from an OpenThread Border Router's own topology. | Refresh online nodes and compare actual failures. A sparse drawing is not proof of separate Thread networks. |
| Every Thread device is red, Wi-Fi Matter works | The shared Thread border router, Thread mesh, local IPv6 addressing, or multicast discovery traffic is more likely than many simultaneous device failures. | Check border-router power and the intended Thread network; use Tara's Thread and connectivity guides before resetting devices. |
How to Refresh Without Fooling Yourself
- Select the affected node. Save a screenshot and note the time so you can compare rather than rely on memory.
- Use Update connection data. For an online Thread device, the dashboard re-reads its neighbor and route tables.
- Include connected online neighbors when useful. This asks the nearby reporting devices what they see from their side.
- For an offline or external node, refresh through online neighbors. The unavailable node cannot answer directly, so its neighbors are the evidence source.
- Test the real device. Trigger the sensor, operate the light, or read its latest timestamp. A map change without a real symptom is not a repair.
- Make one reversible change. Restore power to one router, move one plug, or simplify one network rule, then refresh again.
The map is not documented as a continuously polling live monitor. Thread neighbor entries and border-router discovery can linger after a reboot or removal, and some products report slowly. Give the mesh time to settle. Repeatedly resetting devices can erase the evidence and commission them onto the wrong Thread network.
Why Apple, Aqara, and Other Hubs Can Appear Twice
An orange external router can be perfectly normal. Matter Server learns about border routers through local mDNS, the announcement traffic devices use to advertise themselves, and also sees radio addresses in Thread neighbor tables. Some Apple and Aqara border routers use a stable discovery identifier but a different Thread radio address that can change after reboot. The dashboard may therefore show the known border router and a second external router that is actually the same physical box.
The current Matter Server documentation says there is no protocol-level cross-reference that lets the dashboard merge those two identities reliably. A stale radio address can also remain until neighbor tables age it out. Refresh first and compare the Thread network name. Do not delete an Apple Home, reset an Aqara hub, or clear phone credentials solely because the drawing has an extra question mark.
What the Matter Network Map Cannot Tell You
- It is not every device in the house. The Wi-Fi view covers commissioned Matter-over-Wi-Fi devices, not all Wi-Fi clients. The Thread view starts with diagnostics from Matter devices on this server and best-effort border-router discovery.
- It is not a live packet route. Thread can choose a different path after the snapshot.
- It is not a history chart. One red link does not say how long it was weak or whether it caused yesterday's failure.
- It is not a radio interference scanner. Wi-Fi, Bluetooth, Zigbee, walls, appliances, and device firmware can still matter.
- It is not the Thread network-password page. Use Home Assistant's Thread integration to inspect networks and their preferred credentials, which are the saved network passwords. The map does not merge separate meshes.
- It cannot fully inspect another Matter fabric. A device controlled only by Apple Home, Google Home, Alexa, or another controller may remain external even on the same Thread mesh.
- It does not identify cloud dependency. Matter control may be local while voice, remote access, firmware, accounts, or vendor-only features still use a cloud service.
The Local-Control Boundary
The map's data collection and ordinary Matter control are local to the home, although you can view the dashboard remotely if you have configured a secure Home Assistant remote-access path. Thread devices talk across the low-power mesh; a Thread border router forwards their encrypted traffic onto the home network; Matter Server controls devices over that local path. Supported models and configurations of Apple TV, HomePod, Google Nest, Alexa/Echo, SmartThings, DIRIGERA, or a Home Assistant OpenThread Border Router can be part of the transport story without automatically becoming the automation brain.
That distinction is useful when the map shows an external device. It may belong to another controller but still share the same Thread radio mesh. Matter's multi-admin feature can let more than one platform control one accessory, but it does not merge Thread credentials or duplicate the device onto another radio network. Keep important automations in one place so a signal investigation does not get mixed up with duplicate platform routines.
Tara's Practical Recommendation
Use the map to choose the next check, not to justify the next reset. First separate node status from link quality. Then refresh the selected device and its online neighbors, test the real device, and look for a shared failure pattern. A single weak link suggests placement or interference. Many Thread failures together suggest the border-router or local-network path. One stubborn model on a healthy map suggests firmware or device behavior.
For a supportable home, keep one known Thread network, stable powered routers, simple local networking, saved Matter setup codes, and a short record of which platform commissioned each device. That makes the new map useful evidence instead of another screen full of unexplained icons.
Related Tara Reading
- How to extend Thread range without creating a second network
- Matter Server 9 stuck on Starting or Offline
- Why Matter pairing gets stuck on Checking network connectivity
- Which Thread border router should you use?
- How Matter multi-admin works across platforms
- Will Home Assistant and Matter work without internet?
FAQ
Where is the Matter Server 9 network map in Home Assistant?
On Home Assistant OS, open Settings > Apps > Matter Server > Open Web UI, then choose Thread or WiFi. Do not open the Thread integration or OpenThread Border Router dashboard by mistake.
Does a red line mean the Matter device is offline?
No. A red node means Matter Server considers that device offline. A red line means the reported link is weak. The device can remain online through that link or another route.
Why does the Thread map show an Unknown or External device?
It can be a device on another Matter fabric, a HomeKit-only Thread device, a border router, a range extender, or a stale neighbor entry. Some Apple and Aqara border routers can appear twice after their radio address changes. Unknown is not automatically a fault.
Why is my Matter device missing from the map?
It may not be commissioned to this Matter Server, may not be classified as a Thread or Wi-Fi Matter device, or may use Thread without Matter. If the node appears but has few or no connections, the product may not expose the network details the map needs. Check Nodes in the Matter Server Web UI and Settings > Devices & services > Matter > Devices first.
Should I factory-reset a device because the map looks wrong?
No. Refresh the node and its neighbors, test actual control, check power and shared infrastructure, and save diagnostics. Reset only when the device-specific recovery path requires it and the Matter setup code is safely recorded.