Random disconnects after firmware upgrades on SUN2000-4.6KTL-L1 inverter

[MonYvel]

Hi,

First I want to say: Huge thanks for the creation & support on this integration!

I'm sorry if this issue is already handled in an other discussion. But my issues are a bit different then mentioned in other similar discussions. If I'm wrong, please point me to it & I will share my details there.

Describe the issue

Unfortunately I'm having random disconnects since I've upgraded the firmware on the inverter, DC Modbus & batteries last weekend.

The connection always fixes itself after a few minutes. I don't need to reinitialize the integration like I've seen in some other discussions.

anybody else experiencing this after upgrading to the above mentioned firmware's? Can I provide you with more information to help me troubleshoot this?

Describe your Huawei Solar Setup
Inverter Type: SUN2000-4.6KTL-L1
Inverter Firmware version: V200R001C00SPC146
sDongle present: No
MBUS PLC DC Firmware: V100R001C00SPC335
Power meter present: Yes
Optimizers Present: No
Battery: Yes
LUNA2000 batteries firmware: V100R002C00SPC624
Huawei Solar integration version: 1.5.3

How do you connect to the inverter?
Via the IP with which the inverter is directly connected to your home network connection.

Debuglog

2025-02-04 10:43:31.062 INFO (MainThread) [backoff] Backing off _do_read(...) for 16.0s (huawei_solar.exceptions.ConnectionInterruptedException: Modbus client is not connected to the inverter)
2025-02-04 10:43:32.318 ERROR (MainThread) [custom_components.huawei_solar] Timeout fetching TA2220028785_inverter_data_update_coordinator data
2025-02-04 10:43:35.233 ERROR (MainThread) [custom_components.huawei_solar] Timeout fetching TA2220028785_power_meter_data_update_coordinator data
2025-02-04 10:43:51.332 ERROR (MainThread) [huawei_solar.huawei_solar] Timeout while waiting for connection. Reconnecting
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/asyncio/tasks.py", line 507, in wait_for
    return await fut
           ^^^^^^^^^
  File "/usr/local/lib/python3.13/asyncio/locks.py", line 213, in wait
    await fut
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/huawei_solar/huawei_solar.py", line 141, in _communication_lock
    await asyncio.wait_for(
    ...<2 lines>...
    )
  File "/usr/local/lib/python3.13/asyncio/tasks.py", line 506, in wait_for
    async with timeouts.timeout(timeout):
               ~~~~~~~~~~~~~~~~^^^^^^^^^
  File "/usr/local/lib/python3.13/asyncio/timeouts.py", line 116, in __aexit__
    raise TimeoutError from exc_val
TimeoutError
2025-02-04 10:43:51.335 ERROR (MainThread) [custom_components.huawei_solar] Timeout fetching TA2220028785_battery_data_update_coordinator data
2025-02-04 10:45:56.809 ERROR (MainThread) [homeassistant] Error doing job: Fatal error: protocol.data_received() call failed. (None)
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/asyncio/selector_events.py", line 1019, in _read_ready__data_received
    self._protocol.data_received(data)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
  File "/usr/local/lib/python3.13/site-packages/pymodbus/transport/transport.py", line 304, in data_received
    self.datagram_received(data, None)
    ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/pymodbus/transport/transport.py", line 338, in datagram_received
    cut = self.callback_data(self.recv_buffer, addr=addr)
  File "/usr/local/lib/python3.13/site-packages/pymodbus/transaction/transaction.py", line 183, in callback_data
    self.response_future.set_result(pdu)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^
asyncio.exceptions.InvalidStateError: invalid state
2025-02-04 10:45:56.831 ERROR (MainThread) [huawei_solar.huawei_solar] Modbus client is not connected to the inverter
NoneType: None
2025-02-04 10:45:56.832 INFO (MainThread) [backoff] Backing off _do_read(...) for 1.0s (huawei_solar.exceptions.ConnectionInterruptedException: Modbus client is not connected to the inverter)
2025-02-04 10:45:57.833 ERROR (MainThread) [huawei_solar.huawei_solar] Modbus client is not connected to the inverter
NoneType: None
2025-02-04 10:45:57.833 INFO (MainThread) [backoff] Backing off _do_read(...) for 2.0s (huawei_solar.exceptions.ConnectionInterruptedException: Modbus client is not connected to the inverter)
2025-02-04 10:45:59.834 ERROR (MainThread) [huawei_solar.huawei_solar] Modbus client is not connected to the inverter
NoneType: None
2025-02-04 10:45:59.835 INFO (MainThread) [backoff] Backing off _do_read(...) for 4.0s (huawei_solar.exceptions.ConnectionInterruptedException: Modbus client is not connected to the inverter)

[MonYvel]

Update from my end:

I think I got this fixed, basically I'm an idiot & RTFM was needed...

So I tried a few different things: Changed the polling rate, spun up a HA VM with a direct Wifi connection to the Huawei inverter (Option A of connection.)

Unfortunately nothing changed the behaviour. All caused random disconnects.

Updating to the latest version, 1.5.4 also did not fix this issue.

After this I was at a loss & went trough the wiki again: stumbled on this section:

https://github.com/wlcrs/huawei_solar/wiki/Connecting-to-the-inverter#troubleshooting-sporadic-dongle-disconnects

If you are connecting to the inverter via the Dongle connected to your home network (option B) and have the problem of sporadic but somewhat regular disconnects of about 30 minutes: the solution is to completely restarting the inverter by first turning off DC power and then AC power.

So yesterday morning I performed a full restart of the inverter & batteries (switching of DC power, batteries & AC power) waited a few minutes and turned everything on.

Connection is stable ever since... So seems fixed!

If I can make one small comment: The sporadic disconnects also happend with connection option A, not only option B as mentioned in this wiki...

Anyway. Thanks for the detailed Wiki & all the effort made to get this integration working!!

[MonYvel]

I spoke to soon...

The issue is back.... connection was stable for almost a week but yesterday started to toggle again.

Maybe the connection with the cloud is unstable? referring to this part of the wiki?

When the dongle is unable to connect to the Huawei FusionSolar cloud (for example due to a service or network outage), it will periodically restart in an attempt to restore connectivity. This will also interrupt the connection to this integration.

I will try setting up an OPTION A connection, to test if this is more stable.

Strange that I never had issues before updating the firmware on the inverter a few weeks ago...

If anybody can give some extra insight, that would be nice! Thanks!

[MonYvel]

OK. Update time. (I get the feeling I'm writing a monolog here...)

I spun up a Home Assistant VM with a wifi card directly connected (my main HA is a docker, so unable to connect a Wifi card to this.)

Disabled the Huawei_Solar integration on my main HA instance & configured it for OPTION A on the HA VM with Wifi dongle.

Connection went flawless & as stated in the wiki, the connection to the ModBus seems far more stable. Unfortunately it does still disconnect from time to time (minimum once per day.)

Now, I would like to troubleshoot if the issue is with the ModBus of with the wifi connection to the inverter. Does anybody know where I can find the logs about the wifi connection? I'm not that familiar with Home assistant... If the issue is with Wifi I will look for a Wifi router I can flash DD-WRT on so I can connect via the network. If the issue is in the inverter... Well, I'm at a loss.

Something else I notice: For some reason, since connected via OPTION A, the connection to the fusion solar cloud is very bad, with regular disconnects... Or maybe the servers at Huawei are having issues? Anybody else noticing gaps in their Fusion Solar portal graphs the last few days?

Anyway. Tomorrow I'm going to try to update the Batteries to firmware 629, Mine are currently on version 624.

I still don't understand why I'm having these issues since upgrading to the "latest" firmware.. I ran OPTION B for wel over 6 months dead stable before...