Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disconnecting one Modbus device disrupts the others #110013

Closed
yoch opened this issue Feb 8, 2024 · 9 comments · Fixed by #110017
Closed

Disconnecting one Modbus device disrupts the others #110013

yoch opened this issue Feb 8, 2024 · 9 comments · Fixed by #110017
Assignees

Comments

@yoch
Copy link

yoch commented Feb 8, 2024

The problem

Hi,

I'm using Modbus integration to control an RTU Relay in addition to a HVAC Thermostat.

When I unplug the thermostat, the switches set on the relay no longer work properly (this appears to be because the system is stuck waiting for responses from the thermostat).

This is quite annoying, is there a solution to this problem?

What version of Home Assistant Core has the issue?

2024.2.0

What was the last working version of Home Assistant Core?

No response

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

No response

Example YAML snippet

modbus:
  - name: modbus_hub
    type: serial
    port: /dev/ttyUSB0
    baudrate: 9600
    bytesize: 8
    method: rtu
    parity: N
    stopbits: 1
    delay: 0
    message_wait_milliseconds: 30
    timeout: 5

    switches:
      - name: Switch1
        slave: 1
        address: 0
        write_type: coil
      - name: Switch2
        slave: 1
        address: 1
        write_type: coil
      - name: Switch3
        slave: 1
        address: 2
        write_type: coil
      - name: Switch4
        slave: 1
        address: 3
        write_type: coil
      - name: Switch5
        slave: 1
        address: 4
        write_type: coil
      - name: Switch6
        slave: 1
        address: 5
        write_type: coil
      - name: Switch7
        slave: 1
        address: 6
        write_type: coil
      - name: Switch8
        slave: 1
        address: 7
        write_type: coil

    climates:
      - name: "BC103-4DM"
        unique_id: clim1
        data_type: uint16
        input_type: holding
        slave: 2
        address: 9
        fan_mode_register:
            address: 0
            values:
                state_fan_high: 0
                state_fan_medium: 1
                state_fan_low: 2
                state_fan_auto: 3
        hvac_mode_register:
            address: 1
            values:
                state_cool: 1
                state_heat: 2
                state_fan_only: 3
        hvac_onoff_register: 2
        target_temp_register: 3
        max_temp: 35
        min_temp: 5
        offset: 0
        precision: 1
        scale: 0.1
        temp_step: 0.5
        temperature_unit: C

logger:
  default: warning
  logs:
    homeassistant.components.modbus: debug

Anything in the logs that might be useful for us?

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/modbus/climate.py", line 367, in async_update
    self._attr_fan_mode = self._fan_mode_mapping_from_modbus[int(fan_mode)]
                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
KeyError: -1
2024-02-08 16:23:51.517 DEBUG (SyncWorker_1) [homeassistant.components.modbus.modbus] Pymodbus: modbus_hub: Error: device: 2 address: 3 -> Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
2024-02-08 16:24:04.683 DEBUG (SyncWorker_18) [homeassistant.components.modbus.modbus] Pymodbus: modbus_hub: Error: device: 2 address: 9 -> Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
2024-02-08 16:24:17.848 DEBUG (SyncWorker_15) [homeassistant.components.modbus.modbus] Pymodbus: modbus_hub: Error: device: 2 address: 3 -> Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
2024-02-08 16:24:31.016 DEBUG (SyncWorker_4) [homeassistant.components.modbus.modbus] Pymodbus: modbus_hub: Error: device: 2 address: 1 -> Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
2024-02-08 16:24:44.183 DEBUG (SyncWorker_7) [homeassistant.components.modbus.modbus] Pymodbus: modbus_hub: Error: device: 2 address: 3 -> Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
2024-02-08 16:24:57.351 DEBUG (SyncWorker_3) [homeassistant.components.modbus.modbus] Pymodbus: modbus_hub: Error: device: 2 address: 9 -> Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
2024-02-08 16:25:10.520 DEBUG (SyncWorker_1) [homeassistant.components.modbus.modbus] Pymodbus: modbus_hub: Error: device: 2 address: 3 -> Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
2024-02-08 16:25:23.686 DEBUG (SyncWorker_18) [homeassistant.components.modbus.modbus] Pymodbus: modbus_hub: Error: device: 2 address: 1 -> Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
2024-02-08 16:25:36.859 DEBUG (SyncWorker_15) [homeassistant.components.modbus.modbus] Pymodbus: modbus_hub: Error: device: 2 address: 9 -> Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
2024-02-08 16:25:50.029 DEBUG (SyncWorker_16) [homeassistant.components.modbus.modbus] Pymodbus: modbus_hub: Error: device: 2 address: 3 -> Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Feb 8, 2024

