Hi, I have some troubles with TCP requests. I'd like to send over TCP a flowContext variable with some string appended to it, and it seems I could be able to do that using JSONata in the inject node. Problem is, when I send a simple string from a inject node, I get without any problem the answer f…

You have provided no information that we can help you with, we would be guessing as to the strings you are sending. Possibly an example flow might be of help. You could look at using the template node to add strings to a flow context variable. Read the sidebar help text for the node to see how.

Hi ! Thank you for your answer, and very sorry for the lack of detailed information, I realize I sent the message a bit too quickly. Actually, I made my tests using one of the example flows from the TCP node . By playing again with it, I think that maybe my problem is the special caracters used i…

Maybe try \r as the delimiter instead of \n

The delimiter tells the tcp node that this is the end of the message, so it hold all received messages and once it receives the delimiter it then passes on all the messages received, that includes all messages without a delimiter and the final delimiter message.

thank you guys, will give it a try tomorrow and come back.

Hi there, I had a quick look today at work, but did not have time to work on it correctly. I've seen that the TCP request node was not set to close after specific character received, so might be the origin of the problem. What's still strange is that all inject nodes are first connected to a funct…

Hi all ! I keep working on it, but still have some weird connection problems to the TCP server. First, here is some info from the TCP server API : The message sequence of the protocol basically consists of commands sent from external devices / applications(hereinafter called clients), and respon…

Will queuing the inputs and only allowing new input once tcp responds work [{"id":"7f219818a234a3c6","type":"inject","z":"d1395164b4eec73e","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"eeeeee","payloadType":…

Works like a charm ! [image] Thank you so much PS : do you think that might introduce some kind of delay in the communication ? this example is 1 per second but I might something a bit faster for other commands..

Node-RED

Node-RED Forum

Problem with TCP requests

General

JeromeVISUALS 27 September 2023 15:51 10

Thank you very much, will give it a try

Topic		Replies	Views
Tcp request node, host/port via flow works only once General	20	6713	3 February 2019
JSON send to TCP General	5	325	15 July 2022
Tcp msg is reassigned to the next data before debug output General http-request , function-node , possible-bug	20	445	26 October 2023
String type difference General	11	534	9 March 2021
Tcp request node issue General	8	489	25 July 2022

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Problem with TCP requests

Related topics