Zigbee2MQTT Network Map Shows Devices as Siblings to Coordinator

[grebenyuk51]

When using Zigbee2MQTT, the network map displays some devices as "siblings" to the Coordinator, which should not be possible according to Zigbee network topology. In a Zigbee network, the Coordinator is the root node (depth 0) and has no parent, so it cannot have siblings. Devices directly connected to the Coordinator should be its children (depth 1), and devices sharing the same parent are siblings to each other, not to the Coordinator.

This issue was observed in the Zigbee2MQTT network map, where certain devices (e.g., End Devices or Routers) are incorrectly shown as siblings to the Coordinator, often with adepth of N/A, despite functioning correctly in the network. This behavior is unexpected to me. Is there any explanation of this phenomenon?

[grebenyuk51]

Morove, the network map sometimes indicates that Device A is a parent of Device B, while Device B is simultaneously shown as a parent of Device A. This is not possible in a Zigbee network, as it violates the hierarchical structure (directed acyclic graph) of the protocol. A node cannot be both a parent and a child of another node, as this would create a circular dependency in depth and addressing.

[Koenkk]

Could you please open a discussion here: https://github.com/Nerivec/zigbee2mqtt-windfront/discussions ?

[BigData-SmallMind]

I was wondering the same, when i started my zigbee network it was all connected when i had the isParent and isChild marks on and the isSibling turned off. now there seems to be three clusters or i dont know what to call them. I am not an expert to be honest but I am hopeful to learn something about how the zigbee network works and specially inside homeassistant's z2m.

[M1cha]

To me the whole hierarchy also doesn't make any sense. In addition to what others mentioned, I have devices where A is the parent of B, but B is not a child of A.

[wenstarner]

When using Zigbee2MQTT, the network map displays some devices as "siblings" to the Coordinator, which should not be possible according to Zigbee network topology. In a Zigbee network, the Coordinator is the root node (depth 0) and has no parent, so it cannot have siblings. Devices directly connected to the Coordinator should be its children (depth 1), and devices sharing the same parent are siblings to each other, not to the Coordinator.

This issue was observed in the Zigbee2MQTT network map, where certain devices (e.g., End Devices or Routers) are incorrectly shown as siblings to the Coordinator, often with adepth of N/A, despite functioning correctly in the network. This behavior is unexpected to me. Is there any explanation of this phenomenon?>

I have this issue as well. Please see below: