[Bug]: The connection only works once after a restart

[psi33]

Describe the issue

First of all, many thanks for this ingenious integration. Unfortunately, it only works once for me and is not stable. After restarting the integration, all data is correctly retrieved from the inverter via the network.

If I try to connect again, the values are no longer updated. This is clearly visible in the log.

A second home server also accesses the same interface via the network. This shows that the connection to the Modbus interface is working.

For a test, I ended this second query so that the Home Assistant has unrestricted sole access. Unfortunately, this did not result in any improvement and the values are only read in once after a restart. Why does the integration crash?

Thank you for your help

Describe your Huawei Solar Setup

Inverter Type: SUN2000-10KTL-M1
Inverter Firmware version: V100R001C00SPC162
sDongle present: Yes
sDongle Type: sDongleA-05 (WiFi / Ethernet)
sDongle Connectivitiy: Ethernet
sDongle Firmware: V100R001C00SPC335
Power meter present: three phase
Optimizers Present: No
Battery: None
Huawei Solar integration version: None

How do you connect to the inverter?

Via the SDongle, wired connection

Upload your Diagnostics File

Drag & Drop your Diagnostics File here.
config_entry-huawei_solar-01JFN1QA6R2EV2RNH153ECHFY9.json
Log.txt

Upload your relevant debug logs

[Log.txt](https://github.com/user-attachments/files/18246644/Log.txt)

Please confirm the following:

• I'm running the latest release of Home Assistant.
• I'm running the latest release of this integration.
• I did not find an existing issue describing this problem.
• I did upload the diagnostics-file that I could retrieve from the 'Devices & Services Page'
• I did upload the relevant debug logs (via 'Enable Debug Logging'-feature or by manually configuring HA logging)

[NBOnGithub]

I'm seeing the same behaviour for the past week. Any restart of home assistant gives me a single snapshot value for the battery status and inferior power, etc. and nothing further. Command actions still seem to take effect as I can manage to change the charge from grid settings via automations.
Previous to this week the integration has been working flawlessly.
I've tried resetting the solar system by turning off the power to it but this has not fixed it either

[Mav70]

@psi33 I'm also seeing the same issue for the past couple of days. Any update on a resolution?

[NBOnGithub]

I eventually removed the integration and also removed the download from hacs. Then I rebooted and reinstalled and it started working again.
It might be getting something corrupt on disk that it is then failing to reload properly.
Note that I did need to do a second reboot to fix the automation warnings.

[psi33]

Thx @NBOnGithub
I have deleted the integration and also deleted it in HACS. Then restarted HA. Added the integration (1.5.0a1) again. It has improved and works for about 10 queries, but even after that the integration crashes. Does anyone have an idea where this could be

[Mav70]

@psi33 @NBOnGithub I've also tried to delete and reinstall but with the same results as before. What I have noticed though is that sometimes the inverter isn't responding to pings (I connect via wifi) although I can access it fine through the app. The wifi connection at the inverter side seems to go into a "sleep" mode.

[psi33]

@NBOnGithub und @Mav70
I connect via a fixed network cable. I have just tested it again. After restarting the integration (1.5.0a1), I get 20 measuring points from the inverter. Then the integration crashes without a log entry and does not send any further data. In all this time I have not lost a single ping. So I think we can rule out the inverter and the network connection. What else can we test or adjust? Does anyone have an idea?

[psi33]

Unfortunately, the new HA version 2025.1 does not bring any improvement. I think only the developer can help us here. I hope for feedback

[fehlerteufel]

I have a similar issue (worked fine before updating HA and the integration yesterday). Data from the inverter is updated normally, but data from the additionally connected power meter is only updated once after restarting the integration.

[WILHER]

I have the same Problem. After reboot ist works für a couple of seconds than it crash

[fehlerteufel]

Reverting the Huawei Solar Integration back to version 1.3.3 solved the problem for now. I'm happy to help in resolving the problem with version 1.4.1, please ping me if I can support in some way.

[psi33]

Unfortunately, installing version 1.3.3 does not help me. The data is updated for 5 minutes and then the interface crashes.
I also hope for a solution soon and will gladly support you in testing and reporting.

[psi33]

@wlcrs
What does this mean for me if the entry was migrated from Issue to discussion?

[psi33]

Hi @wlcrs
First and foremost, I would like to sincerely thank you for your outstanding work on this integration. It is of great value to us, and we truly appreciate your effort and dedication.

Some time ago, you converted my issue into a discussion, for which I am also grateful. However, we have not received any further updates regarding the next steps since then.

It would be very helpful for us to know if the reported issue might be due to a bug in the interface or if there is a workaround we could apply. I would greatly appreciate it if you could provide us with a brief update on how to proceed.

If additional time and effort are required to achieve a working solution, I want to let you know that I am willing to support this financially as well.

Thank you very much in advance for your time and assistance. I look forward to hearing from you.

Best regards,
Peter

[psi33]

@wlcrs
I have installed 1.5.3 and unfortunately the integration is still not working. How can I support you, I would like to help?

@WILHER and @fehlerteufel
Have you also installed it, how does it look for you?

[WILHER]

I also installed 1.5.3, unfortunately the same problem.
The connection is established after a restart for approx. 1 minute and goes into "not available"

[psi33]

I immediately installed 2025.2.0 today, unfortunately the connection is also started here and after a minute “not available” appears. It's a pity that we never hear a word from the developer @wlcrs about the next steps and whether we can provide support. :-(

[amaduain]

I immediately installed 2025.2.0 today, unfortunately the connection is also started here and after a minute “not available” appears. It's a pity that we never hear a word from the developer @wlcrs about the next steps and whether we can provide support. :-(

Sadly this is also my case, @psi33 sometimes the open source world can be frustrating, but @wlcrs has been working to fix this modbus version compatibility hell, so let's give him some kudos and then help him to continue moving forward.

As I said, I'm in the same place, when I try to install the new module 1.5.3 over HA 2025.0 it says it can't connect.
In my case I'm using a Protoss PW11 TCP/Modbus adapter, and I can see the connection on the admin web page, but the counters are not going up, so it seems that the integration is not seeing that is really connected:

So I tried to use the python library that also was maintained by @wlcrs : https://pypi.org/project/huawei-solar/

After creating and environment, the following code is working:

`pip3 -m asyncio

import asyncio
from huawei_solar import AsyncHuaweiSolar, register_names as rn
slave_id = 1
client = await AsyncHuaweiSolar.create("192.168.8.123", 502, slave_id)
result = await client.get(rn.NB_PV_STRINGS, slave_id)
result
Result(value=2, unit=None)

`
So that is working, from the same host that HA is installed, and I can see that the TCP adapter is receiving and querying the modbus correctly:

Also note that the other connection from the HA to connect via Huawei module is still there.
Anyway, if you need more feedback or testing let me know, but it seems that cover this use case will take a while.

[N1ckn4m3sN3t]

Same Problem for me - then i changed connection to SUN2000-xxx instead of SDongle and seems that's working with described settings:

"When connecting to the inverter AP the host IP is typically 192.168.200.1 and the slave id is typically 0"

[persching1978]

I use the connection of my SUN2000-xxx and not the SDongle connection, but it's not working with huawei solar V1.5.3 and HA2025.2.1.
So there seems to be another difference that you can successfully connect and others can't. I use currently huawei solar V1.4.1 and this is working stable for me.

[N1ckn4m3sN3t]

After the initial problems, I tested the fork https://github.com/tmenguy/huawei_solar, but it didn't work with that either. Then I went back to the original integration and since then (about 2h^^) it works great.

SUN2000-8KTL-M101074300-002
Firmware: V100R001C00SPC153

Home Assistant
Core 2025.2.1
Supervisor 2025.02.0
Operating System 14.2
Frontend 20250205.0

Huawei solar 1.5.3

[persching1978]

I have a SUN2000-10KTL-M1 with Firmware V100R001C00SPC167 and the MBUS Firmware V100R001C00SPC335. Maybe there is the difference if it's working with 1.5.3. But before HA2025.1.0 I used Huawei Solar V1.5.3, but I have to try it often to start the integration. Once started it works if I do not restart HA...

[psi33]

@wlcrs
I have installed HA 2025.2.3 and Huawei 1.5.4. The connection works and the data is read in correctly. But after about a minute, unavailable appears. My setting is shown in the first post.

How and with what information can I provide support?
Is there an alternative to Huawei Solar if this inverter is not supported?

I am grateful for any advice.

If this integration runs stably for a month, I will also be happy to donate a sum of money