-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
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
Comments
Hey there @janiversen, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) modbus documentation |
Please with a debug log as pr modbus documentation so we can see what happens. |
The traceback seems incomplete, but that might be the real problem...a debug log will show. |
Here is a more complete log with pymodbus set to dbug.
|
you cut the log exactly at the point where it becomes interesting. |
Sorry, here's the rest (then I turned off the box) :
|
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". |
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. |
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. |
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
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
The text was updated successfully, but these errors were encountered: