ModbusTcpClient(redacted:1502): Connection unexpectedly closed

[bakboord4]

Basically there two, connected, error messages (copies from Log)

2022-08-20 23:08:40.007 ERROR (MainThread) [custom_components.solaredge_modbus_multi] Error fetching SolarEdge Coordinator data: Failed to update devices: Modbus Error: [Connection] ModbusTcpClient(.......:1502): Connection unexpectedly closed 0.000131 seconds into read of 8 bytes without response from unit before it closed connection

2022-08-21 05:54:43.009 ERROR (MainThread) [custom_components.solaredge_modbus_multi] Error fetching SolarEdge Coordinator data: Failed to update devices: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
2022-08-21 05:55:46.007 ERROR (SyncWorker_5) [pymodbus.client.sync] Connection to (......., 1502) failed: timed out
2022-08-21 05:56:49.006 ERROR (SyncWorker_0) [pymodbus.client.sync] Connection to (......., 1502) failed: timed out
....... continuing...

Solaredge thru modbus is unreachable. No data is coming into HA. Solaredge entities are: not available.
Getting control back by either by resetting or reinstall of the integration Solaredge.
Reconfigured the WiFI connection with my LAN brought no solution.
Every time within a few hours after a restart, both errors appear.

Solaredge Support updated my Solaredge and stated that the transformer is operating ok.

Home Assistant (please complete the following information):

• Home Assistant Core Version: 2022.8.6 and .5
• solaredge-modbus-multi Version: 2.1.2 also 2.1.1. The integration is standard configured.

Please, do you have a solution?

[WillCodeForCats]

First try turning on the "Keep Modbus Connection Open" option.

[bakboord4]

Thanks for the reply.
Turned Keep .... open on.
Will report tomorrow after 24 hrs.

[WillCodeForCats]

If that doesn't help, I've also created a pre-release for the latest pymodbus dev version: v2.1.2-pymodbusdev.1

If you are using HACS you will need to turn on "show beta versions" for the integration in HACS (you can do this by choosing "redownload")

[bakboord4]

@WillCodeForCats. Will keep your suggestion in mind.

A Status update.
Applied Keep ..connection open.
In the last hour Solaredge status is alternating per 300 sec (call freq.) between status: 4 (production) and status: not available and per 10 minutes an error:
Error fetching SolarEdge Coordinator data: Failed to update devices: Modbus Error: [Connection] ModbusTcpClient(192.168.2.119:1502): Connection unexpectedly closed 0.000475 seconds into read of 8 bytes without response from unit before it closed connection

[WillCodeForCats]

We can randomly try things but if the inverter is dropping the connection during the read there's probably no actual fix I can come up with.

I don't use wifi so if there's a network problem related to wifi anywhere in the communication path I probably won't see the issue personally.

[WillCodeForCats]

Did you try the pymodbusdev.1 pre release version?

[bakboord4]

@WillCodeForCats.
Not yet. Will do that tomorrow.
I am also contemplating how to connect Solaredge with a cable instead of WiFi.

[WillCodeForCats]

I've created Release v2.1.3-pre.1 which adds disconnect calls on modbus read errors. The idea is that if there is an error it will make sure the connection is closed and re-opened on the next attempt.

[bakboord4]

@WillCodeForCats.
Tomorrow is this evening. Installed V2.1.2-pymodbusdev.1 pre.
20 min Solaredge status: in production, after that, alternation of status started again: 5 min in production and 5 min not available. No improvement.
Just saw your 2.1.3-pre.1. Will try it.

[WillCodeForCats]

Just to be clear, read errors can't be prevented by the integration. I can only change how the integration handles errors.

[bakboord4]

@WillCodeForCats
Applied 2.1.3-pre.1. It looks good so far. No alternation of statuses seen.
Let see what the performance will be the coming 24 hrs.
Support for your focus on error handling.

[bakboord4]

@WillCodeForCats
In status "production", last night started at 20:39 and continued in sleeping mode at 21:14 56 error messages were recorded until 5:49:

---

Deze fout is ontstaan door een aangepaste integratie.

