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

Serialport: "not connected" will not be sent from status node

Open
#888 10 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

What are the steps to reproduce?

image

Set an unused COM Port!

[{"id":"8f77ef3358816793","type":"serial in","z":"14972ae43ba3a3f1","name":"","serial":"1b909dd2b3f2dc6e","x":250,"y":1820,"wires":[["17b4a55b44609a6f"]]},{"id":"17b4a55b44609a6f","type":"debug","z":"14972ae43ba3a3f1","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":390,"y":1820,"wires":[]},{"id":"4490c6afdf741d52","type":"status","z":"14972ae43ba3a3f1","name":"","scope":["8f77ef3358816793"],"x":240,"y":1880,"wires":[["fb90753a624cf048"]]},{"id":"fb90753a624cf048","type":"debug","z":"14972ae43ba3a3f1","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":390,"y":1880,"wires":[]},{"id":"1b909dd2b3f2dc6e","type":"serial-port","serialport":"COM3","serialbaud":"115200","databits":"8","parity":"none","stopbits":"1","waitfor":"","dtr":"none","rts":"none","cts":"none","dsr":"none","newline":"0xd","bin":"false","out":"char","addchar":"0x0D","responsetimeout":"10000"}]

What happens?

I get an error msg in the debug window but no msg from the status node. Also no msg from catch node.
So in this case i get no information and cannot pull further actions.

What do you expect to happen?

A msg "Not connected" from the status node, so i can send an email, telegram ...

Please tell us about your environment:
  • Node-RED version: v2.2.2
  • node.js version: v16.14.0
  • npm version:
  • Platform/OS: win10
  • 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 with the node-red-node-serialport implementation and reproduce the unused-COM-port case from the issue, observing the serial in node, status node, and catch node. Done means the status node emits a "Not connected" message that can trigger follow-up actions, with the existing error behavior verified.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.