In the meantime I have found out that the status node does not work either here. It shows the wrong state like the node-red admin UI. So, for me that is not a cosmetic one.
I have solved it for me now with the suggested fix Wolfgang has explained in this thread. It works but isn't very elegant to send a msg.host="" before next connect attempt.
Thus, my recommendation to the maintainer of the tcp request node is:
should be changed, so that it reconnects when a new msg.host/msg.port is received or disconnects if host/port will get "". The status information should be updated accordingly, so that the status node can really be used here to work with the current connection state of the tcp request node.
Anyway, thanks for your help!
