Modbus-Read works the first time, then stops working

[joseamirandavelez]

I have a flow with multiple modbus-read nodes that works the first time it executes, and then every node seems to stay connected (status says connected). They are set to execute every 1 minute. When it executes a second time, it gives me an PortNotOpenError error. I searched this forum and found several questions about this error, but none of them have a solution.

Some more info. This is getting info from a Midnite Classic 150 charge controller (solar).

[PPz]

I struggled a lot with modbus devices (plc's).
I'm mostly a beginner here, so my idea is just an idea. It worked for me, that's it.

I had several disconnections for unknown reasons too.

Instead of polling different adresses, I changed the way my poll works. I now poll an array of contiguous data and parse them. And I poll more often to avoid disconnections or errors and keep a steady flow.

I also added a status analyzer linked to a switch to restart the flow in case of errors.

How to restart flows automatically?

Dear all, We're encountering a situation whereby if we have loss of connectivity, a number of flows (namely websocket nodes) fail to reconnect, while I realise we could check the source for the problematic nodes and implement a reconnect mechanism, this isn't viable for number of nodes we use (longterm, yes). Is there a way to restart flows from within Node Red? This would not only be useful to overcome the above, but also for testing purposes... Failing that we're considering triggering a scr…