node-zwave-js: [Bug]: Node-red crashes on a restart with an error that "z-wave driver" is not ready (see paste of logs from NOde-red below)
What happened?
I have noticed this happening on a few different Hubs in the past few weeks. the Zwave interface becomes unresponsive and then Node-Red dives into a restart. Most times it eventually recovers but I have one Hub right now that will just not get past the “uncaught error”.
I am using a Zooz 700 Z-wave dongle. One possibility is that the firmware is 7.17 and the latest version is 7.18.
How to reproduce?
Please list steps to reproduce. If the problem is hardware-specific, please list which devices are affected.
Version
8.0
Node-RED Version
3.0.2
What hardware are you seeing the problem on?
Other Linux
Relevant Z-Wave-JS log as a text file
May 02 20:51:12 rosedale-apt-multi-N200 Node-RED[2746]: 2 May 20:51:12 - [error] ZWaveError: The controller is not yet ready! (ZW0103)
May 02 20:51:12 rosedale-apt-multi-N200 Node-RED[2746]: at Driver.get controller [as controller] (/home/pi/.node-red/node_modules/zwave-js/src/lib/driver/Driver.ts:708:10)
May 02 20:51:12 rosedale-apt-multi-N200 Node-RED[2746]: at Driver.shouldDiscardCC (/home/pi/.node-red/node_modules/zwave-js/src/lib/driver/Driver.ts:3607:21)
May 02 20:51:12 rosedale-apt-multi-N200 Node-RED[2746]: at Driver.serialport_onData (/home/pi/.node-red/node_modules/zwave-js/src/lib/driver/Driver.ts:2895:14)
May 02 20:51:12 rosedale-apt-multi-N200 systemd[1]: nodered.service: Main process exited, code=exited, status=1/FAILURE
May 02 20:51:12 rosedale-apt-multi-N200 systemd[1]: nodered.service: Failed with result 'exit-code'.
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 24 (16 by maintainers)
Will try to get this fixed later tonight
Thanks Marcus. I temporarily resolved the problem by removing the nodes which were calling the zwave driver immediately after a reboot or re-deploy which is probably a preferable design in any event but look forward to the release where the fix is released.
@AlCalzone,
Have marked this as upstream - if its not, do let me know.
Thank you for theses inputs. I will use the code fences going forward.
A few other pieces of information which may help.
I have over 50 hubs running the same hardware and identical NR flows and have not had this before when NR just won’t restart. There is an ongoing issue where Zwave-JS seems to force a NR restart on a larger network whenever a new device is joined.
I have a suspicion that the error on the particular device is hardware related. Possibly the USB port or the dongle have a some issue. I am going to reload the installation onto a new Hub and see if this resolves anything
Weird, the logs do show 10.16.0, but the line numbers in the error log line up with where those are in 10.15.0 🤔
Just checked the npm package for 10.16 to be sure - its contents are what I’d expect.
This should already be fixed in the latest driver release.