Integration Solar inverter huawei 2000L

how i can retrieve all the attribute from the inverter?
i don’t use modbus because i’vbe undestand that i can only use one connection at time: platform or modbus right?

Can you try read data using python?

sudo pip3 install huawei-solar==1.1.0
python3
import huawei_solar
inverter = huawei_solar.HuaweiSolar('192.168.1.13',502,5,3,1)
inverter.get("model_name")

Hmm it really seems that the inverter is not listening to modbus at all, maybe they disabled the modbus again in this new version??

As far as I know SPC123 should work correctly. Maybe there is another device connected. Did you try from other PC? Maybe something is blocking traffic on this port.

Very strange, i’ve indeed checked from the home assistant host and an virtual ubuntu on my laptop and the same results it cannot connect.

This evening I had a time to get close to the inverter (it is at our new house still in construction) and I connected my laptop to the SUN2000 wifi. Then doing your command I managed to get output.

afbeelding
Thanks for the tip, i’ll see if I can rule out that some other “thing” is connecting to modbus by putting the rj45 cable direct in my laptop. Just have to find an ethernet to usb cable since these new laptops don’t have rj45 anymore :stuck_out_tongue:

OK So far I have benefited from your help. Now maybe I can help someone.
I attach a configuration entry containing all the most necessary entities with solar production data.
modbus:

  • name: Solar
    type: tcp
    host: 192.168.3.182 (change to the IP address of your inverter)
    port: 502
    sensors:
    • name: active_power
      slave: 1
      address: 32080
      unit_of_measurement: W
      data_type: int
      count: 2
      scale: 1
      precision: 1
      scan_interval: 10
    • name: input_power
      slave: 1
      address: 32064
      unit_of_measurement: W
      data_type: int
      count: 2
      scale: 1
      precision: 1
      scan_interval: 10
    • name: day_active_power_peak
      slave: 1
      address: 32078
      unit_of_measurement: W
      data_type: int
      count: 2
      scale: 1
      precision: 1
      scan_interval: 10
    • name: pv_01_voltage
      slave: 1
      address: 32016
      unit_of_measurement: V
      data_type: uint16
      count: 1
      scale: 0.1
      precision: 2
      scan_interval: 10
    • name: pv_01_current
      slave: 1
      address: 32017
      unit_of_measurement: A
      data_type: uint16
      count: 1
      scale: 0.01
      precision: 2
      scan_interval: 10
    • name: pv_02_voltage
      slave: 1
      address: 32018
      unit_of_measurement: V
      data_type: uint16
      count: 1
      scale: 0.1
      precision: 2
      scan_interval: 10
    • name: pv_02_current
      slave: 1
      address: 32019
      unit_of_measurement: A
      data_type: uint16
      count: 1
      scale: 0.01
      precision: 2
      scan_interval: 10
    • name: phase_A_voltage
      slave: 1
      address: 32069
      unit_of_measurement: V
      data_type: uint16
      count: 1
      scale: 0.1
      precision: 2
      scan_interval: 10
    • name: phase_B_voltage
      slave: 1
      address: 32070
      unit_of_measurement: V
      data_type: uint16
      count: 1
      scale: 0.1
      precision: 2
      scan_interval: 10
    • name: phase_C_voltage
      slave: 1
      address: 32071
      unit_of_measurement: V
      data_type: uint16
      count: 1
      scale: 0.1
      precision: 1
      scan_interval: 10
    • name: phase_A_current
      slave: 1
      address: 32072
      unit_of_measurement: A
      data_type: int
      count: 2
      scale: 0.001
      precision: 3
      scan_interval: 10
    • name: phase_B_current
      slave: 1
      address: 32074
      unit_of_measurement: A
      data_type: int
      count: 2
      scale: 0.001
      precision: 3
      scan_interval: 10
    • name: phase_C_current
      slave: 1
      address: 32076
      unit_of_measurement: A
      data_type: int
      count: 2
      scale: 0.001
      precision: 3
      scan_interval: 10
    • name: accumulated_yield_energy
      slave: 1
      address: 32106
      unit_of_measurement: kWh
      data_type: int
      count: 2
      scale: 0.01
      precision: 1
      scan_interval: 10
    • name: daily_yield
      slave: 1
      address: 32114
      unit_of_measurement: kWh
      data_type: int
      count: 2
      scale: 0.01
      precision: 2
      scan_interval: 10
3 Likes

Hi, Thanks for sharing your experiences. After reading them through I’ve decided to upgrade my SDongleA-05 firmware.

After upgrading to V100R001C00SPC123 I can make connection to modbus via ethernet and what’s more interesting - via Wi-Fi also (the dongle is connected to my main router).

Can someone share V100R001C00SPC123 firmware?

Cześć, jakiego routera (model) używasz do połączenia z ap falownika? Mam podobną sytuacje z umiejscowieniem falownika, a ha mam postawione na proxmoxie w zupełnie innym miejscu.

I can not see this version in the Huawei website. Last public for V100R001 is V100R001C00SPC600
What’s the difference between V100R001 and V200R001 (mine) ?

OK, since we have several power outtages lately and the LUNA battery doesn’t come until 2 weeks from now.
How do you restart your inverters so you can connect from HA again?
Do I relly need to turn off AC-> Turn off DC - > Wait at least 30 sec → Turn on DC → Turn on AC

Isn’t there a better way to clear the connection?

Do wczoraj używałem tp-link wr841n z DD-WRT (aby był AP klient ) o ile dobrze pamiętam, ale robiłem migrację z LXC na LXD to podpiąłem na razie kabelkiem LAN.

Cześć zrobiłem Bridge przez starego tplink, falownik jest połączony z moją siecią, ale nie wiem jak dalej z nim rozmawiać z HA. W integracji wskazałem na adres tego routerka ale dalej się nie komunikuje. Tego MAC adresu również nie widzę w mojej sieci… Nie pytał mnie również o hasło…
co jeszcze powinienem sprawdzić / zrobić?


obraz
obraz

W konfiguracji routera raczej ci nie pomogę, ale falownik ma zazwyczaj Ip 192.168.8.1 lub 192.168.200.1. Nie wiem dokładnie jak działa bridge w oryginalnym sofcie tp-link, ale na dd-wrt falownik mam jaką odrębną podsieć i do karty sieciowej z HA przypisany wirtualny adres z podsieci falownika. Wcześniej opisywałem już tą konfigurację, również inna osoba opisywała inny sposób konfiguracji bridge w tym wątku.

Hi
This is the file for MODBUS in Hassio integration , that I created for SUN2000L V2, where the slave is in position “0” I added some other parameters only for one stream and optimizers

Im working to import data optimizers

1 Like

I can confirm. Now I don’t need LAN cable. With firmware SPC123 I can connect directly to smart dongle and read data with slave: 1

Can anyone help creating template for Luna battery?

I mean the sensor

There are any way to make work this integration by the connection to slave 0 ? I tried to make work only by modbus integration, but when I setup this integration Solar Inverter huawei 2000L, everything apperas disconnected (modbus data commented)
My inverter is conected to my router in IP 192.168.31.92, and I setup this IP and Slave 0

Now you are using modbus integration. Only one connection is allowed so if something is connected, then integration from Emilv2 will not work.

Ok, is solved… I created a template sensors add to the main integration and those sensors are not working, but… the main integration is here… and I did’t see… simple concetp mistake…

I’m living in spain. The “Irleand” value is collected from the inverser or in huawei app. ?
Another question… There are some beautiful card to use for this integration ???

Edited: sensors were not working because were defined as sensor.sun2000_6ktl_m1, and mine is sensor.sun2000_6ktl_l1 now all is working