You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When no ZWave dongle is attached (or is broken), Node-Red server stops.
This scenario happened to me and others a couple of times.
The user is not informed what happened.
Not everyone Node-Red user can solve this issue.
The proposal is not to call "process.exit()" in method driverFailed() in file "10-zwave.js".
It would be nice if the error message could be shown in the node info (instead of "disconnected").
The text was updated successfully, but these errors were encountered:
Another issue I experienced regarding to this, is the fact that the USB device changes when un/plugging my ZWave stick from/into my Raspberry Pi. I edit the flow file and restart node-red, but something tells me, this can be fixed in an easier way.
Now I see that the issue has been fixed (except the info status) in the latest version on Github.
But unfortunately this version is not yet in npm repository?
When no ZWave dongle is attached (or is broken), Node-Red server stops.
This scenario happened to me and others a couple of times.
The user is not informed what happened.
Not everyone Node-Red user can solve this issue.
The proposal is not to call "process.exit()" in method driverFailed() in file "10-zwave.js".
It would be nice if the error message could be shown in the node info (instead of "disconnected").
The text was updated successfully, but these errors were encountered: