-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node-Red is stopped when no ZWave dongle is attached #78
Comments
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. |
I have mapped my zstick to always appear as /dev/zwave no matter which USB port it is plugged into. I posted a how to here: https://thefrinkiac7.wordpress.com/linux-stuff/fix-usb-serial-port-names/ |
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: