When I "Deploy" my Node-RED flow the modbustcp-read nodes don't reconnect.
They show "Initiating...." and then after about 2 minutes they show "Disconnected" but they never reconnect.
I am using a King Pigeon M230T 4 Analog input module.
The hardware device continues to show the "Link" lamp active.
If I reboot the PC it all starts up nicely.
If I node-red-stop, then node-red-start, it all starts up nicely.
If I disconnect then reconnect power to my hardware device while the modbustcp-read nodes show "Disconnected", it starts reading in about 3 seconds
If I disconnect then reconnect power to my hardware while the modbustcp-read nodes show "Initiating..." the status will eventually change to show "Disconnected" but never starts reading.
I have the Modbus reconnect time set to 3 seconds, but changing this doesn't seem to affect the fault sequence.
I have found that having different Poll Rates for read nodes causes another reason for the system not to reconnect.
Why does stop then start (and reboot) work, where "Deploy" doesn't?
Why does the "Initiating..." status stop it from reconnecting?
Why when "Initiating..." does it take so long to decide it is "Disconnected" but then still not reconnect?
This situation makes working on even a simple flow very tedious.
Any thoughts please?