[question] Network Graph is a flat line #739
Comments
|
Could you also attach a screenshot? |
|
|
|
@bushvin While you have browser open try to press F12 (chrome) and check if there are errors on console. If so send me a screenshot or the logs you find there |
|
There are no messages whatsoever. |
|
Hummm strange. I would need a nodes dump so, you could use mqtt apis and require Topic You should get the nodes on I know it's not so user friendly right now but I may addd a button on UI to download a bump in future :) |
|
I'm afraid that doesn't seem to get any result except for a 404 I got the MQTT name from the settings page |
|
@bushvin Sorry maybe I didn't explained it well, that needs to be called using MQTT |
|
Ah... my bad... :/ For future reference these were the commands executed: To log to file: To send the command: |
|
@bushvin How are you building z2m? Git clone? |
|
not building, running it in Docker ---
version: '3.7'
services:
zwavejs2mqtt:
container_name: zwavejs2mqtt
image: zwavejs/zwavejs2mqtt:1.2.3
restart: always
tty: true
stop_signal: SIGINT
networks:
- zwavejs
devices:
- '/dev/ttyACM0:/dev/ttyACM0'
volumes:
- zwavejs_store:/usr/src/app/store
ports:
- '8091:8091'
networks:
zwavejs:
volumes:
zwavejs_store: |
|
@bushvin Could you try using version 1.4.0? |
|
This happens to me whenever the neighbors are unknown. What happens if you perform a heal? |
|
@robertsLando @jmgiaever Running that now. keep you posted |
|
@jmgiaever I do see your point in having bad nodes not reporting correct info, but why would that impact all nodes? |
|
The "Network Heal" didn't "cure" the issue. |
|
I sincerly never faced this problem. @AlCalzone ? |
|
Please make a zwave-js log, loglevel That log should probably include a re-interview of an affected node. |
|
Apologies for my absence. The graph still shows a "flatline" Which logs would you like me to put to "silly"?
Are there any particular tasks you want me to perform while logging? |
|
Zwave |
Yep, re-interview one or two of the affected nodes. |
|
Here's the log file. Hope this helps. |
|
Seems that at least node 6 knows its neighbors: Not sure if it was this way before too. |
|
Well, that was also in one of my original posts here. |
|
Oh sorry I didn't see that. Not a problem on my end then :) |
Have you updated to latest 2.0.1 version? |
|
I have now! And still a flatline |
|
@bushvin Ok seems I have found the problem here but I'm not 100% sure about the solution. ATM to draw a connection I check if a node can forward packets, the forward property is evaluated by
Now the question is, would it be ok to remove the |
It might give a false sense of safety if you think Node X is reachable via Y and Z, although it is actually not because Y and Z are sleeping 99.9% of the time. |
|
Ok let us know if replacing the controller fixes the problem :) |
|
Replacing the controller and clearing the browser cache fixed it for me - the graph is working fine now! |
Hummm this is kinda useless as I don't store any nodes information in cache, btw glad the issue is fixed now :) |
|
That's strange - here's the whole story: |
|
Weird, all data are sent via websockets... Let's see if someone else reports this, I will investigate |
|
Aha, I might have found something - should I open a new bug report? After adding a device, a full page reload seems to be necessary (clearing the cache is not required). Otherwise, the neighbors of the controller node are not updated in the graph (i couldn't capture the neighbors of the controller node in the screenshot, but device 10 was missing):
|
|
@andyboeh Yes please open a new bug to keep track of that :) |
|
I have the problem, too. My controller has no neighbors... Resulting in flatline, healing the controller fails. Do you have any suggestions what i can try to fix this? Here are the corresponding logs: |
|
@blackmore190 Could you upload a full zwavejs logs please? cc @AlCalzone |
|
I'm not sure why the controller reports no neighbors. Maybe ask the manufacturer's support? |
|
@andyboeh Replacing the controler solved your problem. Have you changed to another brand or just replacing "the same"? Which Controler or Controlers have you? @robertsLando what do you mean by "full"? Is this enough? |
|
Well, in the meantime, I switched to OpenWrt-flashed Smart Home Gateways that have a generic Z-Wave modules onboard (the device is a SERCOMM NA-502, I've got an ISP-branded version). I use ser2net to connect to the Z-Wave module. |
|
That sounds pretty interesting! Is there a step-by-step guide to flashing and integrating with Homeassistant? Is it reliable? Does zigbee work as well? |
|
Since it's OT, I'll keep it short: You have to disassemble the NA502 and attach a serial console, the instructions are in the commit message: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=a3d8c1295ed9eeceabd78ab86e73b151ae2868a9 I don't have any ZigBee devices, but the controller is detected by the HA integration. I can do a write-up on this if/when I have some spare time. |
|
Hi, Here's what I've tried so far:
The hard reset removed all the nodes (as expected) and when I started adding them back one by one (I only added two nodes), I'm still getting a flat line and the controller still has no neighbors. I'm attaching my homeid.json and zwave logs (set to silly). nodes.json is empty (just has a pair of braces) for some reason, but I'll still attach it. zwavejs2mqtt-store.zip PS: For some reason, GitHub was complaining when I was trying to upload a json file, so I renamed it to .json.txt. Also, I have a nodes dump of my previous setup before doing a hard reset. Please let me know if providing that helps debugging this issue. |
|
The neighbor information is stored in the controller memory and returned by the controller firmware. I don't think there is anything the host software (Z-Wave JS) can do if the information isn't accurate. |
|
Got it. Would you recommend replacing the controller? If so, do you know a good/reliable controller I can use? |
|
Is there any need except a not-so-pretty network map that doesn't tell anything useful anyways? Driver version 9 (in the works) will expose actual routing information on supporting controllers, which can then be used to draw an actually informative network map without relying on neighbor information. |
|
Oh, I honestly don't mind the flat network graph. I was just more worried about the connectivity of nodes to controller. What's happening in my network is that, if, say, a motion sensor triggers a few lights to turn on/off, sometimes there's quite a delay in turning on the lights and sometimes the lights don't turn off at all. My suspicion was that it's probably because controller doesn't have any neighbors which "maybe" adds to the delay? Also, sometimes the nodes become unavailable and I thought maybe the controller not being able to "see" the nodes (as neighbors) makes them be reported as unavailable. 🤷♂️ I'm trying to pinpoint to see if the issue is because of lack of neighbors or if it's something to do with the switches (Inovelli) I'm using. |
|
If the controller actually had no neighbors, nothing should be working. I'm not sure why this information is reported in this way, but it doesn't seem to match reality. |
|
Interesting. Do you have any recommendations on how to proceed? :) |
|
The interesting thing is: most of the time everything works. I also thought, if the controller does not know any neighbors no communication can take place... the practice shows however a different behavior. But now a few observations: My controller was in the basement, there was sometimes a neighbor visible at the controller. My assumption was that the signal is bad, so I brought the controller to the ground floor and suddenly more than half of the nodes were visible as neighbors of the controller. But the very next day, no neighbors were visible.... But the network still works (most of the time). |
Asking the manufacturer support could be one idea. |
|
I'm having similar issues with a flat network graph:
Despite everything seemingly being well-connected: I'm running version 6.4.0 of zwajs2mqtt from the official docker image. Please let me know what other information I could provide to help resolve. Thanks! |
Looks like your controller only lists your battery-powered as neighbors. And battery-powered nodes don't route, so there is no path from the controller to Node 3 for example. According to your neighbors list, there is no mesh - which is obviously not true, but that's what the controller tells zwave-js. You could test out these steps (if you haven't already) and see if this changes things: |
|
OK I will try some of that. Thanks for pointing out that only the battery-operated nodes are connected to the controller...not sure why that is, but will look into it. Still, why would zwavejsmqtt not draw all of the links between the other devices? |
|
The USB extension did the trick! Now, nothing is more than 2 hops away from my controller. Thank you for the hints! |
Thanks for this advice. I got a new zwave.me Stick for replacement and now the controller shows its neighbors. Hopefully this remains working reliable :-) |
z2m tries to give you an idea of how the packets could be routed from and to the controller and uses that to layout the map. AFAIK the neighbor-lines between the nodes are only drawn as secondary info.
Then you had connectivity issues before. But thanks for confirming this also affects the map. |
I have recently adopted ZwaveJS2MQTT, and everything seems to work.
I took the time to perform cleanups, as previous Zwave Control Panels lacked some cleanup features.
My network Graph is a flat line with the controller to the left (in the right purple colour) and all other nodes to the right in grey.
Grey seems to indicate they are not connected, however I can assure you they are, as I can control my nodes
I have not checked all nodes, but those I did, did have 'neighbors' (in the debug section of a node).
I have attached the debug info of my Zwave controller (a Z-Wave.ME UZB) and one of the nodes for reference.
controller.json.txt
node-006.json.txt
I have tested it on Firefox v85.0.1 and Chromium v88.0.4324.150
Any pointers?
The text was updated successfully, but these errors were encountered: