Communication fails (irreversible) after restart

[CSH12]

Describe the bug
After a restart of HA the communication to modbus fails.

Expected behavior
Communication established also after restart

Screenshots

Debug Logs
2023-08-08 10:02:05.166 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] solaredge_modbus_multi configuration: number_of_inverters=1, start_device_id=1, detect_meters=True, detect_batteries=True, keep_modbus_open=True, adv_storage_control=False, adv_site_limit_control=False, allow_battery_energy_reset=False, battery_rating_adjust=0,
2023-08-08 10:02:05.166 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] coordinator timeout is 21.6
2023-08-08 10:02:05.174 WARNING (MainThread) [pymodbus.logging] Failed to connect [Errno 111] Connect call failed ('192.168.2.113', 1502)
2023-08-08 10:02:05.176 DEBUG (MainThread) [custom_components.solaredge_modbus_multi] Finished fetching SolarEdge Coordinator data in 0.010 seconds (success: False)
2023-08-08 10:02:05.419 WARNING (MainThread) [pymodbus.logging] Failed to connect [Errno 111] Connect call failed ('192.168.2.113', 1502)

Home Assistant (please complete the following information):

• Home Assistant Core Version: Hassos 10.4, HA 2023.8.1
• solaredge-modbus-multi Version: v2.4.1
• Installation Type: Supervised

Additional context
After deleting the inegration, restarting HA and reintegrating of solaredge modbus multi, the integration is working properly

My configuration is the following:

[WillCodeForCats]

The "Connect call failed" error is from pymodbus, not this integration.

You can try rebooting your inverter or the server Home Assistant is running on.

[froggi1930]

same issue here. reboot of Inverter and HA did not change anything. No other instance is connecting to the Converter Modbus.

[pymodbus.logging] Failed to connect [Errno 111] Connect call failed.

If I read a register manually through the modbus integration I receive a value immediately.

Home Assistant 2023.8.1
Supervisor 2023.08.1
Operating System 10.4
Frontend 20230802.0 - latest

[WillCodeForCats]

I have not seen this problem in my HAOS test environments.

[WillCodeForCats]

Also everyone needs to upload their diagnostic files and debug logs.

[froggi1930]

Also everyone needs to upload their diagnostic files and debug logs.

I am new to Home Assistant. What files do you need and where do I find them?

[WillCodeForCats]

Go to any inverter or meter or battery device info screen and there is a button that says "download diagnostics", it will download a file that can be uploaded here.

[froggi1930]

Go to any inverter or meter or battery device info screen and there is a button that says "download diagnostics", it will download a file that can be uploaded here.

Thanks... I will set up a fresh installation and set up the SolardEdge again. In case I run into the same issues I will post the log files.

[froggi1930]

I have made a fresh installation and get the same error. If I read the modbus with the same settings in iobroker I do not fail.
I can not upload the debug file here... :-(

[WillCodeForCats]

Those logs are from a different integration, not this one.

[froggi1930]

Sorry... my mistake. Looks like I tried the wrong one. Here is the log for your solution.

home-assistant_solaredge_modbus_multi_2023-08-10T15-46-08.541Z.log

[WillCodeForCats]

I don't know what iobroker is, show debug logs from that and your inverter modbus config.

[WillCodeForCats]

Also you do know the inverter can only take one connection at a time, if whatever iobroker is connected nothing else can connect.

[WillCodeForCats]

Converting to discussion because no evidence this is an integration issue.

[froggi1930]

Iobroker is simular to Homeassistant. This instance is offline, so no other program tries to reach the inverter.
As I am new to Homeassistant I do not know what to do extra except installing your solution... Do I need to configure Modbus seperately, or only through your config?
I can reach the Inverter from my Laptop on port 1502 and also read the values.

[WillCodeForCats]

If you're able to read modbus through other devices there's no reason this shouldn't work if the IP and port are the same.

Otherwise I don't really have any ideas why it would say failed to connect. Since you've tried another integration where those logs showed also can't connect the only thing that tells me is that it's not specifically a problem with my integration.

[CSH12]

Hi all,

Sorry for the delayed info, but had no time to respond this week earlier.

I encountered the error again today as I restarted the Home assistant.
Attached the requested diagnostic info and the log. If some more Infos are required, let me know

In my system there is no other device connecting to the modbus - just a single connection from home assistant.

To resolve the error I had to delete it again and reintegrate it.

home-assistant_solaredge_modbus_multi_2023-08-08T08-06-37.746Z.log
config_entry-solaredge_modbus_multi-e3d0a9ca86e2ff5a85c0a45012c00feb.json.txt

There is one more issue that is happening sometime. Some individual information (B1 Energy Export and Import, or Solar Production) are unavailable. But just some of them, all other ones are stable. So I don't know why. If I reload the integration it is working properly - strange.

[CSH12]

and actually just one entity is missing again

is this maybe some timeout detection related to the information is not getting update within a tiemespan or sth.?
seems that the information that are not updated frequently (night in germany, no solar production change) are detected as unavailable

[WillCodeForCats]

Night shouldn't change anything, mine don't change at night and just stay at the same value.

[WillCodeForCats]

What entity is that going unavailable? These are sensor.solaredge_i1_ac_energy_kwh and sensor.solaredge_i1_ac_energy_kwh on my system:

[CSH12]

just as an idea...
this is the only hint that I recognized that the not changing data are set to unavailable.
It seems to be all time the same ones: solar production or B1 Energy Import, Export

[WillCodeForCats]

B1 import and export energy are a known issue that they "go backwards" when they should be increasing only: Known-Issues#battery-energy

[john8329]

I'm having the same problem. The inverter becomes unreachable after restarting HASS. The only way to fix it is restarting the inverter. I presume it thinks there's an open connection and refuses any new one, remaining stuck in this state. Perhaps the integration is not closing the modbus connection properly on shutdown?

Here's the diags. Thanks for the component btw.
home-assistant_solaredge_modbus_multi_2023-09-11T19-12-08.957Z.log

[WillCodeForCats]

Propose what should be changed if you think the sequence is incorrect.

[WillCodeForCats]

This is the shutdown function if you suspect it is out of sequence:

    async def shutdown(self) -> None:
        """Shut down the hub and disconnect."""
        async with self._lock:
            self.online = False
            self.disconnect()
            self._client = None

    def disconnect(self) -> None:
        """Disconnect from inverter."""
        if self._client is not None:
            self._client.close()

The only restriction is that self.disconnect() has to come before self._client = None otherwise self._client.close() does not exist.

[john8329]

I confirm it's the inverter becoming stuck. Even if I keep HA off for an hour, it fails reconnecting, and I have to reboot it. Hope this info can help somebody out there.

[john8329]

Also wait. Isn't this an async client? I'm not extremely practical with async python, but shouldn't you await the close() call when disconnecting? Got it from here

[WillCodeForCats]

Close is not an async call since PR pymodbus-dev/pymodbus#1492 starting with pymodbus v3.3.0