Integration Solar inverter huawei 2000L

Feature Requests
765

Does anyone have a similar reading case, it disrupts my monthly and annual readings, but not the total. It turns out that the error comes from pv_string_01_voltage

obraz

obraz

obraz

  - platform: template
    sensors:
      pv_string_01_power:
        friendly_name: "Huawei PV String 01 Power"
        unit_of_measurement: "W"
        device_class: energy
        icon_template: mdi:solar-power
        value_template: '{{ (states("sensor.pv_string_01_voltage")|float * states("sensor.pv_string_01_current")|float * 1) | round(0) }}'

Can such readings be avoided? What could it be from?
Calibration of the utility meter helps, but until the next wrong reading

766

I’m also getting wrong readings, that’s why I stopped using smart dongle and I’m connecting again to internal wifi AP. With internal AP I had never got any wrong readings.

1 Like
767

It turns out, however, that it remains to return to the topic of the router as a gateway via wifi or use the kiosk option

768

You can also modify template to accept only values between some range:

    pv_strin1_voltage:
      friendly_name: "Napiecie string 1"
      unit_of_measurement: 'V'
      value_template: >
        {% if state_attr('sensor.sun2000_8ktl_m0', 'pv_string_01_voltage') | float > 0 and state_attr('sensor.sun2000_8ktl_m0', 'pv_string_01_voltage')|float < 500 %}
          {{ state_attr('sensor.sun2000_8ktl_m0', 'pv_string_01_voltage') }}
        {% else %}
          0
        {% endif %}

Piszę z głowy więc nie jestem pewien czy składnia poprawnie.

769

In a my old configuration I had similar issue on an utility meter sensor based to template. This happened at HA restart.
I am not an expert but maybe it could be caused to the temporary unavailablity values of some sensor included into the template.

770

@ligeza which values you use in energy dashboard? Energy Management in Home Assistant - #929 by yousaf465
I have highlighted the same issue here.

771

I currently don’t use energy dashboard. I tested it but it is not useful for me.

772

https://github.com/home-assistant/core/pull/56564 this might fix spike reading issue in 2021.10.x
and this too https://github.com/home-assistant/core/pull/56609

773

I don’t know why, but for a few days I can’t connect to the dongle anymore.
I do a “ncmli device wifi” and it shows me SUN2000-HV20C0028779 for some time. Then it wifi AP disappears, and maybe reappear.
When I try to connect “nmcli d wifi connect SUN2000-HV20C0028779 password xxx” it gives me “Error: Connection activation failed: (53) The Wi-Fi network could not be found.” or after 1 minute or so “Error: Connection activation failed: (7) Secrets were required, but not provided.”

Any idea what’s going wrong here? It was working fine for the last 2 month since I got it. Dongle fw version seems to have auto-updated to v123

774

Hello, someone know how reduce the data collecting time ? Now with 30 secs I have problmens

775

hi from yesterday have a 2 strings of panels .in data I receive for any string power in A and Voltage for string .how is easiest way to calculculate sensor which show kwh or wh for string in that moment .like to see in real time separate for every string

Thanks

776

Hello

  1. /config/configuration.yaml

sensor: !include sensor.yaml

  1. /config/sensor.yaml

     - platform: template
     sensors:
       pv_01_power:
         friendly_name: "PV 01 Power"
         unit_of_measurement: 'W'
         value_template: >
           {{ '%0.2f' | format (states('sensor.pv_01_voltage') | float *  
                                        states('sensor.pv_01_current') | float ) }}

       pv_02_power:
         friendly_name: "PV 02 Power"
         unit_of_measurement: 'W'
         value_template: >
           {{ '%0.2f' | format (states('sensor.pv_02_voltage') | float *  
                                        states('sensor.pv_02_current') | float ) }}
777

save and restart HA :wink:

778

many thanks , pleas help me wit this line which going in configuration.yamal

can save them , all time is error message for this line

part in sensor.yaml is ok but for now no any numbers until I fix this part in configuration.yaml I think.

thanks on help

779

It is because you probably are using other sensors in configuration.yaml and sensor: include means that all you sensors will be in sensor.yaml file. If your sensors are in configuration files you can add it to sesnsor section:

sensors:
  - platform: template
      sensors:
        pv_01_power:
          friendly_name: "PV 01 Power"
          unit_of_measurement: 'W'
          value_template: >
            {{ '%0.2f' | format (states('sensor.pv_01_voltage') | float *  
                                         states('sensor.pv_01_current') | float ) }}
 
        pv_02_power:
          friendly_name: "PV 02 Power"
          unit_of_measurement: 'W'
          value_template: >
            {{ '%0.2f' | format (states('sensor.pv_02_voltage') | float *  
                                         states('sensor.pv_02_current') | float ) }}
780

Thanks lewusek0 and Rafal

Works like charm.

781

Hi, any way to modify the spript to reduce from 30 to 20 seconds ?

782

You don’t need to modify script, just add scan_interval in config like this:

- platform: huawei_solar   
  host: 192.168.8.1
  scan_interval: 20
783

Siema, potrzebuję pomocy, połączyłem się z HA i odczytuje dane, ale mam problem z dostosowaniem wyglądu, czy można się z Tobą jakoś inaczej skontaktować żeby nie denerwować użytkowników że nie piszę do angielsku? mój angielski jest bardzo słaby…

784

Thansk, wow… simple. Could be good if it is included in the doc as “option” in the configuration space