where do i have to change / add those? i know in zwavegraph2.html but where?
I just found this discussion and is exactly what I need to track my 15+ devices.
But I need some help.
I have never setup a custom panel and am having trouble.
Can some one tell me exactly what code goes where.
If I place the panel_custom in my configuration.yaml file my whole side panel goes away. So I must be doing something wrong.
Do I need to create a panels folder?
Sorry but I am confused even after reading the HA docs to set up a custom panel.
1 Like
Use this link: https://gist.github.com/AdamNaj/cbf4d792a22f443fe9d354e4dca4de00
configuration.yaml goes anywhere in your configuration.yaml.
zwavegraph2.html goes in the “panels” folder in your configuration directory. If you don’t have a “panels” folder, just create it.
Then restart Home Assistant.
3 Likes
Thanks. Will give a try tonight.
Just installed this but 3 nodes are showing unconnected . In HA all is good ( disregard the Unkown Node)
I have cleared Chrome Cache , restarted HA . Any ideas ?
@MajorBlunder you will have to wait until those nodes wake up for a two-way comm session with the controller. Depending on how they are configured, that can be once an hour, day, or week. Once that happens (and you haven’t restarted HA since they woke up), it should include them.
Battery devices are in low-power ‘asleep’ mode most of the time and only check in occasionally for things like neighbor reporting and parameter updates as those consume a lot of power.
Any chance of getting this working in the iOS app?
Thank you
works for me…
EDIT: It shows up super small but it works at least. So probably a bug in there somewhere.
When I look at it in a browser I get the little box in the lower right hand corner as well as the larger version centered. I also can’t seem to navigate away from the panel once it is open.
Yeah, i get this on most browsers. I’d consider this a bug.
Swipe right to bring the menu back up.
Except it works perfectly in a browser but not in the iOS app.
Also, swiping right does not work on iOS mobile beta.
You gotta swipe right starting far left, like edge of the screen. I’m running both the old app and the beta and it works in both.
I have issues in all browsers unless I refresh. This might be related to the size of the image produced ‘image’.
Hi chaps,
I’m getting the following error in my logs when using this script. It seems to be working, just wondering if there was a fix ot something i’ve done wrong?
https://cdnjs.cloudflare.com/ajax/libs/dagre-d3/0.6.1/dagre-d3.js:0:0 Script error
Hi,
Just discovered this add-on today, despite having used HA for almost a year. Definitively a must when using Z-wave, and I think it should be part of HA if Z-wave was enabled.
Thanks for Z-wave graph!
Tried downloading the code from git hub, created a panels directory and put the file there and modified my configurations.yaml file. Unfortunately, all I get is a blank page with an empty box in the lower right hand corner. The home-assistant.log file gives a very long error:
2019-08-28 12:31:55 ERROR (MainThread) [frontend.js.latest.201908050] data:text/javascript;charset=utf-8,%0A%20%20class%20HaPanelZWave%20extends%20Polymer.
...
panel_custom%2Fzwavegraph2.js%0A:0:0 Script error.
Can anyone help?
Pretty much every time I use my graph page, I get the same thing and a refresh fixes it.
1 Like
Since you asked for graphs from people with a lot of devices, here you go! Definitely a cluster, but I have over 50 nodes, soon to add about 12 more. =)
Very cool project, thanks for sharing!
I also had the really tiny graph problem (using chrome), but refreshing the page fixed it. The graph also works fine over the Nabu Casa connection too.
Here’s mine looks very…not exciting. Is it normal for a mesh network to not be meshing? Everything has a direct connection to my hub ( HUSBZB-1), and not any sort of hopping amongst each other. Is this because they all have a good connection to the hub and do not need to repeat themselves? Is this efficient?
:EDIT:
If I hover over a node, some dim while others stay lit up. I’m assuming this is showing some sort of relationship between them, but what exactly? The one’s that it would hop to if it needed to?
It’s good that they can all directly connect to the hub, zwave has a limit of 4 hops to reach the hub. The graph shows the optimal route to the hub. If you hover of each node you will see the “neighbors” of each node. As long as a node is a repeater then any of it’s neighbors can communicate via that node back to the hub (eg: node 1 = hub, node 2 = switch, node 3 = switch2. if node 2 has a neighbor of node 1 and node 3 and node 3 is a repeater. Then if node 2 couldn’t communicate to node 1 then it could hop through node 3 to reach node 1.) But the less hops a node needs to communicate with the hub the better.
1 Like
Gotcha, OK awesome.