search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.3k stars 30.61k forks source link

Lost Modbus Sensor after upgrade to Core 2024.3 #112607

Closed phoinixgrr closed 7 months ago

phoinixgrr commented 8 months ago

The problem

Using Modbus, to control my Lg Therma Heat pump. After the update to Core 2024.3. I Seem to be experiencing some issues with reading specifically the following sensor:

      - name: "lg_therma_outlet_temp"
        unique_id: "lg_therma_outlet_temp"
        scan_interval: 10
        address: 3
        slave: 1
        input_type: input
        scale: 0.1
        device_class: temperature
        unit_of_measurement: "°C"
        precision: 1

Here is the whole configuration 

 modbus:
  - name: "Heat Pump - LG Therma V"
    delay: 1
    timeout: 14
    message_wait_milliseconds: 200
    host: pump.home
    port: 8899
    type: tcp
    binary_sensors:
      - name: "lg_therma_heating_mode"
        address: 0
        scan_interval: 60
        slave: 1
        input_type: coil
      - name: "lg_therma_flow_too_low"
        address: 0
        scan_interval: 60
        slave: 1
        input_type: discrete_input
      - name: "lg_therma_pump_status"
        address: 1
        scan_interval: 10
        slave: 1
        input_type: discrete_input
        device_class: running
      - name: "lg_therma_compressor_status"
        address: 3
        scan_interval: 10
        slave: 1
        input_type: discrete_input
        device_class: running
      - name: "lg_therma_defrost_status"
        address: 4
        scan_interval: 60
        slave: 1
        input_type: discrete_input
        device_class: running
      - name: "lg_therma_dhw_status"
        address: 5
        scan_interval: 60
        slave: 1
        input_type: discrete_input
        device_class: running
      - name: "lg_therma_disinfect_status"
        address: 6
        scan_interval: 60
        slave: 1
        input_type: discrete_input
        device_class: running
      - name: "lg_therma_silent_status"
        address: 7
        scan_interval: 10
        slave: 1
        input_type: discrete_input
      - name: "lg_therma_error_status"
        address: 13
        scan_interval: 60
        slave: 1
        input_type: discrete_input
        device_class: problem
    sensors:
      - name: "lg_therma_outlet_temp"
        unique_id: "lg_therma_outlet_temp"
        scan_interval: 10
        address: 3
        slave: 1
        input_type: input
        scale: 0.1
        device_class: temperature
        unit_of_measurement: "°C"
        precision: 1
      - name: "lg_therma_inlet_temp"
        unique_id: "lg_therma_inlet_temp"
        scan_interval: 10
        address: 2
        slave: 1
        input_type: input
        scale: 0.1
        device_class: temperature
        unit_of_measurement: "°C"
        precision: 1
      - name: "lg_therma_flow_rate"
        unique_id: "lg_therma_flow_rate"
        scan_interval: 10
        address: 8
        slave: 1
        input_type: input
        scale: 0.1
        unit_of_measurement: "l/min"
        precision: 1
        zero_suppress: 5
      - name: "lg_therma_outdoor_air_temp"
        unique_id: "lg_therma_outdoor_air_temp"
        scan_interval: 10
        address: 12
        slave: 1
        input_type: input
        scale: 0.1
        device_class: temperature
        unit_of_measurement: "°C"
        precision: 1
      - name: "lg_therma_compressor_rpm"
        unique_id: "lg_therma_compressor_rpm"
        scale: 60
        precision: 0.1
        scan_interval: 10
        address: 24
        slave: 1
        unit_of_measurement: rpm
        input_type: input
      - name: "lg_therma_evaporator_pressure" # Dampfdruck Kondensator
        unique_id: "lg_therma_evaporator_pressure"
        address: 22
        scan_interval: 60
        unit_of_measurement: Bar
        slave: 1
        input_type: input
      - name: "lg_therma_compressor_pressure" # Dampfdruck Verdampfer
        unique_id: "lg_therma_compressor_pressure"
        address: 23
        scan_interval: 60
        unit_of_measurement: Bar
        slave: 1
        input_type: input

    switches:
      - name: "lg_therma_power"
        slave: 1
        address: 0
        write_type: coil
        command_on: 1
        command_off: 0
        verify:
          input_type: coil
          address: 0
          state_on: 1
          state_off: 0
      - name: "lg_therma_silent_mode"
        slave: 1
        address: 2
        write_type: coil
        command_on: 1
        command_off: 0
        verify:
          input_type: coil
          address: 2
          state_on: 1
          state_off: 0
    climates:
      - name: "lg_therma_climate_control"
        address: 3
        slave: 1
        input_type: input
        max_temp: 50
        min_temp: 15
        offset: 0
        precision: 1
        scale: 0.1
        target_temp_register: 2
        temp_step: 1
        temperature_unit: C
          #hvac_onoff_register: 0
        write_registers: true
        hvac_mode_register:
          address: 0
          values:
            state_cool: 0
            state_heat: 4