Hey there @janiversen, mind taking a look at this issue as it has been labeled with an integration (modbus) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of modbus can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign modbus Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


modbus documentation
modbus source
(message by IssueLinks)

@janiversen
Copy link
Member

Please with a debug log as pr modbus documentation so we can see what happens.

@janiversen
Copy link
Member

The traceback seems incomplete, but that might be the real problem...a debug log will show.

@yoch
Copy link
Author

yoch commented Feb 8, 2024

Here is a more complete log with pymodbus set to dbug.

2024-02-08 16:11:31.547 DEBUG (SyncWorker_22) [pymodbus.logging] Running transaction 596
2024-02-08 16:11:31.548 DEBUG (SyncWorker_22) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:11:31.548 DEBUG (SyncWorker_22) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:11:31.548 DEBUG (SyncWorker_22) [pymodbus.logging] Changing state to IDLE - Last Frame End - None Current Time stamp - 1707401491.548693
2024-02-08 16:11:31.553 DEBUG (SyncWorker_22) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:11:31.554 DEBUG (SyncWorker_22) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:11:41.560 DEBUG (SyncWorker_22) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:11:41.560 DEBUG (SyncWorker_22) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:11:41.561 DEBUG (SyncWorker_22) [pymodbus.logging] RECV: 
2024-02-08 16:11:41.561 DEBUG (SyncWorker_22) [pymodbus.logging] Retry on empty response - 3
2024-02-08 16:11:41.561 DEBUG (SyncWorker_22) [pymodbus.logging] Changing transaction state from "WAITING_FOR_REPLY" to "RETRYING"
2024-02-08 16:11:41.862 DEBUG (SyncWorker_22) [pymodbus.logging] Sleeping 0.3
2024-02-08 16:11:41.863 DEBUG (SyncWorker_22) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:11:41.863 DEBUG (SyncWorker_22) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:11:46.864 DEBUG (SyncWorker_22) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:11:46.865 DEBUG (SyncWorker_22) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:11:56.872 DEBUG (SyncWorker_22) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:11:56.872 DEBUG (SyncWorker_22) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:11:56.872 DEBUG (SyncWorker_22) [pymodbus.logging] RECV: 
2024-02-08 16:11:56.873 DEBUG (SyncWorker_22) [pymodbus.logging] Retry on empty response - 2
2024-02-08 16:11:56.873 DEBUG (SyncWorker_22) [pymodbus.logging] Changing transaction state from "WAITING_FOR_REPLY" to "RETRYING"
2024-02-08 16:11:57.473 DEBUG (SyncWorker_22) [pymodbus.logging] Sleeping 0.6
2024-02-08 16:11:57.474 DEBUG (SyncWorker_22) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:11:57.474 DEBUG (SyncWorker_22) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:12:02.475 DEBUG (SyncWorker_22) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:12:02.477 DEBUG (SyncWorker_22) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:12:12.484 DEBUG (SyncWorker_22) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:12:12.485 DEBUG (SyncWorker_22) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:12:12.485 DEBUG (SyncWorker_22) [pymodbus.logging] RECV: 
2024-02-08 16:12:12.485 DEBUG (SyncWorker_22) [pymodbus.logging] Retry on empty response - 1
2024-02-08 16:12:12.485 DEBUG (SyncWorker_22) [pymodbus.logging] Changing transaction state from "WAITING_FOR_REPLY" to "RETRYING"
2024-02-08 16:12:13.686 DEBUG (SyncWorker_22) [pymodbus.logging] Sleeping 1.2
2024-02-08 16:12:13.686 DEBUG (SyncWorker_22) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:12:13.687 DEBUG (SyncWorker_22) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:12:18.687 DEBUG (SyncWorker_22) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:12:18.690 DEBUG (SyncWorker_22) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:12:28.697 DEBUG (SyncWorker_22) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:12:28.698 DEBUG (SyncWorker_22) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:12:28.698 DEBUG (SyncWorker_22) [pymodbus.logging] RECV: 
2024-02-08 16:12:28.698 DEBUG (SyncWorker_22) [pymodbus.logging] Processing: 
2024-02-08 16:12:28.699 DEBUG (SyncWorker_22) [pymodbus.logging] Getting transaction 2
2024-02-08 16:12:28.705 DEBUG (SyncWorker_22) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-02-08 16:12:28.706 DEBUG (SyncWorker_22) [homeassistant.components.modbus.modbus] Pymodbus: modbus_hub: Error: device: 2 address: 3 -> Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
2024-02-08 16:12:28.748 DEBUG (SyncWorker_17) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-02-08 16:12:28.748 DEBUG (SyncWorker_17) [pymodbus.logging] Running transaction 597
2024-02-08 16:12:28.749 DEBUG (SyncWorker_17) [pymodbus.logging] SEND: 0x1 0x5 0x0 0x0 0x0 0x0 0xcd 0xca
2024-02-08 16:12:28.749 DEBUG (SyncWorker_17) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:12:28.749 DEBUG (SyncWorker_17) [pymodbus.logging] Changing state to IDLE - Last Frame End - None Current Time stamp - 1707401548.749457
2024-02-08 16:12:28.753 DEBUG (SyncWorker_17) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:12:28.754 DEBUG (SyncWorker_17) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:12:28.781 DEBUG (SyncWorker_17) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:12:28.781 DEBUG (SyncWorker_17) [pymodbus.logging] RECV: 0x1 0x5 0x0 0x0 0x0 0x0 0xcd 0xca
2024-02-08 16:12:28.782 DEBUG (SyncWorker_17) [pymodbus.logging] Processing: 0x1 0x5 0x0 0x0 0x0 0x0 0xcd 0xca
2024-02-08 16:12:28.782 DEBUG (SyncWorker_17) [pymodbus.logging] Getting Frame - 0x5 0x0 0x0 0x0 0x0
2024-02-08 16:12:28.782 DEBUG (SyncWorker_17) [pymodbus.logging] Factory Response[WriteSingleCoilResponse': 5]
2024-02-08 16:12:28.783 DEBUG (SyncWorker_17) [pymodbus.logging] Frame advanced, resetting header!!
2024-02-08 16:12:28.783 DEBUG (SyncWorker_17) [pymodbus.logging] Adding transaction 1
2024-02-08 16:12:28.783 DEBUG (SyncWorker_17) [pymodbus.logging] Getting transaction 1
2024-02-08 16:12:28.783 DEBUG (SyncWorker_17) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-02-08 16:12:28.820 DEBUG (SyncWorker_21) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-02-08 16:12:28.821 DEBUG (SyncWorker_21) [pymodbus.logging] Running transaction 598
2024-02-08 16:12:28.821 DEBUG (SyncWorker_21) [pymodbus.logging] SEND: 0x1 0x5 0x0 0x1 0x0 0x0 0x9c 0xa
2024-02-08 16:12:28.821 DEBUG (SyncWorker_21) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:12:28.822 DEBUG (SyncWorker_21) [pymodbus.logging] Changing state to IDLE - Last Frame End - 1707401548.781214 Current Time stamp - 1707401548.821993
2024-02-08 16:12:28.822 DEBUG (SyncWorker_21) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:12:28.824 DEBUG (SyncWorker_21) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:12:28.852 DEBUG (SyncWorker_21) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:12:28.853 DEBUG (SyncWorker_21) [pymodbus.logging] RECV: 0x1 0x5 0x0 0x1 0x0 0x0 0x9c 0xa
2024-02-08 16:12:28.853 DEBUG (SyncWorker_21) [pymodbus.logging] Processing: 0x1 0x5 0x0 0x1 0x0 0x0 0x9c 0xa
2024-02-08 16:12:28.853 DEBUG (SyncWorker_21) [pymodbus.logging] Getting Frame - 0x5 0x0 0x1 0x0 0x0
2024-02-08 16:12:28.853 DEBUG (SyncWorker_21) [pymodbus.logging] Factory Response[WriteSingleCoilResponse': 5]
2024-02-08 16:12:28.853 DEBUG (SyncWorker_21) [pymodbus.logging] Frame advanced, resetting header!!
2024-02-08 16:12:28.853 DEBUG (SyncWorker_21) [pymodbus.logging] Adding transaction 1
2024-02-08 16:12:28.853 DEBUG (SyncWorker_21) [pymodbus.logging] Getting transaction 1
2024-02-08 16:12:28.853 DEBUG (SyncWorker_21) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-02-08 16:12:28.888 DEBUG (SyncWorker_11) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-02-08 16:12:28.888 DEBUG (SyncWorker_11) [pymodbus.logging] Running transaction 599
2024-02-08 16:12:28.888 DEBUG (SyncWorker_11) [pymodbus.logging] SEND: 0x1 0x5 0x0 0x1 0xff 0x0 0xdd 0xfa
2024-02-08 16:12:28.889 DEBUG (SyncWorker_11) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:12:28.889 DEBUG (SyncWorker_11) [pymodbus.logging] Changing state to IDLE - Last Frame End - 1707401548.852772 Current Time stamp - 1707401548.889321
2024-02-08 16:12:28.889 DEBUG (SyncWorker_11) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:12:28.892 DEBUG (SyncWorker_11) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:12:28.925 DEBUG (SyncWorker_11) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:12:28.925 DEBUG (SyncWorker_11) [pymodbus.logging] RECV: 0x1 0x5 0x0 0x1 0xff 0x0 0xdd 0xfa
2024-02-08 16:12:28.926 DEBUG (SyncWorker_11) [pymodbus.logging] Processing: 0x1 0x5 0x0 0x1 0xff 0x0 0xdd 0xfa
2024-02-08 16:12:28.926 DEBUG (SyncWorker_11) [pymodbus.logging] Getting Frame - 0x5 0x0 0x1 0xff 0x0
2024-02-08 16:12:28.926 DEBUG (SyncWorker_11) [pymodbus.logging] Factory Response[WriteSingleCoilResponse': 5]
2024-02-08 16:12:28.927 DEBUG (SyncWorker_11) [pymodbus.logging] Frame advanced, resetting header!!
2024-02-08 16:12:28.927 DEBUG (SyncWorker_11) [pymodbus.logging] Adding transaction 1
2024-02-08 16:12:28.927 DEBUG (SyncWorker_11) [pymodbus.logging] Getting transaction 1
2024-02-08 16:12:28.927 DEBUG (SyncWorker_11) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-02-08 16:12:28.963 DEBUG (SyncWorker_3) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-02-08 16:12:28.963 DEBUG (SyncWorker_3) [pymodbus.logging] Running transaction 600
2024-02-08 16:12:28.964 DEBUG (SyncWorker_3) [pymodbus.logging] SEND: 0x1 0x5 0x0 0x0 0xff 0x0 0x8c 0x3a
2024-02-08 16:12:28.964 DEBUG (SyncWorker_3) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:12:28.964 DEBUG (SyncWorker_3) [pymodbus.logging] Changing state to IDLE - Last Frame End - 1707401548.925159 Current Time stamp - 1707401548.964811
2024-02-08 16:12:28.965 DEBUG (SyncWorker_3) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:12:28.966 DEBUG (SyncWorker_3) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:12:29.003 DEBUG (SyncWorker_3) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:12:29.004 DEBUG (SyncWorker_3) [pymodbus.logging] RECV: 0x1 0x5 0x0 0x0 0xff 0x0 0x8c 0x3a
2024-02-08 16:12:29.004 DEBUG (SyncWorker_3) [pymodbus.logging] Processing: 0x1 0x5 0x0 0x0 0xff 0x0 0x8c 0x3a
2024-02-08 16:12:29.004 DEBUG (SyncWorker_3) [pymodbus.logging] Getting Frame - 0x5 0x0 0x0 0xff 0x0
2024-02-08 16:12:29.005 DEBUG (SyncWorker_3) [pymodbus.logging] Factory Response[WriteSingleCoilResponse': 5]
2024-02-08 16:12:29.005 DEBUG (SyncWorker_3) [pymodbus.logging] Frame advanced, resetting header!!
2024-02-08 16:12:29.005 DEBUG (SyncWorker_3) [pymodbus.logging] Adding transaction 1
2024-02-08 16:12:29.006 DEBUG (SyncWorker_3) [pymodbus.logging] Getting transaction 1
2024-02-08 16:12:29.006 DEBUG (SyncWorker_3) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-02-08 16:12:29.042 DEBUG (SyncWorker_2) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-02-08 16:12:29.042 DEBUG (SyncWorker_2) [pymodbus.logging] Running transaction 601
2024-02-08 16:12:29.043 DEBUG (SyncWorker_2) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:12:29.043 DEBUG (SyncWorker_2) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:12:29.043 DEBUG (SyncWorker_2) [pymodbus.logging] Changing state to IDLE - Last Frame End - 1707401549.003422 Current Time stamp - 1707401549.04352
2024-02-08 16:12:29.043 DEBUG (SyncWorker_2) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:12:29.046 DEBUG (SyncWorker_2) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:12:39.054 DEBUG (SyncWorker_2) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:12:39.054 DEBUG (SyncWorker_2) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:12:39.055 DEBUG (SyncWorker_2) [pymodbus.logging] RECV: 
2024-02-08 16:12:39.055 DEBUG (SyncWorker_2) [pymodbus.logging] Retry on empty response - 3
2024-02-08 16:12:39.055 DEBUG (SyncWorker_2) [pymodbus.logging] Changing transaction state from "WAITING_FOR_REPLY" to "RETRYING"
2024-02-08 16:12:39.356 DEBUG (SyncWorker_2) [pymodbus.logging] Sleeping 0.3
2024-02-08 16:12:39.356 DEBUG (SyncWorker_2) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:12:39.357 DEBUG (SyncWorker_2) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:12:44.357 DEBUG (SyncWorker_2) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:12:44.358 DEBUG (SyncWorker_2) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:12:54.368 DEBUG (SyncWorker_2) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:12:54.368 DEBUG (SyncWorker_2) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:12:54.368 DEBUG (SyncWorker_2) [pymodbus.logging] RECV: 
2024-02-08 16:12:54.369 DEBUG (SyncWorker_2) [pymodbus.logging] Retry on empty response - 2
2024-02-08 16:12:54.369 DEBUG (SyncWorker_2) [pymodbus.logging] Changing transaction state from "WAITING_FOR_REPLY" to "RETRYING"
2024-02-08 16:12:54.969 DEBUG (SyncWorker_2) [pymodbus.logging] Sleeping 0.6
2024-02-08 16:12:54.970 DEBUG (SyncWorker_2) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:12:54.970 DEBUG (SyncWorker_2) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:12:59.971 DEBUG (SyncWorker_2) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:12:59.972 DEBUG (SyncWorker_2) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:13:09.979 DEBUG (SyncWorker_2) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:13:09.979 DEBUG (SyncWorker_2) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:13:09.980 DEBUG (SyncWorker_2) [pymodbus.logging] RECV: 
2024-02-08 16:13:09.980 DEBUG (SyncWorker_2) [pymodbus.logging] Retry on empty response - 1
2024-02-08 16:13:09.980 DEBUG (SyncWorker_2) [pymodbus.logging] Changing transaction state from "WAITING_FOR_REPLY" to "RETRYING"
2024-02-08 16:13:11.181 DEBUG (SyncWorker_2) [pymodbus.logging] Sleeping 1.2
2024-02-08 16:13:11.181 DEBUG (SyncWorker_2) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:13:11.181 DEBUG (SyncWorker_2) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:13:16.182 DEBUG (SyncWorker_2) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:13:16.184 DEBUG (SyncWorker_2) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:13:26.191 DEBUG (SyncWorker_2) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:13:26.192 DEBUG (SyncWorker_2) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:13:26.192 DEBUG (SyncWorker_2) [pymodbus.logging] RECV: 
2024-02-08 16:13:26.192 DEBUG (SyncWorker_2) [pymodbus.logging] Processing: 
2024-02-08 16:13:26.193 DEBUG (SyncWorker_2) [pymodbus.logging] Getting transaction 2
2024-02-08 16:13:26.201 DEBUG (SyncWorker_2) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-02-08 16:13:26.201 ERROR (SyncWorker_2) [homeassistant.components.modbus.modbus] Pymodbus: modbus_hub: Error: device: 2 address: 3 -> Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response

@janiversen
Copy link
Member

you cut the log exactly at the point where it becomes interesting.

@yoch
Copy link
Author

yoch commented Feb 8, 2024

Sorry, here's the rest (then I turned off the box) :

2024-02-08 16:13:26.243 DEBUG (SyncWorker_23) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-02-08 16:13:26.243 DEBUG (SyncWorker_23) [pymodbus.logging] Running transaction 602
2024-02-08 16:13:26.244 DEBUG (SyncWorker_23) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:13:26.244 DEBUG (SyncWorker_23) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:13:26.245 DEBUG (SyncWorker_23) [pymodbus.logging] Changing state to IDLE - Last Frame End - None Current Time stamp - 1707401606.244974
2024-02-08 16:13:26.249 DEBUG (SyncWorker_23) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:13:26.251 DEBUG (SyncWorker_23) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:13:36.257 DEBUG (SyncWorker_23) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:13:36.258 DEBUG (SyncWorker_23) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:13:36.258 DEBUG (SyncWorker_23) [pymodbus.logging] RECV: 
2024-02-08 16:13:36.259 DEBUG (SyncWorker_23) [pymodbus.logging] Retry on empty response - 3
2024-02-08 16:13:36.259 DEBUG (SyncWorker_23) [pymodbus.logging] Changing transaction state from "WAITING_FOR_REPLY" to "RETRYING"
2024-02-08 16:13:36.559 DEBUG (SyncWorker_23) [pymodbus.logging] Sleeping 0.3
2024-02-08 16:13:36.560 DEBUG (SyncWorker_23) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:13:36.561 DEBUG (SyncWorker_23) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:13:41.561 DEBUG (SyncWorker_23) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:13:41.563 DEBUG (SyncWorker_23) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:13:51.570 DEBUG (SyncWorker_23) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:13:51.570 DEBUG (SyncWorker_23) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:13:51.570 DEBUG (SyncWorker_23) [pymodbus.logging] RECV: 
2024-02-08 16:13:51.571 DEBUG (SyncWorker_23) [pymodbus.logging] Retry on empty response - 2
2024-02-08 16:13:51.571 DEBUG (SyncWorker_23) [pymodbus.logging] Changing transaction state from "WAITING_FOR_REPLY" to "RETRYING"
2024-02-08 16:13:52.171 DEBUG (SyncWorker_23) [pymodbus.logging] Sleeping 0.6
2024-02-08 16:13:52.172 DEBUG (SyncWorker_23) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:13:52.172 DEBUG (SyncWorker_23) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:13:57.173 DEBUG (SyncWorker_23) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:13:57.175 DEBUG (SyncWorker_23) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:14:07.183 DEBUG (SyncWorker_23) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:14:07.184 DEBUG (SyncWorker_23) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:14:07.184 DEBUG (SyncWorker_23) [pymodbus.logging] RECV: 
2024-02-08 16:14:07.184 DEBUG (SyncWorker_23) [pymodbus.logging] Retry on empty response - 1
2024-02-08 16:14:07.185 DEBUG (SyncWorker_23) [pymodbus.logging] Changing transaction state from "WAITING_FOR_REPLY" to "RETRYING"
2024-02-08 16:14:08.385 DEBUG (SyncWorker_23) [pymodbus.logging] Sleeping 1.2
2024-02-08 16:14:08.386 DEBUG (SyncWorker_23) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:14:08.386 DEBUG (SyncWorker_23) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:14:13.387 DEBUG (SyncWorker_23) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:14:13.389 DEBUG (SyncWorker_23) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:14:23.397 DEBUG (SyncWorker_23) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:14:23.397 DEBUG (SyncWorker_23) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:14:23.397 DEBUG (SyncWorker_23) [pymodbus.logging] RECV: 
2024-02-08 16:14:23.398 DEBUG (SyncWorker_23) [pymodbus.logging] Processing: 
2024-02-08 16:14:23.398 DEBUG (SyncWorker_23) [pymodbus.logging] Getting transaction 2
2024-02-08 16:14:23.405 DEBUG (SyncWorker_23) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-02-08 16:14:23.405 DEBUG (SyncWorker_23) [homeassistant.components.modbus.modbus] Pymodbus: modbus_hub: Error: device: 2 address: 3 -> Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
2024-02-08 16:14:23.446 DEBUG (SyncWorker_26) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-02-08 16:14:23.447 DEBUG (SyncWorker_26) [pymodbus.logging] Running transaction 603
2024-02-08 16:14:23.447 DEBUG (SyncWorker_26) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:14:23.447 DEBUG (SyncWorker_26) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:14:23.447 DEBUG (SyncWorker_26) [pymodbus.logging] Changing state to IDLE - Last Frame End - None Current Time stamp - 1707401663.447828
2024-02-08 16:14:23.452 DEBUG (SyncWorker_26) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:14:23.453 DEBUG (SyncWorker_26) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:14:33.461 DEBUG (SyncWorker_26) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:14:33.461 DEBUG (SyncWorker_26) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:14:33.461 DEBUG (SyncWorker_26) [pymodbus.logging] RECV: 
2024-02-08 16:14:33.462 DEBUG (SyncWorker_26) [pymodbus.logging] Retry on empty response - 3
2024-02-08 16:14:33.462 DEBUG (SyncWorker_26) [pymodbus.logging] Changing transaction state from "WAITING_FOR_REPLY" to "RETRYING"
2024-02-08 16:14:33.763 DEBUG (SyncWorker_26) [pymodbus.logging] Sleeping 0.3
2024-02-08 16:14:33.763 DEBUG (SyncWorker_26) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:14:33.764 DEBUG (SyncWorker_26) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:14:38.764 DEBUG (SyncWorker_26) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:14:38.766 DEBUG (SyncWorker_26) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:14:48.774 DEBUG (SyncWorker_26) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:14:48.774 DEBUG (SyncWorker_26) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:14:48.774 DEBUG (SyncWorker_26) [pymodbus.logging] RECV: 
2024-02-08 16:14:48.775 DEBUG (SyncWorker_26) [pymodbus.logging] Retry on empty response - 2
2024-02-08 16:14:48.775 DEBUG (SyncWorker_26) [pymodbus.logging] Changing transaction state from "WAITING_FOR_REPLY" to "RETRYING"
2024-02-08 16:14:49.375 DEBUG (SyncWorker_26) [pymodbus.logging] Sleeping 0.6
2024-02-08 16:14:49.376 DEBUG (SyncWorker_26) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:14:49.377 DEBUG (SyncWorker_26) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:14:54.377 DEBUG (SyncWorker_26) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:14:54.379 DEBUG (SyncWorker_26) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:15:04.388 DEBUG (SyncWorker_26) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:15:04.389 DEBUG (SyncWorker_26) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:15:04.389 DEBUG (SyncWorker_26) [pymodbus.logging] RECV: 
2024-02-08 16:15:04.389 DEBUG (SyncWorker_26) [pymodbus.logging] Retry on empty response - 1
2024-02-08 16:15:04.389 DEBUG (SyncWorker_26) [pymodbus.logging] Changing transaction state from "WAITING_FOR_REPLY" to "RETRYING"
2024-02-08 16:15:05.590 DEBUG (SyncWorker_26) [pymodbus.logging] Sleeping 1.2
2024-02-08 16:15:05.591 DEBUG (SyncWorker_26) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:15:05.591 DEBUG (SyncWorker_26) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:15:10.592 DEBUG (SyncWorker_26) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:15:10.593 DEBUG (SyncWorker_26) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:15:20.602 DEBUG (SyncWorker_26) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:15:20.602 DEBUG (SyncWorker_26) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:15:20.602 DEBUG (SyncWorker_26) [pymodbus.logging] RECV: 
2024-02-08 16:15:20.603 DEBUG (SyncWorker_26) [pymodbus.logging] Processing: 
2024-02-08 16:15:20.603 DEBUG (SyncWorker_26) [pymodbus.logging] Getting transaction 2
2024-02-08 16:15:20.610 DEBUG (SyncWorker_26) [pymodbus.logging] Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
2024-02-08 16:15:20.610 DEBUG (SyncWorker_26) [homeassistant.components.modbus.modbus] Pymodbus: modbus_hub: Error: device: 2 address: 3 -> Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
2024-02-08 16:15:20.653 DEBUG (SyncWorker_16) [pymodbus.logging] Current transaction state - TRANSACTION_COMPLETE
2024-02-08 16:15:20.654 DEBUG (SyncWorker_16) [pymodbus.logging] Running transaction 604
2024-02-08 16:15:20.654 DEBUG (SyncWorker_16) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:15:20.655 DEBUG (SyncWorker_16) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:15:20.655 DEBUG (SyncWorker_16) [pymodbus.logging] Changing state to IDLE - Last Frame End - None Current Time stamp - 1707401720.655231
2024-02-08 16:15:20.660 DEBUG (SyncWorker_16) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:15:20.662 DEBUG (SyncWorker_16) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:15:30.670 DEBUG (SyncWorker_16) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:15:30.670 DEBUG (SyncWorker_16) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:15:30.670 DEBUG (SyncWorker_16) [pymodbus.logging] RECV: 
2024-02-08 16:15:30.671 DEBUG (SyncWorker_16) [pymodbus.logging] Retry on empty response - 3
2024-02-08 16:15:30.671 DEBUG (SyncWorker_16) [pymodbus.logging] Changing transaction state from "WAITING_FOR_REPLY" to "RETRYING"
2024-02-08 16:15:30.972 DEBUG (SyncWorker_16) [pymodbus.logging] Sleeping 0.3
2024-02-08 16:15:30.972 DEBUG (SyncWorker_16) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:15:30.973 DEBUG (SyncWorker_16) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:15:35.973 DEBUG (SyncWorker_16) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:15:35.975 DEBUG (SyncWorker_16) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:15:45.983 DEBUG (SyncWorker_16) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:15:45.983 DEBUG (SyncWorker_16) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:15:45.983 DEBUG (SyncWorker_16) [pymodbus.logging] RECV: 
2024-02-08 16:15:45.984 DEBUG (SyncWorker_16) [pymodbus.logging] Retry on empty response - 2
2024-02-08 16:15:45.984 DEBUG (SyncWorker_16) [pymodbus.logging] Changing transaction state from "WAITING_FOR_REPLY" to "RETRYING"
2024-02-08 16:15:46.585 DEBUG (SyncWorker_16) [pymodbus.logging] Sleeping 0.6
2024-02-08 16:15:46.585 DEBUG (SyncWorker_16) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:15:46.586 DEBUG (SyncWorker_16) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-02-08 16:15:51.586 DEBUG (SyncWorker_16) [pymodbus.logging] New Transaction state "SENDING"
2024-02-08 16:15:51.588 DEBUG (SyncWorker_16) [pymodbus.logging] Changing transaction state from "SENDING" to "WAITING FOR REPLY"
2024-02-08 16:16:01.596 DEBUG (SyncWorker_16) [pymodbus.logging] No response received, Expected 7 bytes Received 0 bytes !!!!
2024-02-08 16:16:01.597 DEBUG (SyncWorker_16) [pymodbus.logging] Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
2024-02-08 16:16:01.597 DEBUG (SyncWorker_16) [pymodbus.logging] RECV: 
2024-02-08 16:16:01.597 DEBUG (SyncWorker_16) [pymodbus.logging] Retry on empty response - 1
2024-02-08 16:16:01.597 DEBUG (SyncWorker_16) [pymodbus.logging] Changing transaction state from "WAITING_FOR_REPLY" to "RETRYING"
2024-02-08 16:16:02.798 DEBUG (SyncWorker_16) [pymodbus.logging] Sleeping 1.2
2024-02-08 16:16:02.799 DEBUG (SyncWorker_16) [pymodbus.logging] SEND: 0x2 0x3 0x0 0x3 0x0 0x1 0x74 0x39
2024-02-08 16:16:02.799 DEBUG (SyncWorker_16) [pymodbus.logging] Resetting frame - Current Frame in buffer - 

@janiversen
Copy link
Member

This is all as expected, device 2 do not respond. Apart from an important difference, there are no stack trace !

But I cannot see you are trying to use device 1, by switching something. A switch entity is passive and do not collect data until you ask it to, by making a switch.

Maybe I have misunderstood your problem, can you please explain a bit more "the switches set on the relay no longer work properly".

@yoch
Copy link
Author

yoch commented Feb 8, 2024

This is exactly the problem I described: I switch the relay in the interface but nothing happens, likely because the device isn't actually called.

If I connect the thermostat back, then the device respond instantly and the call do appears in the log.

@janiversen
Copy link
Member

Well if that is when the traceback comes, then there is a PR submitted.

But the idea was that provide a debug log that shows the problem, and not break it up in pieces so we cannot see the sequence.

@github-actions github-actions bot locked and limited conversation to collaborators Mar 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants