Troubles with Modbus

Hello -

I am currently in the process of migrating from OpenHAB. Main reason for migrating is that i am after more control over dashboards, values and incorporating some of my security cameras into the dashboards, etc… So far i have been kicking tires on a few core integrations, that i use daily here at home. With my openHAB configuration I use several R421a08 Relay modules that i have configured to work via MQTT to python app on a Rpi that then sends the commands to the modules via serial rs485. Now my HA instance is HASSos running via proxmox, i would rather not use serial pass through in proxmox with a usbRS485 dongle so i have acquired a POE Lantronix UDS 1100 through work. I currently have it functioning but with some undesirable results. Any help or guidance would be much appreciated. I would like to levarage this configuration rather than reverting to a middleware like i have in My Openhab instance. So any help or guidance would be much appreciated.

from dashboard i hit the toggle on the right, the relay on the Relay Module activates. But then goes grey.

image

I then have to click on the switch icon to pull up the visual switch, i have to turn it on, it then goes unavailable for about 3-5 seconds, then show it is on mirroring the actual state of the relay, i then can turn it off where it again becomes unavailable to control for 3-5seconds.

modbus:
  - type: rtuovertcp
    host: 192.168.10.10
    port: 3001
    delay: .1
    timeout: .1
    switches:
      - name: 00_rly01
        slave: 1
        address: 1
        command_on: 256
        command_off: 512
      - name: 00_rly02
        slave: 1
        address: 2
        command_on: 256
        command_off: 512
      - name: 01_rly01
        slave: 2
        address: 1
        command_on: 256
        command_off: 512

Verify option maybe

# Example configuration.yaml entry
modbus:
  - type: tcp
    host: IP_ADDRESS
    port: 502
    fans:
      - name: "Fan1"
        address: 13
        write_type: coil
      - name: "Fan2"
        slave: 2
        address: 14
        write_type: coil
        verify:
      - name: "Register1"
        address: 11
        command_on: 1
        command_off: 0
        verify:
            input_type: holding
            address: 127
            state_on: 25
            state_off: 1

tried the verify option, i can now see it polls via the log. but i get this


also the switch status is now permanently unavailable with verify option added.