The entity lg_therma_outlet_temp is reported as Unavailable. No other changes introduced except upgrading to Core 2024.3.

What version of Home Assistant Core has the issue?

core-2024.3.0

What was the last working version of Home Assistant Core?

core-2024.2.5

What type of installation are you running?

Home Assistant OS

Integration causing the issue

modbus

Link to integration documentation on our website

https://www.home-assistant.io/integrations/modbus/

Diagnostics information

2024-03-07 14:57:35.015 DEBUG (SyncWorker_9) [pymodbus.logging] New Transaction state "SENDING"
2024-03-07 14:57:35.016 DEBUG (SyncWorker_9) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-03-07 14:57:35.104 DEBUG (SyncWorker_9) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-03-07 14:57:35.104 DEBUG (SyncWorker_9) [pymodbus.logging] RECV: 0x2 0x8b 0x0 0x0 0x0 0x4 0x1 0x2 0x1 0x0
2024-03-07 14:57:35.105 DEBUG (SyncWorker_9) [pymodbus.logging] Processing: 0x2 0x8b 0x0 0x0 0x0 0x4 0x1 0x2 0x1 0x0
2024-03-07 14:57:35.105 DEBUG (SyncWorker_9) [pymodbus.logging] Factory Response[ReadDiscreteInputsResponse': 2]
2024-03-07 14:57:35.105 DEBUG (SyncWorker_9) [pymodbus.logging] Adding transaction 651
2024-03-07 14:57:35.106 DEBUG (SyncWorker_9) [pymodbus.logging] Frame check failed, ignoring!!
2024-03-07 14:57:35.106 DEBUG (SyncWorker_9) [pymodbus.logging] Getting transaction 651
2024-03-07 14:57:35.106 DEBUG (SyncWorker_9) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-03-07 14:57:35.311 DEBUG (SyncWorker_11) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-03-07 14:57:35.311 DEBUG (SyncWorker_11) [pymodbus.logging] Running transaction 652
2024-03-07 14:57:35.311 DEBUG (SyncWorker_11) [pymodbus.logging] SEND: 0x2 0x8c 0x0 0x0 0x0 0x6 0x1 0x4 0x0 0x2 0x0 0x1
2024-03-07 14:57:35.312 DEBUG (SyncWorker_11) [pymodbus.logging] New Transaction state "SENDING"
2024-03-07 14:57:35.312 DEBUG (SyncWorker_11) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-03-07 14:57:35.385 DEBUG (SyncWorker_11) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-03-07 14:57:35.385 DEBUG (SyncWorker_11) [pymodbus.logging] RECV: 0x2 0x8c 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x0 0xbf
2024-03-07 14:57:35.385 DEBUG (SyncWorker_11) [pymodbus.logging] Processing: 0x2 0x8c 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x0 0xbf
2024-03-07 14:57:35.386 DEBUG (SyncWorker_11) [pymodbus.logging] Factory Response[ReadInputRegistersResponse': 4]
2024-03-07 14:57:35.386 DEBUG (SyncWorker_11) [pymodbus.logging] Adding transaction 652
2024-03-07 14:57:35.386 DEBUG (SyncWorker_11) [pymodbus.logging] Frame check failed, ignoring!!
2024-03-07 14:57:35.386 DEBUG (SyncWorker_11) [pymodbus.logging] Getting transaction 652
2024-03-07 14:57:35.387 DEBUG (SyncWorker_11) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-03-07 14:57:35.590 DEBUG (SyncWorker_16) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-03-07 14:57:35.590 DEBUG (SyncWorker_16) [pymodbus.logging] Running transaction 653
2024-03-07 14:57:35.591 DEBUG (SyncWorker_16) [pymodbus.logging] SEND: 0x2 0x8d 0x0 0x0 0x0 0x6 0x1 0x4 0x0 0x8 0x0 0x1
2024-03-07 14:57:35.591 DEBUG (SyncWorker_16) [pymodbus.logging] New Transaction state "SENDING"
2024-03-07 14:57:35.592 DEBUG (SyncWorker_16) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-03-07 14:57:35.664 DEBUG (SyncWorker_16) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-03-07 14:57:35.665 DEBUG (SyncWorker_16) [pymodbus.logging] RECV: 0x2 0x8d 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x0 0x32
2024-03-07 14:57:35.666 DEBUG (SyncWorker_16) [pymodbus.logging] Processing: 0x2 0x8d 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x0 0x32
2024-03-07 14:57:35.667 DEBUG (SyncWorker_16) [pymodbus.logging] Factory Response[ReadInputRegistersResponse': 4]
2024-03-07 14:57:35.667 DEBUG (SyncWorker_16) [pymodbus.logging] Adding transaction 653
2024-03-07 14:57:35.667 DEBUG (SyncWorker_16) [pymodbus.logging] Frame check failed, ignoring!!
2024-03-07 14:57:35.667 DEBUG (SyncWorker_16) [pymodbus.logging] Getting transaction 653
2024-03-07 14:57:35.668 DEBUG (SyncWorker_16) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-03-07 14:57:35.889 DEBUG (SyncWorker_1) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-03-07 14:57:35.889 DEBUG (SyncWorker_1) [pymodbus.logging] Running transaction 654
2024-03-07 14:57:35.890 DEBUG (SyncWorker_1) [pymodbus.logging] SEND: 0x2 0x8e 0x0 0x0 0x0 0x6 0x1 0x4 0x0 0xc 0x0 0x1
2024-03-07 14:57:35.890 DEBUG (SyncWorker_1) [pymodbus.logging] New Transaction state "SENDING"
2024-03-07 14:57:35.890 DEBUG (SyncWorker_1) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-03-07 14:57:35.964 DEBUG (SyncWorker_1) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-03-07 14:57:35.964 DEBUG (SyncWorker_1) [pymodbus.logging] RECV: 0x2 0x8e 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x0 0xb9
2024-03-07 14:57:35.965 DEBUG (SyncWorker_1) [pymodbus.logging] Processing: 0x2 0x8e 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x0 0xb9
2024-03-07 14:57:35.965 DEBUG (SyncWorker_1) [pymodbus.logging] Factory Response[ReadInputRegistersResponse': 4]
2024-03-07 14:57:35.965 DEBUG (SyncWorker_1) [pymodbus.logging] Adding transaction 654
2024-03-07 14:57:35.966 DEBUG (SyncWorker_1) [pymodbus.logging] Frame check failed, ignoring!!
2024-03-07 14:57:35.966 DEBUG (SyncWorker_1) [pymodbus.logging] Getting transaction 654
2024-03-07 14:57:35.966 DEBUG (SyncWorker_1) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-03-07 14:57:36.169 DEBUG (SyncWorker_20) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-03-07 14:57:36.170 DEBUG (SyncWorker_20) [pymodbus.logging] Running transaction 655
2024-03-07 14:57:36.170 DEBUG (SyncWorker_20) [pymodbus.logging] SEND: 0x2 0x8f 0x0 0x0 0x0 0x6 0x1 0x4 0x0 0x18 0x0 0x1
2024-03-07 14:57:36.170 DEBUG (SyncWorker_20) [pymodbus.logging] New Transaction state "SENDING"
2024-03-07 14:57:36.171 DEBUG (SyncWorker_20) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-03-07 14:57:36.244 DEBUG (SyncWorker_20) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-03-07 14:57:36.244 DEBUG (SyncWorker_20) [pymodbus.logging] RECV: 0x2 0x8f 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x0 0x0
2024-03-07 14:57:36.245 DEBUG (SyncWorker_20) [pymodbus.logging] Processing: 0x2 0x8f 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x0 0x0
2024-03-07 14:57:36.245 DEBUG (SyncWorker_20) [pymodbus.logging] Factory Response[ReadInputRegistersResponse': 4]
2024-03-07 14:57:36.245 DEBUG (SyncWorker_20) [pymodbus.logging] Adding transaction 655
2024-03-07 14:57:36.246 DEBUG (SyncWorker_20) [pymodbus.logging] Frame check failed, ignoring!!
2024-03-07 14:57:36.246 DEBUG (SyncWorker_20) [pymodbus.logging] Getting transaction 655
2024-03-07 14:57:36.246 DEBUG (SyncWorker_20) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-03-07 14:57:36.452 DEBUG (SyncWorker_7) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-03-07 14:57:36.452 DEBUG (SyncWorker_7) [pymodbus.logging] Running transaction 656
2024-03-07 14:57:36.452 DEBUG (SyncWorker_7) [pymodbus.logging] SEND: 0x2 0x90 0x0 0x0 0x0 0x6 0x1 0x4 0x0 0x3 0x0 0x1
2024-03-07 14:57:36.453 DEBUG (SyncWorker_7) [pymodbus.logging] New Transaction state "SENDING"
2024-03-07 14:57:36.453 DEBUG (SyncWorker_7) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-03-07 14:57:36.534 DEBUG (SyncWorker_7) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-03-07 14:57:36.535 DEBUG (SyncWorker_7) [pymodbus.logging] RECV: 0x2 0x90 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x0 0xbf
2024-03-07 14:57:36.535 DEBUG (SyncWorker_7) [pymodbus.logging] Processing: 0x2 0x90 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x0 0xbf
2024-03-07 14:57:36.536 DEBUG (SyncWorker_7) [pymodbus.logging] Factory Response[ReadInputRegistersResponse': 4]
2024-03-07 14:57:36.536 DEBUG (SyncWorker_7) [pymodbus.logging] Adding transaction 656
2024-03-07 14:57:36.536 DEBUG (SyncWorker_7) [pymodbus.logging] Frame check failed, ignoring!!
2024-03-07 14:57:36.537 DEBUG (SyncWorker_7) [pymodbus.logging] Getting transaction 656
2024-03-07 14:57:36.537 DEBUG (SyncWorker_7) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-03-07 14:57:36.741 DEBUG (SyncWorker_5) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-03-07 14:57:36.742 DEBUG (SyncWorker_5) [pymodbus.logging] Running transaction 657
2024-03-07 14:57:36.742 DEBUG (SyncWorker_5) [pymodbus.logging] SEND: 0x2 0x91 0x0 0x0 0x0 0x6 0x1 0x3 0x0 0x0 0x0 0x1
2024-03-07 14:57:36.742 DEBUG (SyncWorker_5) [pymodbus.logging] New Transaction state "SENDING"
2024-03-07 14:57:36.743 DEBUG (SyncWorker_5) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-03-07 14:57:36.814 DEBUG (SyncWorker_5) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-03-07 14:57:36.815 DEBUG (SyncWorker_5) [pymodbus.logging] RECV: 0x2 0x91 0x0 0x0 0x0 0x5 0x1 0x3 0x2 0x0 0x4
2024-03-07 14:57:36.815 DEBUG (SyncWorker_5) [pymodbus.logging] Processing: 0x2 0x91 0x0 0x0 0x0 0x5 0x1 0x3 0x2 0x0 0x4
2024-03-07 14:57:36.815 DEBUG (SyncWorker_5) [pymodbus.logging] Factory Response[ReadHoldingRegistersResponse': 3]
2024-03-07 14:57:36.816 DEBUG (SyncWorker_5) [pymodbus.logging] Adding transaction 657
2024-03-07 14:57:36.816 DEBUG (SyncWorker_5) [pymodbus.logging] Frame check failed, ignoring!!
2024-03-07 14:57:36.816 DEBUG (SyncWorker_5) [pymodbus.logging] Getting transaction 657
2024-03-07 14:57:36.816 DEBUG (SyncWorker_5) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-03-07 14:57:43.737 DEBUG (SyncWorker_3) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-03-07 14:57:43.737 DEBUG (SyncWorker_3) [pymodbus.logging] Running transaction 658
2024-03-07 14:57:43.737 DEBUG (SyncWorker_3) [pymodbus.logging] SEND: 0x2 0x92 0x0 0x0 0x0 0x6 0x1 0x2 0x0 0x1 0x0 0x1
2024-03-07 14:57:43.738 DEBUG (SyncWorker_3) [pymodbus.logging] New Transaction state "SENDING"
2024-03-07 14:57:43.738 DEBUG (SyncWorker_3) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-03-07 14:57:43.814 DEBUG (SyncWorker_3) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-03-07 14:57:43.815 DEBUG (SyncWorker_3) [pymodbus.logging] RECV: 0x2 0x92 0x0 0x0 0x0 0x4 0x1 0x2 0x1 0x0
2024-03-07 14:57:43.815 DEBUG (SyncWorker_3) [pymodbus.logging] Processing: 0x2 0x92 0x0 0x0 0x0 0x4 0x1 0x2 0x1 0x0
2024-03-07 14:57:43.816 DEBUG (SyncWorker_3) [pymodbus.logging] Factory Response[ReadDiscreteInputsResponse': 2]
2024-03-07 14:57:43.816 DEBUG (SyncWorker_3) [pymodbus.logging] Adding transaction 658
2024-03-07 14:57:43.816 DEBUG (SyncWorker_3) [pymodbus.logging] Frame check failed, ignoring!!
2024-03-07 14:57:43.816 DEBUG (SyncWorker_3) [pymodbus.logging] Getting transaction 658
2024-03-07 14:57:43.816 DEBUG (SyncWorker_3) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-03-07 14:57:44.023 DEBUG (SyncWorker_6) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-03-07 14:57:44.023 DEBUG (SyncWorker_6) [pymodbus.logging] Running transaction 659
2024-03-07 14:57:44.024 DEBUG (SyncWorker_6) [pymodbus.logging] SEND: 0x2 0x93 0x0 0x0 0x0 0x6 0x1 0x2 0x0 0x3 0x0 0x1
2024-03-07 14:57:44.024 DEBUG (SyncWorker_6) [pymodbus.logging] New Transaction state "SENDING"
2024-03-07 14:57:44.024 DEBUG (SyncWorker_6) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-03-07 14:57:44.094 DEBUG (SyncWorker_6) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-03-07 14:57:44.095 DEBUG (SyncWorker_6) [pymodbus.logging] RECV: 0x2 0x93 0x0 0x0 0x0 0x4 0x1 0x2 0x1 0x0
2024-03-07 14:57:44.095 DEBUG (SyncWorker_6) [pymodbus.logging] Processing: 0x2 0x93 0x0 0x0 0x0 0x4 0x1 0x2 0x1 0x0
2024-03-07 14:57:44.095 DEBUG (SyncWorker_6) [pymodbus.logging] Factory Response[ReadDiscreteInputsResponse': 2]
2024-03-07 14:57:44.095 DEBUG (SyncWorker_6) [pymodbus.logging] Adding transaction 659
2024-03-07 14:57:44.096 DEBUG (SyncWorker_6) [pymodbus.logging] Frame check failed, ignoring!!
2024-03-07 14:57:44.096 DEBUG (SyncWorker_6) [pymodbus.logging] Getting transaction 659
2024-03-07 14:57:44.096 DEBUG (SyncWorker_6) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-03-07 14:57:44.300 DEBUG (SyncWorker_17) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-03-07 14:57:44.301 DEBUG (SyncWorker_17) [pymodbus.logging] Running transaction 660
2024-03-07 14:57:44.301 DEBUG (SyncWorker_17) [pymodbus.logging] SEND: 0x2 0x94 0x0 0x0 0x0 0x6 0x1 0x2 0x0 0x7 0x0 0x1
2024-03-07 14:57:44.301 DEBUG (SyncWorker_17) [pymodbus.logging] New Transaction state "SENDING"
2024-03-07 14:57:44.302 DEBUG (SyncWorker_17) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-03-07 14:57:44.374 DEBUG (SyncWorker_17) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-03-07 14:57:44.375 DEBUG (SyncWorker_17) [pymodbus.logging] RECV: 0x2 0x94 0x0 0x0 0x0 0x4 0x1 0x2 0x1 0x0
2024-03-07 14:57:44.375 DEBUG (SyncWorker_17) [pymodbus.logging] Processing: 0x2 0x94 0x0 0x0 0x0 0x4 0x1 0x2 0x1 0x0
2024-03-07 14:57:44.375 DEBUG (SyncWorker_17) [pymodbus.logging] Factory Response[ReadDiscreteInputsResponse': 2]
2024-03-07 14:57:44.376 DEBUG (SyncWorker_17) [pymodbus.logging] Adding transaction 660
2024-03-07 14:57:44.376 DEBUG (SyncWorker_17) [pymodbus.logging] Frame check failed, ignoring!!
2024-03-07 14:57:44.376 DEBUG (SyncWorker_17) [pymodbus.logging] Getting transaction 660
2024-03-07 14:57:44.376 DEBUG (SyncWorker_17) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-03-07 14:57:44.582 DEBUG (SyncWorker_2) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-03-07 14:57:44.583 DEBUG (SyncWorker_2) [pymodbus.logging] Running transaction 661
2024-03-07 14:57:44.583 DEBUG (SyncWorker_2) [pymodbus.logging] SEND: 0x2 0x95 0x0 0x0 0x0 0x6 0x1 0x4 0x0 0x2 0x0 0x1
2024-03-07 14:57:44.583 DEBUG (SyncWorker_2) [pymodbus.logging] New Transaction state "SENDING"
2024-03-07 14:57:44.584 DEBUG (SyncWorker_2) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-03-07 14:57:44.654 DEBUG (SyncWorker_2) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-03-07 14:57:44.655 DEBUG (SyncWorker_2) [pymodbus.logging] RECV: 0x2 0x95 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x0 0xbf
2024-03-07 14:57:44.655 DEBUG (SyncWorker_2) [pymodbus.logging] Processing: 0x2 0x95 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x0 0xbf
2024-03-07 14:57:44.655 DEBUG (SyncWorker_2) [pymodbus.logging] Factory Response[ReadInputRegistersResponse': 4]
2024-03-07 14:57:44.656 DEBUG (SyncWorker_2) [pymodbus.logging] Adding transaction 661
2024-03-07 14:57:44.656 DEBUG (SyncWorker_2) [pymodbus.logging] Frame check failed, ignoring!!
2024-03-07 14:57:44.656 DEBUG (SyncWorker_2) [pymodbus.logging] Getting transaction 661
2024-03-07 14:57:44.656 DEBUG (SyncWorker_2) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-03-07 14:57:44.862 DEBUG (SyncWorker_9) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-03-07 14:57:44.862 DEBUG (SyncWorker_9) [pymodbus.logging] Running transaction 662
2024-03-07 14:57:44.863 DEBUG (SyncWorker_9) [pymodbus.logging] SEND: 0x2 0x96 0x0 0x0 0x0 0x6 0x1 0x4 0x0 0x8 0x0 0x1
2024-03-07 14:57:44.863 DEBUG (SyncWorker_9) [pymodbus.logging] New Transaction state "SENDING"
2024-03-07 14:57:44.863 DEBUG (SyncWorker_9) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-03-07 14:57:44.934 DEBUG (SyncWorker_9) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-03-07 14:57:44.935 DEBUG (SyncWorker_9) [pymodbus.logging] RECV: 0x2 0x96 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x0 0x32
2024-03-07 14:57:44.935 DEBUG (SyncWorker_9) [pymodbus.logging] Processing: 0x2 0x96 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x0 0x32
2024-03-07 14:57:44.935 DEBUG (SyncWorker_9) [pymodbus.logging] Factory Response[ReadInputRegistersResponse': 4]
2024-03-07 14:57:44.935 DEBUG (SyncWorker_9) [pymodbus.logging] Adding transaction 662
2024-03-07 14:57:44.936 DEBUG (SyncWorker_9) [pymodbus.logging] Frame check failed, ignoring!!
2024-03-07 14:57:44.936 DEBUG (SyncWorker_9) [pymodbus.logging] Getting transaction 662
2024-03-07 14:57:44.936 DEBUG (SyncWorker_9) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-03-07 14:57:45.140 DEBUG (SyncWorker_11) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-03-07 14:57:45.141 DEBUG (SyncWorker_11) [pymodbus.logging] Running transaction 663
2024-03-07 14:57:45.141 DEBUG (SyncWorker_11) [pymodbus.logging] SEND: 0x2 0x97 0x0 0x0 0x0 0x6 0x1 0x4 0x0 0xc 0x0 0x1
2024-03-07 14:57:45.142 DEBUG (SyncWorker_11) [pymodbus.logging] New Transaction state "SENDING"
2024-03-07 14:57:45.144 DEBUG (SyncWorker_11) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-03-07 14:57:45.224 DEBUG (SyncWorker_11) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-03-07 14:57:45.225 DEBUG (SyncWorker_11) [pymodbus.logging] RECV: 0x2 0x97 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x0 0xb9
2024-03-07 14:57:45.226 DEBUG (SyncWorker_11) [pymodbus.logging] Processing: 0x2 0x97 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x0 0xb9
2024-03-07 14:57:45.226 DEBUG (SyncWorker_11) [pymodbus.logging] Factory Response[ReadInputRegistersResponse': 4]
2024-03-07 14:57:45.226 DEBUG (SyncWorker_11) [pymodbus.logging] Adding transaction 663
2024-03-07 14:57:45.226 DEBUG (SyncWorker_11) [pymodbus.logging] Frame check failed, ignoring!!
2024-03-07 14:57:45.227 DEBUG (SyncWorker_11) [pymodbus.logging] Getting transaction 663
2024-03-07 14:57:45.228 DEBUG (SyncWorker_11) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-03-07 14:57:45.434 DEBUG (SyncWorker_16) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-03-07 14:57:45.435 DEBUG (SyncWorker_16) [pymodbus.logging] Running transaction 664
2024-03-07 14:57:45.435 DEBUG (SyncWorker_16) [pymodbus.logging] SEND: 0x2 0x98 0x0 0x0 0x0 0x6 0x1 0x4 0x0 0x18 0x0 0x1
2024-03-07 14:57:45.436 DEBUG (SyncWorker_16) [pymodbus.logging] New Transaction state "SENDING"
2024-03-07 14:57:45.438 DEBUG (SyncWorker_16) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-03-07 14:57:45.526 DEBUG (SyncWorker_16) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-03-07 14:57:45.526 DEBUG (SyncWorker_16) [pymodbus.logging] RECV: 0x2 0x98 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x0 0x0
2024-03-07 14:57:45.527 DEBUG (SyncWorker_16) [pymodbus.logging] Processing: 0x2 0x98 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x0 0x0
2024-03-07 14:57:45.527 DEBUG (SyncWorker_16) [pymodbus.logging] Factory Response[ReadInputRegistersResponse': 4]
2024-03-07 14:57:45.527 DEBUG (SyncWorker_16) [pymodbus.logging] Adding transaction 664
2024-03-07 14:57:45.528 DEBUG (SyncWorker_16) [pymodbus.logging] Frame check failed, ignoring!!
2024-03-07 14:57:45.528 DEBUG (SyncWorker_16) [pymodbus.logging] Getting transaction 664
2024-03-07 14:57:45.528 DEBUG (SyncWorker_16) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

janiversen commented 7 months ago

But if it works for you then all is good...I was just noting that this does not work as a general solution.

vwtuner commented 7 months ago

👍

MrNorm commented 7 months ago

All of the information in this thread helped me massively. Thanks all