Logger: custom_components.solaredge_modbus_multi
Source: custom_components/solaredge_modbus_multi/hub.py:347
Integration: SolarEdge Modbus Multi Device (documentation, issues)
First occurred: 21 augustus 2022 20:39:31 (56 occurrences)
Last logged: 05:49:31

Unexpected error fetching SolarEdge Coordinator data: Modbus Error: [Connection] ModbusTcpClient(...:1502): Connection unexpectedly closed 0.000135 seconds into read of 8 bytes without response from unit before it closed connection
Unexpected error fetching SolarEdge Coordinator data: Modbus Error: [Connection] ModbusTcpClient(..:1502): Connection unexpectedly closed 0.000132 seconds into read of 8 bytes without response from unit before it closed connection
Unexpected error fetching SolarEdge Coordinator data: Modbus Error: [Connection] ModbusTcpClient(..:1502): Connection unexpectedly closed 0.000136 seconds into read of 8 bytes without response from unit before it closed connection
Unexpected error fetching SolarEdge Coordinator data: Modbus Error: [Connection] ModbusTcpClient(...:1502): Connection unexpectedly closed 0.000138 seconds into read of 8 bytes without response from unit before it closed connection
Unexpected error fetching SolarEdge Coordinator data: Modbus Error: [Connection] ModbusTcpClient(1....:1502): Connection unexpectedly closed 0.000164 seconds into read of 8 bytes without response from unit before it closed connection
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 205, in _async_refresh
self.data = await self._async_update_data()
File "/config/custom_components/solaredge_modbus_multi/init.py", line 121, in _async_update_data
return await self._hub.async_refresh_modbus_data()
File "/config/custom_components/solaredge_modbus_multi/hub.py", line 291, in async_refresh_modbus_data
await self._hass.async_add_executor_job(inverter.read_modbus_data)
File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/solaredge_modbus_multi/hub.py", line 447, in read_modbus_data
inverter_data = self.hub.read_holding_registers(
File "/config/custom_components/solaredge_modbus_multi/hub.py", line 347, in read_holding_registers
return self._client.read_holding_registers(address, count, **kwargs)
File "/usr/local/lib/python3.10/site-packages/pymodbus/client/common.py", line 114, in read_holding_registers
return self.execute(request)
File "/usr/local/lib/python3.10/site-packages/pymodbus/client/sync.py", line 109, in execute
return self.transaction.execute(request)
File "/usr/local/lib/python3.10/site-packages/pymodbus/transaction.py", line 174, in execute
response, last_exception = self._transact(
File "/usr/local/lib/python3.10/site-packages/pymodbus/transaction.py", line 294, in _transact
result = self._recv(response_length, full)
File "/usr/local/lib/python3.10/site-packages/pymodbus/transaction.py", line 326, in _recv
read_min = self.client.framer.recvPacket(min_size)
File "/usr/local/lib/python3.10/site-packages/pymodbus/framer/init.py", line 49, in recvPacket
return self.client.recv(size)
File "/usr/local/lib/python3.10/site-packages/pymodbus/client/sync.py", line 89, in recv
return self._recv(size)
File "/usr/local/lib/python3.10/site-packages/pymodbus/client/sync.py", line 297, in _recv
return self._handle_abrupt_socket_close(
File "/usr/local/lib/python3.10/site-packages/pymodbus/client/sync.py", line 342, in _handle_abrupt_socket_close
raise ConnectionException(msg)
pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] ModbusTcpClient(.....:1502): Connection unexpectedly closed 0.000101 seconds into read of 8 bytes without response from unit before it closed connection

At 5.49 sleeping mode changed into a non recoverable "not available" generating per 5 min. error messages:

---

2022-08-22 05:54:34.007 ERROR (SyncWorker_4) [pymodbus.client.sync] Connection to (.., 1502) failed: timed out
2022-08-22 05:59:37.009 ERROR (SyncWorker_2) [pymodbus.client.sync] Connection to (.., 1502) failed: timed out
2022-08-22 06:04:40.007 ERROR (SyncWorker_2) [pymodbus.client.sync] Connection to (.... 1502) failed: timed out
.........

At 8:30 I made a total hardware restart and in HA, Solaredge status is showing "production"......

[WillCodeForCats]

Added connection exception in Release v2.1.3-pre.2

[bakboord4]

@WillCodeForCats
Implemented -pre.2