Why lqi value in device info is different from it in topology?

[strawberryhcy]

I know what these two lqi values represent in the topology.But i want to know it in the device info.Why two device (coordinater and router)have 3 lqi value?

[MattWestb]

The topology is done with requesting all routers neighbors and the links to them.
The device cars is made from the LQI that the coordinator is getting with the package revived from the network and its depends of the rout its taken and if end devices is direct connected to the coordinator with EZSP you is very likely getting 255 in most firmware versions (best is blocking the coordinator having direct children for getting more stable network).

[strawberryhcy]

The topology is done with requesting all routers neighbors and the links to them. The device cars is made from the LQI that the coordinator is getting with the package revived from the network and its depends of the rout its taken and if end devices is direct connected to the coordinator with EZSP you is very likely getting 255 in most firmware versions (best is blocking the coordinator having direct children for getting more stable network).
I want to know why the values on the page are different from those in the topology diagram. As far as I know, the value of lqi comes from two places, but it has three values that are different from each other.

[strawberryhcy]

I want to know why the values on the page are different from those in the topology diagram. As far as I know, the value of lqi comes from two places, but it has three values that are different from each other.

[Shulyaka]

As @MattWestb already described, they come from 3 different sources. For the topology, the two LQI between the routers are requested from those routers. For the device info, the LQI is provided by the coordinator firmware and, depending on the firmware, could actually be the LQI of the last hop (i.e. between the coordinator and the nearest router)

[strawberryhcy]

As @MattWestb already described, they come from 3 different sources. For the topology, the two LQI between the routers are requested from those routers. For the device info, the LQI is provided by the coordinator firmware and, depending on the firmware, could actually be the LQI of the last hop (i.e. between the coordinator and the nearest router)

Thank you for your answer. But in the connection between the router and coordinator, the neighbor table only has one value, and to my knowledge, the other value is the connection quality of the last message determined by the coordinator firmware
dmulcahey/zha-network-visualization-card#46 So, I still feel puzzled about this.

[Shulyaka]

Every value in the topology graph comes from the neighbor tables. It could be the neighbor table of the coordinator itself if the coordinator supports loopback ZDO frames. Two devices would give two values for the link between them. See https://github.com/zigpy/zigpy/blob/50bb2171341bd44239898cfd3dd77b22ac49a03e/zigpy/appdb.py#L332

And the device info (and the zha network card) comes from the coordinator firmware with the last received packet, see
https://github.com/zigpy/zigpy/blob/50bb2171341bd44239898cfd3dd77b22ac49a03e/zigpy/application.py#L1008

I would not rely on the value in the device info because it is only for the last hop (and you would probably be more interested in the first hop).

[MattWestb]

@Shulyaka What is the LQI / RSSI coming for the https://github.com/dmulcahey/zha-network-card ?
I think its its from the nigbur scan from all routers in the network then i have seen it being updated then clicking update and sniffing the network.

[Shulyaka]

It comes from the device attributes (i.e. from the coordinator firmware), not the neighbor scan.

[dmulcahey]

https://github.com/home-assistant/frontend/blob/f43171f91c51a354fb0d7f8d7f152ab95e8fc16a/src/panels/config/integrations/integration-panels/zha/zha-network-visualization-page.ts#L248

The topology in HA uses the neighbor tables.

[MattWestb]

@dmulcahey is your https://github.com/dmulcahey/zha-network-card#zha-network-card using neighbor scans or the last hope to the coordinator ?

[dmulcahey]

The table is last hop set by zigpy on a per message basis. Neighbors are not used to build the table.

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.