[Bug]: network map has no lines (at all)

[TzachiGuetta]

What happened?

The network map of my zigbee devices has no lines at all
I tried to:

1. switch to dev branch
2. upgrade my adapter to latest version
   but the issue is still occurred

In logs I have:

Error Failed to execute LQI for 'Coordinator'
Info Network scan finished

What did you expect to happen?

to have lines between the cordinator and the endDevices

How to reproduce it (minimal and precise)

1. go to http://192.168.68.85:8080/#/map
2. click on Load map

Zigbee2MQTT version

1.24.0

Adapter firmware version

20211217

Adapter

SONOFF Zigbee 3.0 USB Dongle Plus (CC2652P)

Debug log

Failed to execute LQI for 'Coordinator'
Info Network scan finished

[Shred99]

I'm now running a second, much smaller Zigbee network in parallel with my main one and I'm having the same problem:

• ZigBee2MQTT version is 1.24.0
• Coordinator is a CC2531 (I know...) with firmware 20211115

The map worked perfectly while the coordinator was running firmware 20190608. I swapped out the CC2531 for a different one with the 20211115 firmware and the problem with the map appeared.

It may be relevant that the network has no routers.

[TzachiGuetta]

update:
I update my Adapter firmware version to: 20220219
and I updated my Zigbee2MQTT version to: 1.25.0
but the issue is still occurred

[Shred99]

I think the common link between your network and mine is that we both have small networks with no routers. It could be argued that the map functionality is pretty redundant in this sort of network anyway.

You could try adding a router, or downgrading your coordinator firmware to something ancient (mine worked perfectly until I upgraded the router firmware). The problem with doing this is that you may need to re-pair the devices (I vaguely recall that downgrading below a certain version broken things?) and that if you have any sensors that need new firmware, they will break.

[TzachiGuetta]

tried to:

1. add router (a usb stick of SONOFF Zigbee 3.0 USB Dongle Plus)
2. using the shipped version of my Adapter

but the issue is still occurred
@Shred99 @Koenkk

[Koenkk]

Could you check if this firmware fixes the Error Failed to execute LQI for 'Coordinator'?
Note that even after this fix no lines might appear, see https://www.zigbee2mqtt.io/guide/faq/#why-are-some-links-missing-from-my-networkmap

znp_CC1352P_2_LAUNCHXL_tirtos_ccs.hex.zip (only flash this fw on a SONOFF CC2652P coordinator)

[TzachiGuetta]

@Koenkk, thank you for responding!
just tried what you suggested, but the issue is still occurred

- Debug Received MQTT message on 'zigbee2mqtt/bridge/request/networkmap' with data '{"routes":false,"transaction":"1ajh0-1","type":"raw"}'
- Info Starting network scan (includeRoutes 'false')
- Error Failed to execute LQI for 'Coordinator'

[Koenkk]

@TzachiGuetta I cannot reproduce it, could you provide the herdmans debug logging starting from the point where you startm z2m until this error?

See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable the herdsman debug logging. Note that this is only logged to STDOUT and not to log files.

[TzachiGuetta]

updated image of my network map:

[TzachiGuetta]

@Koenkk, sorry for the late respond, missed your comment.
log as a file:
DEBUG=zigbee-herdsman* npm start.log

[Koenkk]

Added some additional logging, can you update to the latest dev and provide the logging again?

Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html)

[TzachiGuetta]

@Koenkk new logs on dev branch
z2m.log

[Koenkk]

@TzachiGuetta interesting, could you stop z2m and look what the nwkAddr of your coordinator is in the data/database.db? It should be 0. If it is not 0 change it manually, start z2m and see if the issue still appears.

Example:

{"id":1,"type":"Coordinator","ieeeAddr":"0x00124b0018e1af91","nwkAddr":0,"manufId":0,"epList":........

[TzachiGuetta]

@Koenkk FIXED!
thank you!
by the way, the value was: "nwkAddr":38978

[Koenkk]

@TzachiGuetta great that that solved it, however I would be interested how the nwkAddr got 38978 in the first place (this is the real bug). If you are able to reproduce it please let me know

[fortellerq]

I am not sure what lead to this situation, but I can confirm that I changed cc2531 coordinator to SONOFF Zigbee 3.0 USB Dongle Plus (CC2652P) with the same firmware as OP. Then I started to receive this "Failed to execute LQI for 'Coordinator'" message during map update, but in my case I have routers. That lead to map showing this:

As you can see, LQI and lines are visible for routers, but not for end devices. That has been fixed by changing nwkAddr of coordinator to 0 as Koenkk suggested. In my case I had 21942 as nwkAddr of Coordinator. After chaning, map looks like this:

(had an issue with one sensor in the meantime, so "Czujnik temperatury zewnątrz sypialnia" wasn't connected, even though it should on previous screenshot)

[ampersandru]

i recently updated my ZBDongle-P to 20211217 and have the latest zigbee2mqtt and having the same issues. After updating the dongle, all the things that were plugged in seemed to have to be re-paired as they would report but not respond to commands.

No issues with devices connecting to routers but nothing wants to connect to the coordinator which is an issue with a lot of aqara devices which don't like to reconnect to routers unless you initially pair it with the router.

Im looking at database.db and it does show the Coordinator nwkAddr as 0