We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug HA Log throws errors and entities are randomly not available for some seconds. Then they appear again.
Your Sungrow inverter:
Model: [e.g. SH-10.RT v112] SH8.0RT-V112
The inverter is connected via (mark one)
Are you using a Modbus Proxy (mark one)
Home Assistant :
modbus_sungrow.yaml:
** Inverter Firmware Status:**
To Reproduce Steps to reproduce the behavior:
Expected behavior No errors like provided and entities should constantly available.
Screenshots
Additional context Behaviour that entities are shortly and randomly not available appears since HA update to 2024.1.0
Logger: homeassistant.components.modbus.modbus Source: components/modbus/modbus.py:375 Integration: Modbus (documentation, issues) First occurred: 4. Januar 2024 um 15:10:58 (6370 occurrences) Last logged: 10:51:46 Pymodbus: SungrowSHx: Error: device: 1 address: 13050 -> Modbus Error: [Input/Output] [Errno 32] Broken pipe Pymodbus: SungrowSHx: Error: device: 1 address: 33047 -> Modbus Error: [Connection] ModbusTcpClient(192.168.178.36:502): Connection unexpectedly closed 0.0004031658172607422 seconds into read of 8 bytes without response from slave before it closed connection Pymodbus: SungrowSHx: Error: device: 1 address: 13024 -> Modbus Error: [Connection] ModbusTcpClient(192.168.178.36:502): Connection unexpectedly closed 0.00040435791015625 seconds into read of 8 bytes without response from slave before it closed connection Pymodbus: SungrowSHx: Error: device: 1 address: 13019 -> Modbus Error: [Input/Output] [Errno 32] Broken pipe Pymodbus: SungrowSHx: Error: device: 1 address: 5007 -> Modbus Error: [Input/Output] [Errno 32] Broken pipe Logger: homeassistant.components.modbus.modbus Source: components/modbus/modbus.py:375 Integration: Modbus (documentation, issues) First occurred: 4. Januar 2024 um 15:10:58 (6420 occurrences) Last logged: 10:56:58 Pymodbus: SungrowSHx: Error: device: 1 address: 13032 -> Modbus Error: [Input/Output] [Errno 32] Broken pipe Pymodbus: SungrowSHx: Error: device: 1 address: 5007 -> Modbus Error: [Input/Output] [Errno 32] Broken pipe Pymodbus: SungrowSHx: Error: device: 1 address: 5016 -> Modbus Error: [Input/Output] [Errno 32] Broken pipe Pymodbus: SungrowSHx: Error: device: 1 address: 33047 -> Modbus Error: [Input/Output] [Errno 32] Broken pipe Pymodbus: SungrowSHx: Error: device: 1 address: 13021 -> Modbus Error: [Connection] ModbusTcpClient(192.168.178.36:502): Connection unexpectedly closed 0.0015299320220947266 seconds into read of 8 bytes without response from slave before it closed connection
The text was updated successfully, but these errors were encountered:
I can confirm i have the same issue on a SH10RT inverter.
Sorry, something went wrong.
Since I've moved to modbus proxy I started to see similar effects. My battery related entity vanished while the rest stays available.
This issue is stale because it has been open for 30 days with no activity.
No branches or pull requests
Describe the bug
HA Log throws errors and entities are randomly not available for some seconds. Then they appear again.
Your Sungrow inverter:
Model: [e.g. SH-10.RT v112]
SH8.0RT-V112
The inverter is connected via (mark one)
Are you using a Modbus Proxy (mark one)
Home Assistant :
2024.1.0
modbus_sungrow.yaml:
2023-12-31
** Inverter Firmware Status:**
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No errors like provided and entities should constantly available.
Screenshots
Additional context
Behaviour that entities are shortly and randomly not available appears since HA update to 2024.1.0
The text was updated successfully, but these errors were encountered: