The Short Answer: Wi-Fi Gets a Number; Thread Gets a Map
Home Assistant Core 2026.7, released on July 1, 2026, adds hidden diagnostic entities for Matter devices. A Matter-over-Wi-Fi device can expose Wi-Fi RSSI in dBm. That is the familiar signal number: -50 dBm is stronger than -80 dBm because a value closer to zero means the receiver hears a stronger signal.
A Matter-over-Thread device does not get one equivalent RSSI entity. Instead, Home Assistant can expose the device's Thread network name, Thread channel, and Thread routing role. To judge Thread radio quality, open Matter Server 9's Network page. Thread is a mesh, so the useful question is not just “How strong is this device?” It is “How well can this device hear each neighbor, and does it have a healthy route home?”
Every new entity is disabled by default. That keeps ordinary dashboards and databases from filling with specialist data. Enable only the diagnostics you will actually use. Home Assistant reads them locally through its own Matter pairing, so Home Assistant Cloud is not required.
Do this first: Check Settings > System > Updates. You need Home Assistant Core 2026.7 or later for the entities described here. The link-by-link Network page comes from Matter Server 9, which Home Assistant announced separately on June 23, 2026.
What You Can Enable on a Matter Device
| Diagnostic | Where it applies | What it tells you | What it does not prove |
|---|---|---|---|
| Wi-Fi RSSI | Matter over Wi-Fi, when the device reports its Wi-Fi diagnostics | The received Wi-Fi signal in dBm. Closer to zero is stronger. | A low number alone does not prove that the device is dropping offline. |
| Thread network name | Matter over Thread | Which Thread mesh the device says it joined. | Matching names do not prove that every route is healthy or that platforms share credentials. |
| Thread channel | Matter over Thread | The radio channel used by that Thread mesh. | The channel number alone does not diagnose interference. |
| Thread routing role | Matter over Thread | Whether the node is a leader, router, router-eligible end device, end device, or sleepy end device. | A role change is not automatically a fault. Thread rearranges roles as conditions change. |
| Reboot count, uptime, and boot reason | Any Matter device that reports its built-in health data | Whether the device restarted, how long it has been running, and why it says it booted. | A reboot reason may be missing or vague, and not every product reports these details. |
| Active hardware, radio, and network faults | Any Matter device that reports its built-in health data | Whether the device currently reports at least one fault in that category. | A clear sensor does not rule out a brief fault that the device never reported. |
Home Assistant creates one of these entities only when the device reports that specific piece of diagnostic data. Two devices on the same network can therefore show different lists. That is a product-reporting difference, not necessarily a Home Assistant bug.
How to Enable the Hidden Diagnostics
- Open Settings > Devices & services > Matter.
- Select the Matter device you want to investigate.
- Expand the section that says there are entities not shown.
- Select Wi-Fi RSSI for a Wi-Fi device, or the Thread network name, Thread channel, and Thread routing role entities for a Thread device.
- Open the entity's settings, choose Enable, and select Update. Give Home Assistant roughly 30 seconds to add it to the device page.
For several devices, open Settings > Devices & services > Entities, filter for disabled Matter diagnostic entities, select only the ones you want, and use Enable. Start with one troublesome device rather than turning on everything in the house.
If the entity is not merely disabled but absent, confirm that the device is really Matter over Wi-Fi or Matter over Thread. A Matter bridge may expose a Zigbee child as a Matter device without passing through the child's radio statistics. A Matter-over-Ethernet controller also has no Wi-Fi or Thread signal to report.
How to Read Wi-Fi RSSI Without Chasing One Number
Matter Server 9 colors Wi-Fi links green above -70 dBm, orange from -70 through -85 dBm, and red at -85 dBm or lower. Those are useful display bands, not universal promises. A device with a stable -78 dBm reading may work for months. Another may fail at -68 dBm because of interference, poor firmware, a busy access point, or power trouble.
The practical value of an entity is its history. Enable RSSI, leave the device in its normal location, and watch it for several days. Compare the dips with the times Home Assistant marks the device unavailable or an automation fails. A repeated fall from its normal -60s into the -80s at the same time as dropouts is much stronger evidence than one red reading.
A quiet alert that can actually help
If a device normally sits well above -70 dBm, a reasonable first experiment is to notify only when it remains at or below -85 dBm for 10 to 15 minutes and the device has also become unavailable or missed a real command. Keep the alert informational. Do not have Home Assistant power-cycle, reset, or re-pair the device automatically.
Before moving hardware, check whether the low reading follows a predictable event: a closed metal door, an access point changing channel, a microwave running, or a plug hidden behind an appliance. Move the access point or add proper Wi-Fi coverage when several nearby devices show the same pattern. Move one device only when the problem belongs to that location.
Why Thread Signal Strength Is Link by Link
Thread devices do not all talk straight to one hub. Mains-powered routers can relay traffic, and battery devices often sleep between reports. A single number attached to the device would hide which neighbor heard it and which direction was weak.
On Home Assistant OS, open Settings > Apps > Matter Server > Open Web UI, then choose Thread. In Matter Server 9, Thread line color is based primarily on the link quality indicator, or LQI: green is greater than 2, orange is 2, red is 1, and gray is 0. Select a connection to see details such as LQI, available signal strength in dBm, direction, path cost, and whether both sides report a usable link.
A red or one-way line deserves attention when the same device is also missing updates. A gray line can be stale neighbor data. Use the map's refresh control and wait for a sleepy battery device to wake before drawing a conclusion. Tara's Matter Server network-map guide explains the colors, arrows, unknown nodes, and refresh behavior in detail.
“Sleepy End Device” is usually normal. It is the expected power-saving role for many battery sensors. Leader and router roles can also move around the mesh. Alert on a role label only when you understand that product's expected behavior; availability and missed reports are better homeowner signals.
Use Reboot and Fault Data to Avoid Blaming the Radio
Signal is only one possible cause of an unavailable Matter device. Home Assistant 2026.7 also adds disabled-by-default General Diagnostics entities. When a product reports them, reboot count, uptime, and boot reason can show whether the device actually restarted. Hardware, radio, and network fault entities can show whether the product itself declared a current problem.
Suppose a plug disappears every afternoon. If Wi-Fi RSSI stays steady but uptime starts over, investigate its power source, thermal load, firmware, or a brownout. If uptime remains steady while RSSI collapses and neighboring devices also weaken, investigate coverage or interference. If the network fault entity turns on while signal looks normal, save the device diagnostics and check the maker's firmware notes before moving your router.
These supporting entities are more useful when enabled for a device that is already misbehaving. Enabling every fault sensor across dozens of devices can create history you never read. Home Assistant disables them by default for exactly that sort of integration-specific reason.
A Safe Troubleshooting Order
- Confirm the software boundary. Use Core 2026.7 or later for entity-level diagnostics and Matter Server 9 or later for the Network map.
- Enable only the useful entities. Start with Wi-Fi RSSI, or Thread name/channel/role, plus uptime and reboot count if the device offers them.
- Observe before changing anything. Give the device several normal days so you know its baseline.
- Match the reading to a real symptom. Look for unavailable periods, missed reports, failed commands, reboot changes, or a fault entity.
- For Thread, inspect the route. Refresh the Matter Server map and look at both directions of the weak link. Add or reposition a mains-powered Thread router only when the route evidence supports it.
- Fix power and placement before re-pairing. A stable network identity is worth preserving. Re-pairing rarely cures weak radio coverage and can break names or automations.
If the device is genuinely dropping, use Tara's focused guides for Matter-over-Thread devices going offline or Matter-over-Wi-Fi devices going offline. If the Thread route is weak at the edge of the house, the Thread range guide shows how to extend the existing mesh without accidentally creating another one.
What These Diagnostics Do Not Do
- They do not turn a bridge child into a radio sensor. An IKEA, Aqara, Hue, or other bridge may expose basic child controls through Matter while keeping Zigbee signal details in its own system.
- They do not merge platform histories. Sharing one Matter accessory with Apple Home, Google Home, Alexa, or SmartThings does not copy Home Assistant's entity history into those apps.
- They do not merge Thread networks. Multi-admin shares a Matter device between controller fabrics; it does not automatically combine separate Thread credentials or meshes.
- They do not prove cloud independence for every feature. Home Assistant reads these Matter diagnostics locally, but a maker may still require an app or account for initial setup, firmware, or extra features.
- They do not make one threshold universal. Use RSSI and LQI as evidence alongside the device's real behavior, not as pass/fail certification.
Tara's Recommendation
Enable diagnostics as a flashlight, not as another dashboard to maintain. For a Wi-Fi device, record RSSI long enough to learn what normal looks like. For Thread, confirm the device is on the intended network and channel, then judge the specific route in Matter Server's map. Add uptime and reboot count when the symptoms could also be power or firmware related.
Only act when the readings line up with a homeowner problem: missed motion, a light that stops responding, a lock that becomes unavailable, or repeated restarts. That keeps a useful diagnostic from turning into a weekend of resets—and it preserves the local Matter setup that is still working.
Frequently Asked Questions
Can Home Assistant show Matter-over-Thread signal strength?
Not as one new per-device RSSI entity in Home Assistant 2026.7. The release adds Thread network name, channel, and routing role entities. Use Matter Server 9's Network page to inspect each Thread link's LQI and the available RSSI details.
Why is the Wi-Fi RSSI or Thread diagnostic entity missing?
First check whether it is disabled. If it is not offered at all, the Matter device may not report that diagnostic data. A bridge child and a Matter-over-Ethernet device may also have no matching radio statistic for Home Assistant to expose.
Is -85 dBm always a failing Matter Wi-Fi signal?
No. Matter Server 9 marks -85 dBm or lower as weak in its visualization, but that boundary is not a universal failure guarantee. Compare the device against its own history and actual unavailable periods.
Does “Sleepy End Device” mean a Thread sensor is broken?
No. It is the normal battery-saving role for many Thread sensors. Thread can also elect a different leader or change router roles as the mesh reorganizes.
Do these Matter diagnostics require Home Assistant Cloud?
No. Home Assistant reads them locally through its own Matter pairing. A product maker may still use its own app or cloud for setup, firmware, or features outside Matter.