node-red-contrib-zigbee
node-red-contrib-zigbee copied to clipboard
hobbyquaker
Network Map nodes display issues
Map works again. However after update 0.11.0 most of the nodes seem like "floating", not connected to any of the routers/coordinator. I also updated to 0.12.0, same behavior. I even deleted the herdsman and started over with adding all the devices. All zigbee sensors work correctly, I receive data from all of them, none of them is out of range or turned off. I'm not sure if this is a display problem or not. Here's how it looks:
(All devices have unique names. I removed device name & address from the screenshot for obvious reasons)
Chrome Version 77.0.3865.90 (Official Build) (64-bit)
They are disconnected if there is no Route or Lqi entry for that device. Can happen when reading the routes fails or no route is established (yet). You can have a look at the log output while generating the map, then you see if there are failing get routingTable commands. I would suggest to just wait a few hours so routes "settle" and then take a look at the map again.
I've checked the Node red log while loading the network map, nothing gets added there. Map looks the same. I'll check back tomorrow.
Small update: Unfortunately the map display is the same. Any idea where to check/how to debug this?
is possible related to: https://github.com/Koenkk/zigbee-herdsman/issues/69 I don't know if that's a Bug somewhere or normal behavior and the way I'm building the map is bad. Have to investigate, give me some time
Thing is... it was working perfectly fine during the shepherd implementation. I have the same number of devices. Also, 4 of my devices are routers in range of most of the devices... so I doubt there's a 3 devices/node limitation
The map is much improved now. I really like the extra info. Also the nodes are connected now. Really like the "Anonymize" feature.
One thing I really loved in past versions and I miss now is the separate URL of the map. One could load the map only. Now it's much harder, as you have to load nodered, click about 4 times to get to the network map. Was there a reason for this change?
That's because I secured the node-red-contrib-zigbee API with Node-RED Authentication - and because I didn't look into if/how it's possible to hand over the auth token to a new window. Will check if it's possible asap.