Matter Saver - Monitor & Diagnose all your Matter/Thread devices in one dashboard

After dealing with 43 Matter/Thread devices (all IKEA) and zero visibility into which ones were offline, what their Thread roles were, or how the mesh was structured, I built Matter Saver - a custom component that gives you complete control over your Matter network.

The Problem

Matter devices in Home Assistant have no central overview. After restarts, devices go offline silently. There’s no way to quickly see which node is down, what its Node ID is, how it connects through the mesh, or why it has communication errors. The only option was clicking through 43 devices one by one in the Matter Server UI.

What Matter Saver Does

5 Dashboard Views:

Status - Sortable device table

  • 14 columns: Node ID, Name, Area, Product, Status, Thread Role, Neighbors, Children, Parent Router,
    Power, Battery, Firmware (with update indicator), Error Count with diagnosis, Last Seen
  • Click any column header to sort with automatic group headers
  • Search field filters across all fields
  • Click device name → Action Popup (Ping, Re-Interview, Reset Error Counters)
  • Click parent → Route Popup showing full mesh path to HA with RSSI/LQI per hop

Activity Log

  • Every online/offline change logged with timestamp
  • All manual actions (Ping, Interview, Reset) with results
  • Persistent - survives HA restarts
  • Filterable

Topology

  • Tree view: each Router with its connected End Devices
  • Leader first, sorted by number of children
  • Quick overview of mesh structure

Mesh Visualization

  • Interactive SVG network graph
  • HA in center, Routers in circle, End Devices around their parents
  • Color coded by role (gold=Leader, green=Router, grey=SED)
  • Red glow on devices with >10k errors
  • Drag nodes, pan, zoom (mouse wheel)
  • Hover for device details

Help

  • Full documentation of every column, popup, action, and color code
  • Troubleshooting guide

Smart Repair Workflow

The Action Popup adapts its recommendations based on what you’ve already tried:

  1. First suggestion: Ping to check Thread-level reachability
  2. If Ping OK → suggest Re-Interview to rebuild Matter connection
  3. If Interview fails → offer Matter Server Addon Restart button
  4. If everything fails → suggest physical power cycle

All actions are logged and the repair history is shown per device.

Thread Diagnostics

  • Error analysis: CCA errors (channel interference), TX aborts, RX frame errors - with human-readable comments like “strong channel interference, many TX aborts”
  • Route tracing: See the exact path from any device through the mesh to Home Assistant, with signal
    strength at each hop
  • RSSI color coding: Green (>-70dBm), Orange (>-85), Red (<-85)

Installation

HACS

  1. HACS → ⋮ → Custom repositories
  2. Add GitHub - cnc-lasercraft/matter-saver: Custom Component for Home Assistant - Monitor Matter/Thread device status · GitHub as Integration
  3. Install → Restart HA
  4. Settings → Integrations → Add → Matter Saver

Manual

Copy custom_components/matter_saver/ and the 4 JS files from www/ to your config.

Requirements

  • Home Assistant 2024.1.0+
  • Matter Server addon
  • Matter/Thread devices

Links

Built to make sense of 43 IKEA Matter/Thread devices. Hope it helps someone else! Feedback (PLEASE!!!) and contributions welcome.

4 Likes

Looks promising.
I got a test setup with some IKEA Matter/Thread devices and some ESPhome openthread devices, connected via an openthread borderrouter.
Does your integration help with no matter but thread devices?

For me the cards are not availble after HACS installation

same here, no cards

Same cant find cards.

The idea is excellent, but unfortunately I’m also unable to see any cards after adding it as an integration. It only shows one device and four entities.

@CNCLC, is there any progress on this?

I got it to work using the manual method, but be sure to pay attention to the way your HA installation references locations for the dashboard resources. /local/* didn’t work for me, it had to be /hacsfiles/*

this looks more like a fast vibecoding experiment to me than solid old school engineering :wink:

I hate when developers do not post screenshot of their apps/cards, especially when it is all about dashboard.

2 Likes

I got it to work using the manual method, but be sure to pay attention to the way your HA installation references locations for the dashboard resources. /local/* didn’t work for me, it had to be /hacsfiles/*

@thuer could you please post some screenshots here?