I update node.js to v24 and NodeRed to v5.0.4 and after this upgrade my flow with 3 modbus nodes (1 modbus-read and 2 modbus-getter) worked fine.
After upgrading the node-red-contrib-modbus from 5.45.2 to 5.60.1 my modbus-read and modbus-getter stopped sending data. The nodes enter in a cycle of disconnection & reconnecting. Sometime it would come alive, often, but not always if I opened one of the nodes or edited the Modbus Server config in the node.
I solved the issue be rolling back to 5.45.2 so can't debug further.
Any ideas of what could be cause the issue?
Version 5.60.2 was just released fixing some reconnection issues.
Upgraded to 5.60.2 and the issue remains. it seems to be the modbus-read node that is not giving any data. The modbus-getter node I have works fine.
Solved it by changing my only modbus-read node to a modbus-getter node triggered by an inject node. Actually better for me as I now have better control of the exact time when it is triggered
