Modbus does not update coils status

1

Hey there,

Just manage to get the HASSOS working with my modbus after moving from raspbian to HASOS…

Now it is working but coils stauts is not being updated…
this is the new settings:

type: serial
  method: rtu
  port: /dev/ttyUSB0
  #port: /dev/serial/by-id/usb-Silicon_Labs_CP2104_USB_to_UART_Bridge_Controller_0133D18C-if00-port0
  baudrate: 9600
  stopbits: 1
  bytesize: 8
  parity: N
  timeout: 4
  #retry_on_empty: true
  #retries: 10
  message_wait_milliseconds: 100
  switches:
    - name: SW001
      slave: 3
      address: 0
      write_type: coil
    - name: SW002
      slave: 3
      address: 1
      write_type: coil
    - name: SW003
      slave: 3
      address: 2
      write_type: coil
    - name: SW004
      slave: 3
      address: 3
      write_type: coil
    - name: SW005
      slave: 3
      address: 4
      write_type: coil
    - name: SW006
      slave: 3
      address: 5
      write_type: coil
    - name: SW007
      slave: 3
      address: 6
      write_type: coil
    - name: SW008
      slave: 3
      address: 7
      write_type: coil

old: working with coils status but not in HASSOS

  - platform: modbus
    coils:
    #====================================Module #1=============================
   # First Floor
      - name: Switch01
        slave: 10 
        coil: 0
      - name: Switch02
        slave: 10 
        coil: 1
      - name: Switch03
        slave: 10
        coil: 2
      - name: Switch04
        slave: 10
        coil: 3

      - name: Switch05
        slave: 10
        coil: 4
      - name: Switch06
        slave: 10 
        coil: 5
      - name: Switch07
        slave: 10
        coil: 6
      - name: Switch08
        slave: 10
        coil: 7

any solution?

2

Something like this?

modbus:
  - name: hub1
    type: tcp
    host: IP_ADDRESS
    port: 502
    covers:
      - name: Door1
        slave: 1
        device_class: door
        scan_interval: 10
        coil: 1
        status_register: 1
        status_register_type: input
        state_opening: 1
        state_open: 2
        state_closing: 3
        state_closed: 4
3

this is cover while i have switches…

is this should cover both RTU and TCP IP?

4

Yes

# Example configuration.yaml entry
modbus:
  - type: tcp # your type rtu etc
    host: IP_ADDRESS
    port: 502

    switches:
      - name: Switch1
        address: 13
        write_type: coil
      - name: Switch2
        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
5 
      - name: Register1
        address: 11
        command_on: 1
        command_off: 0
        verify:
            input_type: holding
            address: 127
            state_on: 25
            state_off: 1

how should i use this section what is the purpose of the register ?
for switch i am using the same settings but mode is not updated…

6

so no one is using modbus here???

7

anyone can tell if syntax changed?

8

hey anyone can tell what happen to the modbus?

9

Trying again…