-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
TCP in Node auto respons [72,67,202,1,1,...] #4139
Comments
Whatever device is on the end of Therefore the TCP node is working as expected. If you need help using node-red, please head to the forum or slack as was displayed when you raised this issue. Thanks, Steve. |
Closing issue. Please re-open or comment if you still believe this to be a Node-RED problem. |
Thank you for your reply. But I still can't got the point. As you see, The node TCP:28001 IS the device that the next node tcp:iot.mapchant.com:28001 (same as tcp:localhost:28001) ,connected to. And the data is send out by the tcp in node (TCP:28001) . But as you see, The Node TCP:28001 send nothing in the function node. But the Node(tcp:iot.mapchang.com:28001) received these data. So why TCP:28001 send these data internally? |
But the tcp node that is only connected to the debug node is NOT connecting to the tcp-in -> function -> tcp-out flow. This can be seen because there is not "connected 1" status under the tcp-in node. This means that If you change the hostname in the bottom tcp node to localhost you should see the connection and no data being sent |
Current Behavior
And if I connect to tcp in node, It‘s will send back some bytes to client. But these data not from my configs.
Expected Behavior
Client do not receive any data when not send data by hand.
Steps To Reproduce
use this config, and node debug68 will receive these bytes repeatedly.
Example flow
Environment
The text was updated successfully, but these errors were encountered: