node-red / node-red/node-red-nodes

Serial-port control node settings

Open
#1,086 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.1k
Forks
612
Avg merge
13h 57m
Merged PRs (30d)
3

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the node-red-node-serialport 2.0.3 implementation and its serial-port control node configuration editor. Reproduce adding a serial-port config node, then verify whether the port path can remain unset during development while the runtime payload supplies it, without deployment errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
embedded-iot
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.