I've to add a Tcp Server and send data received to a mqtt remote client.
My problem is that if the broker is down i've to stop the Tcp listener (the tcp client have an internal cache if no listener is up). I've used the default Tcp server, but it has only static configuration. there is a tcp-server-dynamic but it seems to not work properly, i can start but not stop and then if i start again it tell me that there is already a listening process on port 35000 (my port).
have you some tips ?
I've seen that there is no way to disable a node by code.
Can I ask why?
Cant you simply use the MQTT nodes to send and receive data from the remote MQTT client?
The MQTT nodes will automatically re-connect after the network is "up".
Additionally, you can action the MQTT nodes to "disconnect" and "connect" at runtime.
in my project i've a device that send via tcp data, i use node-red as a gateway, so i read the tcp data, serialize on json message and send i by mqtt connection. If the broker is down i've to close the tcp listener in order to use the local device's internal caching and when the broker is up i can start the tcp listener and the local device flush all data.
So i've to stop the tcp listener or i have to create in node-red a local caching.
It will be saved to disk every 30 seconds by default, but that can be adjusted in settings.js. It will also get saved if node red is shut down normally. The only time you would lose data is if node-red crashed or the power was cut so node-red did not shut down normally.