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
Which node are you reporting an issue on? node-red-node-serialport 2.0.3
What are the steps to reproduce?
drag serial-port control node to canvas
press + to add new serial-port config node
What happens?
You need to enter the serial port path, you will red triangle if not!
What do you expect to happen?
since control node accepts configuration as payload and port can be set in runtime, this is wring behavior,
during development the ports may not exists, if you put port that does not exist on your machine you will get nasty error messages after deploy , ports may exists only in production (may be different architecture or docker image)
the great thing about the dynamic control node is the ability to manage devices changes in runtime (connect/disconnect usb...)
Please tell us about your environment:
Node-RED version: 4.05
node.js version: node-red docker image latest
npm version: node-red docker image latest
Platform/OS: node-red docker image latest
Browser: chrome
The text was updated successfully, but these errors were encountered:
Which node are you reporting an issue on? node-red-node-serialport 2.0.3
What are the steps to reproduce?
drag serial-port control node to canvas
press + to add new serial-port config node
What happens?
You need to enter the serial port path, you will red triangle if not!
What do you expect to happen?
since control node accepts configuration as payload and port can be set in runtime, this is wring behavior,
during development the ports may not exists, if you put port that does not exist on your machine you will get nasty error messages after deploy , ports may exists only in production (may be different architecture or docker image)
the great thing about the dynamic control node is the ability to manage devices changes in runtime (connect/disconnect usb...)
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: