[Bug]: Solis - S5-EH1P3.6K-L "Timed Charge / Discharge Current" update breaks communication

[AKlamaznikovs]

Describe the bug

When changing "Timed Charge Current" or "Timed Discharge Current", the Modbus communication stops. On integration reload / home assistant restart, the communication is up and running again, and the current value actually changes / updates to the value set prior to restart.

Integration Version

2024.08.9 (previous as well)

Homeassistant core version

2024.8.2

Inverter brand

Solis

Plugin used

plugin_solis.py

Serial prefix

603102

Connection Method

Waveshare RS485 to WiFi/Ethernet Module

Detailed Error Log

Nothing in Home Assistant Core logs.

Additional context

I am aware that the WiFi version of Waveshare is not recommended. However, I have had 0 issues with reading data - connection is stable, I have tried various polling rates (1s, 5s, 15s, 20s) - they all work as intended and I don't think the issue is related to the hardware, but might be wrong. Currently, the Waveshare is connected to Home Assistant via Ethernet connection (rather than WiFi). Issues persist in both connection arrangements.

[AKlamaznikovs]

Haven't experienced any problems since 2024.08.10 release, will keep monitoring

[jevburchell]

I'd like to second this bug - I am seeing similar behaviour. I lose Modbus connection, with the only way to restart data flow being an HA reboot. I see this behaviour when making alterations to number input entities in Solax - it seems to happen on quite a few of them, but I have not tested them all. Confirmed Modbus loss after altering the following:

• Solax Solis Timed Charge Current
• Solax Solis Timed Discharge Current
• Solax Solis Energy Storage Control Switch

When Modbus loss is encountered, I see the following error:

During this time, if I try to reload the integration, it displays "initialising" but it never reloads. All entities become unavailable.

Reloading all YAML has nil effect. A full HA reboot allows everything to restart normally.

I'm running HA on an Odroid N2+ 4GB with a networked wireless connection to an Elfin EW11.

Thank you in advance for considering this issue

[AKlamaznikovs]

I'd like to second this bug - I am seeing similar behaviour. I lose Modbus connection, with the only way to restart data flow being an HA reboot. I see this behaviour when making alterations to number input entities in Solax - it seems to happen on quite a few of them, but I have not tested them all. Confirmed Modbus loss after altering the following:

* Solax Solis Timed Charge Current

* Solax Solis Timed Discharge Current

* Solax Solis Energy Storage Control Switch

When Modbus loss is encountered, I see the following error:

During this time, if I try to reload the integration, it displays "initialising" but it never reloads. All entities become unavailable.

Reloading all YAML has nil effect. A full HA reboot allows everything to restart normally.

I'm running HA on an Odroid N2+ 4GB with a networked wireless connection to an Elfin EW11.

Thank you in advance for considering this issue

Just to check, what version of the Solax Integration are you using? As mentioned above, this has been resolved for me since 2024.08.10. From release notes, looks like the removal of await self.async_connect() has fixed it.

[jevburchell]

Just to check, what version of the Solax Integration are you using? As mentioned above, this has been resolved for me since 2024.08.10. From release notes, looks like the removal of await self.async_connect() has fixed it.

Ok, I have just updated now to 2024.08.13, (was on .08). Let me also monitor and report back. Thanks for the heads up!

[wills106]

Can I close this issue down now?

[jevburchell]

Can I close this issue down now?

I've seen no more errors of this type, integration behaviour normal. Thank you Wills for your fine work 👌🏼