-
-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Network graph accuracy #3474
Comments
In home assistant go to Settings > Devices & Services > Click Z-Wave Logo > Click # Devices > Click on the device you want to view > Click : > Click Statistics > Click Last Work Route to see more details. |
The network graph is built using the most accurated info we have from controller like: LWR: Last working root Everything is built by the internal zwave protocol algorithm and sometimes it's known to do some weird things, that's why we added the possibility to customize the routes |
Ah, I'm only using ZWave-JS-UI, not Home Assistant. Once it's set up and running, I only really want it for the MQTT bridge (and the UI will just be taking memory on my router for nothing, as discussed in #3473). |
You don't need home assistant to view that info, you can see that from ui too in network graph by clicking on a node |
What do you mean? Generally the priority is only shown if you set it. The LWR details can be detected based on the color of the link, see legend |
Not sure if this is a bug, I'll start as a question... I don't believe the Network Graph is telling me the truth, or I just don't understand it.
Here's a sample:
![Screenshot from 2023-12-07 13-23-16](https://private-user-images.githubusercontent.com/911239/288771256-88872f05-b4a9-43aa-91e1-ac909424416b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzNzMwODIsIm5iZiI6MTczOTM3Mjc4MiwicGF0aCI6Ii85MTEyMzkvMjg4NzcxMjU2LTg4ODcyZjA1LWI0YTktNDNhYS05MWUxLWFjOTA5NDI0NDE2Yi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjEyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxMlQxNTA2MjJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1lZWRlNzQxNmI2Y2RlMWU2OGNmOTg3ODRhN2U2MWEwODNiN2RmOGI1M2E0MTU2NjM4MTVlMTlkYzMyNjBmM2U4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.WE7PSZYma2oM6UjqaqrbUuCdNr3fQvtEksCnUugzMTM)
There's weirdness in some of these routes but that might be true — for example the "Bathroom light" has "Connie light" as a neighbour, and that would be fewer hops. But I've seen nodes shown in grey as not accessible, even when I can ping them (and check back afterwards that they're still shown as inaccessible). Surely that can't be true?
But mostly... see that 'Primary controller' that's allegedly routing only to the ZWave-JS-UI 'Controller'? That's the real primary controller of this network., running on my production Domoticz box that I haven't yet converted to use ZWave-JS-UI. It works just fine when the USB stick that I'm using for testing ZWave-JS-UI is unplugged, so I'm fairly sure that it does have more routes of its own.
Am I misunderstanding? I know that operating as a secondary controller is not fully supported — is that what's making the routes get reported strangely?
The text was updated successfully, but these errors were encountered: