Repository navigation
Only SDongle aggregate registers (slave 100) reachable — SUN2000-10KTL-M1 via SDongleA-05, no inverter response on any other slave ID #1412
mendemar
started this conversation in
Connecting to the inverter
Replies: 2 comments 2 replies
|
Your SDongleA-05, firmware V100R001C00SPC133 is very old. Please update your sDongle to firmware V200R022C10SPC126 and test again ID1 on port 502. |
1 reply
|
My electrician carried out the update, but unfortunately I can still only see the dongle with ID 100; I can’t find any other IDs, and even with the latest update – software version V200R022C10SPC320 – there are only 5 aggregate sensors (total input/battery/active power, grid power, load power) |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Setup:
Inverter: SUN2000-10KTL-M1, firmware V100R001C00SPC174
Dongle: SDongleA-05, firmware V100R001C00SPC133
Connection: Modbus TCP, xxx.xxx.xxx.xx:502, home LAN (WiFi mode, dongle already joined to home WiFi — no local web UI reachable on port 80/443 from LAN, connection refused)
HA huawei_solar integration version: 2.1.2
What works:
Slave ID 100 connects fine and returns the SDongle's own aggregate sensors (total input/battery/active power, grid power, load power) — this is my existing working config entry.
What doesn't work:
Slave IDs 0, 1, 2, 3, 101, 201 all either fail to connect outright, or (after ruling out a connection-limit conflict with another Modbus client) return "Connected... but no Huawei Solar device responded on slave ID X."
A third-party device (MY-PV AC ELWA-2, via its own "Huawei Modbus TCP Manual" control mode) successfully talks to the same host:port using slave ID 1 for its own power-control purposes — so slave ID 1 clearly responds to something, just apparently not to the register set/identification read that huawei_solar's config flow expects.
Question: Is there a known additional step (e.g. "Unrestricted Modbus TCP" mode mentioned in the wiki) needed for the SDongleA-05 to expose full inverter registers over LAN, beyond just picking the right slave ID? Or does the presence of a third-party "regulation device" connection (MY-PV) on slave ID 1 permanently claim that ID for control-only use, blocking normal telemetry access to the inverter itself?
All reactions