I found this ticket, they claim it will be solved in dev and will be released in 2023.9.2:
Victron/Modbus disconnects/unavailable · Issue #100138 · home-assistant/core · GitHub
That ticket is specifically about the Victron module, but it looks like the tickets I put in the next post talk about the issues with pymodbus and how they will upgrade that package in 2023.9.2. Setting your timeout to be bigger may be a kludge to get it working for now.
These tickets look like they might be more relevant:
For information I can tell that my problems with closed connections were solved in 2023.9.2
Same problem for me now in 2023.9.3.
My charging station is constantly crashing because of this and needed to revert to 2023.9.2 to resolve it.
Oh noooes…! I guess I’m staying with current version for a while…
Has anyone tried the 2023.10 release yet? How is it working?
Hello, is your Modbus configuration working? I’m learning this to access my Modbus, do you have any information to share, thank you
there has been breaking changes in the modbus integration so configurations that were previously working have stopped. It was resolved in 2023.9.2 and was reported broken again in 2023.9.3 by some users. The question is if its working as intended in 2023.10?
Hi Y’all, I’m having Modbus issues too. I have a number of hardwired (RS485) RTU devices with various timings, and I think sometimes they timings coincide causing a network overload. (a timeout error) It looks like the new revision then spends some time cleaning up buffers which causes it to miss the next modbus poll and the whole thing turns to custard for a while. I cannot run update 9.5, and have had to revert to version 8.5.
Hey guys. I have problems with the modbus. I’m noob in it and will be great to have some help. i recive this error:
2024-02-09 20:46:30.444 ERROR (SyncWorker_11) [homeassistant.components.modbus.modbus] Pymodbus: netp: Error: device: 3 address: 30021 → pymodbus returned isError True
And this is my config:
Thanks in advace !!!
I’m having exactly the same problem as others above: I’ve tried various configurations:
modbus:
- name: USR-NET-IO
type: tcp
host: 192.168.30.104
port: 502
close_comm_on_error: true
delay: 1
timeout: 5
retry_on_empty: true
message_wait_milliseconds: 250
retries: 3
#delay: 0
#message_wait_milliseconds: 100
#timeout: 15
sensors:
- name: GB3JV PA Temperature
slave: 17
address: 80
input_type: holding
unit_of_measurement: °C
state_class: measurement
scale: 0.01
offset: -100
precision: 0
- name: GB3JV Return Loss
slave: 17
address: 88
input_type: holding
unit_of_measurement: dB
state_class: measurement
scale: 0.01
offset: 0
precision: 0
switches:
- name: GB3JV PA
slave: 17
address: 3
write_type: coil
verify:
- name: GB3JV Drive
slave: 17
address: 2
write_type: coil
verify:
binary_sensors:
- name: GB3JV PA
address: 3
slave: 17
- name: GB3JV Drive
address: 2
slave: 17
Log file looks like this:
Logger: homeassistant.components.modbus.modbus
Source: components/modbus/modbus.py:318
integration: Modbus (documentation, issues)
First occurred: 17:18:27 (62 occurrences)
Last logged: 23:40:20
Pymodbus: USR-NET-IO: Error: device: 17 address: 2 -> Modbus Error: [Input/Output] ERROR: No response received after 3 retries
Pymodbus: USR-NET-IO: Error: device: 17 address: 80 -> Modbus Error: [Input/Output] ERROR: No response received after 3 retries
Pymodbus: USR-NET-IO: Error: device: 17 address: 80 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.30.104:502]
Logger: homeassistant.components.modbus.modbus
Source: components/modbus/modbus.py:318
integration: Modbus (documentation, issues)
First occurred: 17:18:27 (62 occurrences)
Last logged: 23:40:20
Pymodbus: USR-NET-IO: Error: device: 17 address: 2 -> Modbus Error: [Input/Output] ERROR: No response received after 3 retries
Pymodbus: USR-NET-IO: Error: device: 17 address: 80 -> Modbus Error: [Input/Output] ERROR: No response received after 3 retries
Pymodbus: USR-NET-IO: Error: device: 17 address: 80 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.30.104:502]
But I sometimes get this, but it’s a TCP/IP connection, not serial!
Logger: homeassistant.config
Source: config.py:1324
First occurred: 23:35:26 (4 occurrences)
Last logged: 23:42:21
Invalid config for 'modbus' at configuration.yaml, line 43: required key 'baudrate' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 43: required key 'bytesize' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 43: required key 'method' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 43: required key 'parity' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 43: required key 'stopbits' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 44: not a valid value for dictionary value 'modbus->0->type', got 'tcp', please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 45: 'host' is an invalid option for 'modbus', check: modbus->0->host, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 47: 'close_comm_on_error' is an invalid option for 'modbus', check: modbus->0->close_comm_on_error, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 50: 'retry_on_empty' is an invalid option for 'modbus', check: modbus->0->retry_on_empty, please check the docs at https://www.home-assistant.io/integrations/modbus
Invalid config for 'modbus' at configuration.yaml, line 43: required key 'baudrate' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 43: required key 'bytesize' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 43: required key 'method' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 43: required key 'parity' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 43: required key 'stopbits' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 44: not a valid value for dictionary value 'modbus->0->type', got 'tcp', please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 45: 'host' is an invalid option for 'modbus', check: modbus->0->host, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 47: 'close_comm_on_error' is an invalid option for 'modbus', check: modbus->0->close_comm_on_error, please check the docs at https://www.home-assistant.io/integrations/modbus
Any news for latest version? Still an issue?
Just updated to 2024.5.2 and everything seems fine after almost 2 hours
I now see this issue on 2024.8.2 … I am lost