MODBUS integration wont reconnect to TCP-485 server after power outage (sever reboot)

Does anyone have any experience with reconnecting HA modbus integration to a TCP-serial converter after converter’s reboot and connection to a server was lost?

The explication:
HA is running on a NUC powered with UPS, serial devices connected to an interface of TCP-serial converter. If converter is on, while boot HA establishes a connection to TCP-serial converter which results in a record in converter’s log, that HA ip is connected to converters server. If the power goes off, a TCP-serial converter reboots into state ‘server ready’, naturally all previous connections are lost. And now comes the problem - HA does not attempt to reestablish a connection to a TCP-serial converter. I have to call homeassistant.reboot service to do so. Is there any setup to make HA reconnect (reopen a port maybe) so I would not have to reboot whole system because of TCP-serial power failure?

Thanks!

I am having a similar issue. I have Modbus/TCP data coming in that I’m using to create a sensor. When the remote device loses power momentarily, Home Assistant doesn’t re-connect. I get an error that the sensor is unavailable and I have to restart Home Assistant.

Any fix available? Code below.

modbus:
  - type: tcp
    host: 10.10.21.53
    port: 502
    name: rio_sump
    close_comm_on_error: false
    retry_on_empty: true
    retries: 10
    sensors:
    - name: sumplevel
      slave: 1
      address: 8
      unit_of_measurement: in
      scale: 0.006444
      offset: -4.302096
      precision: 3