-
Notifications
You must be signed in to change notification settings - Fork 595
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-node-serialport message duplication #1069
Comments
Have more or less the same issue with Node-Red 4.05 and node-red-node-serialport 2.0.3 on Windows 11: If the serial port was disabled using "Serial Control" Node, the next time it is enabled, "Serial in" outputs each message twice or more times. The only way to stop it is to change some configurations in "Serial Port" Configuration node and restart the flow. |
Could be event handlers not being removed or being (re)added a second, third time upon re-connection. @syoma755 Would you confirm something please?
That would help us investigate the issue. |
Hi Steve Just tried to reproduce it. Sequence 1:
Sequence 2:
Please note that also after disabling and enabling the serial port in Sequence two, I'm sometimes also get duplicated messages, but can not reproduce it reliably. Usually if 'serial in' becomes grey - not connected, after port enabling (even if node-red console shows that COM is connected), I will get duplicated messages. Especially if some other program was using this serial port in between. Hope it helps to debug the issue.Let me know if |
Which node are you reporting an issue on?
node-red-node-serialport serial control node
What are the steps to reproduce?
Just send enable two or more times to control node
What happens?
All serial nodes that have output and are configured for the same port will emit multiple same messages according to number of issued enables
What do you expect to happen?
I expect to emit the unique message only one time
I've tried it with usb serial and with native rs232, both same behaviour.
The text was updated successfully, but these errors were encountered: