Hope someone will adapt this to work with ZWave JS or create a new visualization for it.
1 Like
Zwave JS already copied this graph as described here: Better Z-wave network graph.
The only difference is that you now see it inside of the ZwaveJS2MQTT interface rather than the HA interface directly. Since we have Ingress and ZJS2M can be embedded in HA interface I see no further reason to keep working on it. I’ve already migrated to ZwaveJS2MQTT as this is the future of HA.
OK. Since I migrated recently from HA’s zwave to zwaveJS, I’m not so queen to do yet another migration towards zwavejs2mqtt. There were so many messages in the HA updates about how zwavejs was so fantastic that honestly I never considered zwavejs2mqtt and have it a bit hard to hear that it would be “the future of HA”, tbh. Not even mentioning that the HA website literally says “This is our recommended Z-Wave integration for Home Assistant.”
1 Like
I could says this exactly the same way… I’m a bit shocked by that last sentence…
OK, first I wanted to say that I was imprecise. ZWaveJS is the future of HA… as I understand it. (I do not contribute or have any insight over what’s publicly available) I hope this is not news and your shock was simply because I confused you.
ZWaveJS2MQTT is just an extension and a GUI over ZWaveJS. In fact, I do not use the “to MQTT” part of it at all. I use the same WS connection that a regular ZWaveJS would use. For my use I consider them to be one and the same, kind of like full HomeAssistant OS and HomeAssistant Core. For me the best part of ZWJS2M is that is has a great management UI for your ZW network. I would expect there should be an easy way to export the setup from what you have and migrate it to the full ZWJS2M.
1 Like
With the release of HA 2021.7 is it now possible to get this graph working again?
Zwave JS now has a status sensor, although I haven’t found it yet.
The status sensors are disabled entities under the devices. You can enable them, and the value I see is “alive.”
Presumably, if it isn’t “alive” it could be dead, unknown or something else.
The nearest neighbors is not visible with the status. However the logs do contain that information, so perhaps this is possible.
Thanks! At least that’s one more thing I can resolve on my system.
dont forget ‘asleep’ 
These graphs are pointless until zwave-js reports routing data of some type.
Ah, yes, asleep would seem like a likely status. However, when I look at a couple of my battery powered devices that I know to be asleep, they show as ‘alive,’ which I don’t quite understand.
The routing is visible in the log. For example, from my log after triggering “re-interview device”:
...
2021-07-14T15:25:12.535Z CNTRLR [Node 021] Interview stage completed: CommandClasses
2021-07-14T15:25:12.536Z CNTRLR [Node 021] Interview stage completed: OverwriteConfig
2021-07-14T15:25:12.536Z CNTRLR » [Node 021] requesting node neighbors...
2021-07-14T15:25:12.556Z CNTRLR « [Node 021] node neighbors received: 1, 19, 20
2021-07-14T15:25:12.556Z CNTRLR [Node 021] Interview stage completed: Neighbors
2021-07-14T15:25:12.557Z CNTRLR [Node 021] Interview completed
2021-07-14T15:25:12.558Z CNTRLR [Node 021] The node is ready to be used
And for another node (more central to my house):
...
2021-07-14T15:32:44.711Z CNTRLR [Node 012] Interview stage completed: CommandClasses
2021-07-14T15:32:44.712Z CNTRLR [Node 012] Interview stage completed: OverwriteConfig
2021-07-14T15:32:44.713Z CNTRLR » [Node 012] requesting node neighbors...
2021-07-14T15:32:44.728Z CNTRLR « [Node 012] node neighbors received: 1, 2, 3, 5, 6, 7, 8, 9, 10, 11, 13, 14, 15
, 16, 17, 18, 19, 20, 22, 23, 25, 26, 27, 30, 32, 33, 35, 38, 39, 40, 41, 42,
46
2021-07-14T15:32:44.729Z CNTRLR [Node 012] Interview stage completed: Neighbors
2021-07-14T15:32:44.730Z CNTRLR [Node 012] Interview completed
2021-07-14T15:32:44.731Z CNTRLR [Node 012] The node is ready to be used
They just aren’t currently available in entities.
The list of neighbors does not tell you how messages between the nodes are routed.
1 Like
Neighbors are not routes.
@Mariusthvdb Interesting. I wonder why mine doesn’t show that. I will have to tinker… Thanks for sharing that.
I was responding to this:
@freshcoast I guess I don’t know enough about z-wave, but I thought with a mesh network, messages could be routed to/through any neighbor. I do see that we would want to map the nearest neighbor, not necessarily all neighbors, and the list appears to be in node number order, not nearest-to-furthest, so that would be a problem.
You can’t derive the nearest neighbor from the neighbor list. You also can’t assume messages are routed through the nearest neighbor.