Error: device: 1 address: 13050 -> Modbus Error: [Input/Output] [Errno 32] Broken pipe

[smartmatic]

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)

  • [x] LAN (internal port)
  • [] WiNet-S (LAN)
  • [] WiNet-S (WLAN)

• Are you using a Modbus Proxy (mark one)
  • [] yes
  • [] no
  • [x] I don't know what that is

Home Assistant :

• Version: [e.g. 2023.09.1] 2024.1.0

modbus_sungrow.yaml:

• Version/ time stamp : [e.g. 2023-09-08] (see header of the file) 2023-12-31

Inverter Firmware Status:

• [x] I made sure that the newest firmware is installed via the installers account

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

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

[NBD99]

I can confirm i have the same issue on a SH10RT inverter.

[umrath]

Since I've moved to modbus proxy I started to see similar effects. My battery related entity vanished while the rest stays available.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.

[umrath]

The problem persists.

[Gnarfoz]

Communication errors can't really be fixed here. This package does no communication by itself. It's "merely" a big configuration file for Home Assistant's built-in Modbus functionality. That said, are you sure Home Assistant is the only thing accessing the inverter via Modbus? The Modbus stack on the inverter is notoriously unstable when multiple clients try to access it.