node-red / node-red/node-red-nodes
Serial in configuration overwritten by Serial out
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
I am running Node-RED v0.20.7
I noticed that both serial in and serial out nodes have a section for "Input" configuration. It happens that I am using both at the same time for the same port. When I changed the input configuration on the serial in node, I noticed that it's not really changing or doing anything different. Later after lengthy investigation, I realized that's because the serial out node still had the default configuration and node-red apparently deployed the input configuration for serial out last, ignoring the input configuration for serial in.
This is clearly a bug to me, and my suggestion for the solution is to have input configuration only on the serial in node, and output configuration only on the serial out node. This I believe will make more sense to most.
Thank you!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the serial in and serial out node configuration and deployment handling described in the issue, then reproduce the problem with both nodes using the same port. Done means changing the serial in input settings no longer gets overwritten by the serial out node's defaults, with the independent input and output configuration behavior verified.
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
- 25/100