WTH not use the same UI/frontend elements to visualize mesh networking topology for wireless mesh network devices in native Zigbee/ZHA, Z-Wave, and Matter integrations?

Month of "What the heck?!"
, , , ,
1

Minor UI/UX annoyance, but for the the sake of a more uniformed user-experince in the UI, why not reuse the same frontend UI elements for the “network topology map” to achieve a consistent look and feel when visualizing the IoT network mesh with routes and links between Z-Wave, Zigbee, and Matter (wireless) devices in the native Matter, Z-Wave JS, Zigbee (ZHA) integrations.

Could the make the Z-Wave and Matter integrations use same UI elements and code for network maps that ZHA (Zigbee)? Maybe make it a new building block integration that those three integrations could all reuse?

For reference, Zigbee, Z-Wave, and Matter IoT devices all use and rely on routers/repeaters in a mesh network and it can sometimes be important for troubleshooting to visualize device links in your mesh networking topology.

The ZHA (Zigbee) integration does have such as network map visualizations in the UI, while the Z-Wave JS and the Matter integration goes not (however the stand-alone Z-Wave JS UI does have the equivalent ):

image
image2199×1886 330 KB

Even nicer would be if could overlay that map onto a house picture with the layout of your rooms/areas, (like what could be done with the Zigzag custom card/panel for Home Assistant):

image
image1920×1057 421 KB

Zigbee network visualization in ZHA UI

The ZHA configuration UI has a tab to visualize device links in your Zigbee network topology.

The network visualization can help to identify devices with poor connection (that is, low values on the link). You will need to look at the ZHA logs to find more detailed information required for troubleshooting.

The visualization shows multi-hop connections between your paired devices and their reported cumulative values of Received Signal Strength Indicator (RSSI) and Link Quality Indication (LQI).

The exact method in which these values are reported depends on the Zigbee network stack used on each device. LQI values can be modified at each step as the message propagates through the mesh networking matrix.

PS: For reference, Zigbee2MQTT also has a alternative way of visualization of network topology map for Zigbee and there are several that made dynamic custom cards for it and ZHA in Home Asssistant dashboard. See example: