[Bug]: Reading register 30000 error #940
Comments
|
Same error in my case, waiting to see if it is resolved |
|
Same error after upgrade 2025.2.21 |
|
Same here after Upgrade |
|
same, tried downgrading back to 2025.2.0, still same issue |
Did you tried also with "old" dependencies versions or you Just downgraded homeassistant? |
Hi just homeassistant (basically ha core update --version 2025.2.0) |
|
Same problem here, this is not my setup but a friend's, so I have limited opportunities to test if needed
2025-02-09 20:07:33.217 WARNING (MainThread) [pymodbus.logging] Failed to connect [Errno 113] Connect call failed ('192.168.1.19', 502) The above exception was the direct cause of the following exception: Traceback (most recent call last): |
|
Same issue here; I tried backup restore both partial (i.e. only HA) and full (including add-ons) back to 2025.1.9 and it's still not working |
|
Same issue |
|
Same issue. With downgrade to 2024.1.4 and Huawei Solar 1.4.1 all works fine |
Good catch! Homeassistant 2025.2.1 and integration 1.4.1 everything works fine! |
Great! Cofirm that with Homeassistant 2025.2.1 and integration 1.4.1 everything works fine! |
|
I confirm for me too. It works with 2025.2.1 and integration 1.4.1. Thanks |
|
Same issue on upgrading to integration 1.4.1 and HA Core 2025.2.1, inverter firmware V200R001C00SPC146, tried via WIFI AP (was working until now) and then tried enabling "Local O&M" and tried connecting via my own wifi, getting the same error: Reverted to HA Core 2025.2.0, no effect. Reverting integration to 1.4.1 fixed it, thanks for the tip! |
|
can confirm that reverting to integration version 1.4.1 fixed it |
|
The latest version of pyModbus that was released this weekend contains a regression which breaks all communication with devices with slave ID 0. I've created an upstream issue pymodbus-dev/pymodbus#2571 explaining what this regression is and what incorrect assumption has caused it. While we wait for the pyModbus maintainer to correct this issue, I've released v1.5.4 which blacklists the faulty pyModbus version. |
This comment has been minimized.
This comment has been minimized.
|
Hello, for me, the issue is fixed with version 2025.2.1 and the latest update of the integration (1.5.4). 🎉 |
This comment has been minimized.
This comment has been minimized.
|
Hello, @wlcrs if this integration will work with 2025.2.1 and with other native modbus integration. Because you wrote this solar version have pymodbus 3.8.5, and HA 2025.2.1 still using 3.8.3 ? |
|
pyModbus 3.8.6 has been released. This fixes the root cause of this issue. I'll unpin the pyModbus version on the next release of this integration. |
Describe the issue
After updating Homeassisstant to 2025.2.1 from 2025.2.0 integration shows error and everything is unavailable. Everything was working perfectly before that moment.
When I updated Homeassistant to latest version was nightime so no solar power from PV, only from batteries.
I also have installer password but seems i cannot connect to the inverter in any way, either from my wifi or to the inverter wifi. Inverter is up and running and sending infos to huawei cloud, everything is still visible from app and/or website
Describe your Huawei Solar Setup
Inverter Type: SUN2000-6KTL-L1
Inverter Firmware version: V200R001C00SPC130
sDongle present: Yes
sDongle Type: sDongleA-05 (WiFi / Ethernet)
sDongle Connectivitiy: WiFi
sDongle Firmware: N/A
Power meter present: single phase
Optimizers Present: Yes
Battery: LUNA2000-SO 2 x 5kWh
Battery Firmware version: V100R002C00SPC621
Huawei Solar integration version: 1.5.3
How do you connect to the inverter?
Via the SDongle, wireless connection
Upload your Diagnostics File
N/A
Upload your relevant debug logs
Please confirm the following:
The text was updated successfully, but these errors were encountered: