Node-red-modbus flex getter does not reconnect

[keshavvasudeva]

Continuing the discussion from Node-red-contrib-modbus no reconnect:

@larslehman1

n fail for 1 to 2 hours at any time.
After a short time the Modbus client should try to establish a connection to the device. After the reconnect timer has expired, I only get a con

I have downgraded to v12.13 as mentioned in the above thread but I am still facing the issue. I have attached a picture of my flow for reference. I am using 4 solos which are connected to the same rs485.

let me know what you guys think.

[UnborN]

@keshavvasudeva

I have downgraded to v12.13

I think there was no need to downgrade to Node js v12 since the issue described it that older thread has now been fixed in the newer versions of the Modbus nodes (see Github)

@keshavvasudeva

I am using 4 solos which are connected to the same rs485.

.. and i believe that issue was only affecting Modbus TCP connections and not Serial.

Its impossible from a screenshot to understand what could be the problem
Can you share your Flow and tell us some details about the devices ?