Integration Solar inverter huawei 2000L

MQTT support has now been added to v1.0.2.
That means PyFusionSolarDataRelay kan now forward FusionSolar Kiosk data to:

It’s quite easy to subscribe Home Assistant to the MQTT topics (if MQTT is implemented)
I’ll add some home assistant templates soon to show how you can subscribe to the MQTT topics for setting up the energy dashboards etc.

If anyone can’t wait and would like to provide some assistance: Here are the basics for another inverter type which need to be ported to the PyFusionSolarDataRelay data format.

2 Likes

Finally I got answer from Huawei Technical Support about the reason why it happens: the inverter works very inefficient (15%-20% losts) if its operation mode is only to follow the home energy demand , the proper configuration to get the optimal efficiency of the inverter is in the mode converting all the PV energy generated, it means injecting into the grid the energy not consumed into the home. I changed the inverter configuration and now it works with the correct efficiency.

Have you solved this issue? Which mode do you have configured your inverter?: following only the home energy demand or converting all generated PV energy?

See may comment, may be could help you if it is your case: link

Hi all,

I have followed good practice and (skim) read through the topic. Can I please check my understanding of how to join the party? For context I have a Sun2000 and a Luna 15KWh battery at home.

I have two wifi points, one is the connection to my home network (192.168.1.x) which is the connection that then goes on to populate my FusionSolar app information.

I also have the Sun2000 AP beaming away on 2.4Ghz.

In order to use this component to extract the data I need to bridge the two networks, 192.168.8.1 and 192.168.1.x.

Is that correct? After I have done that and can get my HA to see the inverter I am good to go?

Many thanks
John.

just start here:

Hi everybody!

A bit off-topic here as I think most of the conversation is geared towards getting the data directly from the inverter through WiFi, but I have just uploaded a configuration to get the data from the inverter using EPShome and Modbus RTU. This has been rock solid for me for as long as I have had it and is easier to setup than what one might think.

One thing to keep in mind is that you really need to put your wifi-router close to the Sun2000. The range of the Sun2000-Wifi is extremely low. I had my router in the same room as the Sun2000 (my garage) about 3 meter away and got lots of disconnects. Moving it to about 1-1.5 meters from the inverter, the connection is rock-solid. It has been up for over 22 days now.

1 Like

Could be. I never really tried the WiFi thing. I had already flashed the first version to the ESP before getting the inverter. Once I figured out the timings, I only have trouble when I try to “improve” the code. Otherwise it has been rock solid since easter (2 months already)

Hello all,

I have been using Emilv2s integration for a while and it’s been great, finally got everything working including the energy dashboard. However I upgraded the inverter because it kept dropping the management data and everytime I logged on it wanted me to upgrade so I finally let it… I knew it would break anything.

Anyways I’ve reread the thread and it seems they have left a port open on 6607, I didn’t see that port open but it’s high. I normally connect directly to the inverter wifi AP with a RasPi anyways…

Pictures attached



Few questions-

Can I read the data with Emilv2s integration by simply upgrading the inverter and changing the port to 6607 in config.yaml?

What is a smart dongle, not sure if I have/need one?

Should I update the MBUS version?

Is it better to use the other integration, test it out on this version that I know works then update the inverter and change the port to 6607?

Anything else I should know?

hey guys, such an amazing amount of work and content in this thread, thank you.
figured i’d ask here as maybe someone has a quick answer, i could not find it in the thread but there are 1700+ replies…
i am using https://github.com/wlcrs/huawei_solar and would like to get an ever growing sensor showing my house’s total energy consumption(kWh). the available data is

and
and i can’t for the life of me figure out how to get basically this from the energy panel
image
thanks again guys

Hi all. Forgive me for possibly going over something again, but I have set up Home Assistant from scratch in a VM, it’s searched for everything on my LAN and I realised that I couldn’t see my Huawei solar there despite the installer asking for my wifi password etc. I’ve therefore done some reading of this thread and worked out that I needed to use the internal Wifi of the inverter. I’ve gone out and bought a wifi bridge, configured HA with a second NIC with DHCP and received an IP address from the Huawei. I can ping the inverter from HA although it loses about 1 packet in 10 currently (that might be the siting of the wifi bridge or the inverter being too busy to ping, but I can troubleshoot that later).

At this point I think I’m ready to integrate an add-in to see/control the solar, but i’m not sure what I’m doing there - the start of this thread mentions Emilv2’s project which required me to install HACS (managed that) and then copy some files into a location (although a button on the component seemed to handle that for me) but now I’m not sure how to kick that project into life - I’ve edited the configuration.yaml file with my own inverter’s IP address, but still nothing’s popping into life and I’m not sure how to make it happen?

Also, the end of this thread mentions wlcrs’s project which seems to be different, but maybe what I want instead - i’m not sure? is one project more advanced than the other? do you need both to co-exist? and finally what do I do next?
(TIA!)

If you can ping your inverter, it sounds like you have managed the tricky part with bridging the networks!
You should really use the wlcrs-version https://github.com/wlcrs/huawei_solar.
Emilv2 is an old version, so remove that if you have it installed.
If you can reach your inverter, you should only need to configure the huawei_solar-integration and be good to go. You do not need any configuration in your .yaml-config. You configure with the UI.

Marvellous, thanks. Got it showing details now.
Is there a reason that “Daily Yield” doesn’t show the amount of kwh i’ve put into the batteries? I’ve filled my 10kwh LUNA2000 batteries in the 6 or so hours from sunrise to now, but Daily Yield is showing ~4kwh. Are there any customisations I should be considering to show accurate figures?
Also, someone mentioned above the temperature of the inverter - I don’t see that as a returnable figure?

Check the FAQ in the readme on github.
There is a section on:

The “Daily Yield” value reported does not match with the value from FusionSolar?

About the temperature, I think you can see the temperature if you have optimizers. Not the temperature of the inverter itself.

1 Like

Thanks - I won’t bother about the inverter temps as I don’t have any. I’m a total noob with HA though (but not with networking), so i’ve read the Daily Yield section and understand why it’s a flawed calculation but I have absolutely no idea what to do with the code snippets on that wiki page (Daily Solar Yield · wlcrs/huawei_solar Wiki · GitHub) - where do I put this?

Did you solve this @colseven, I am going through the same process myself.

So, good practice (i think) is to split your configuration.yaml into a few different files. I would suggest that you add these lines to the file configuration.yaml

sensor: !include sensor.yaml

template: !include template.yaml

utility_meter: !include utility_meter.yaml

Then create those 3 files. They can be empty for a start. If you already have a
template, sensor or utility_meter-block in you configuration.yaml, I think you have to remove those (and move the contents to the corresponding file.

In the template.yaml-file, you add

- sensor:  
  - name: "input_power_with_efficiency_loss"
    unique_id: "input_power_with_efficiency_loss"
    unit_of_measurement: "W"
    device_class: power
    state_class: measurement
    state: >-
       {% set inverter_rating = 3000 %} # adjust this value to the rated power of your inverter
       {% set inpower = states('sensor.input_power')|float(0) %}
       {% if inpower < (inverter_rating*0.1) %}
         {{ inpower * 0.90 }}
       {% elif inpower < (inverter_rating*0.2) %}  
         {{ inpower * 0.95 }}
       {% else %}
         {{ inpower * 0.98 }}
       {% endif %}

In the sensor.yaml-file, you put

- platform: integration
  source: sensor.input_power_with_efficiency_loss
  name: solar_energy_riemann
  round: 3

Now you can use the “solar_energy_riemann” as the sensor for measuring your solar panel yield.

You have to restart HA to see them. Make sure to use the “Check Configuration” under Development->YAML in the UI, to make sure you do not have any errors before restarting.

1 Like

Excellent, thank you very much - I’ll report back when I get that sorted.

So my sensor.yaml file looks like this now:

 - platform: huawei_solar   
    host: '192.168.200.1'
    optimizers: false
    battery: true
    slave: 1
    port: 6607
 - platform: integration
  source: sensor.input_power_with_efficiency_loss
  name: solar_energy_riemann
  round: 3

but I get the following from a Check Configuration. I must’ve screwed up the syntax but i’m not sure what the proper syntax should be for a yaml file:

Error loading /config/configuration.yaml: mapping values are not allowed here
in "/config/sensor.yaml", line 2, column 9

2 things. Not sure why you have the huawei_solar there? Is that left from the Emilv2, maybe?
Then, make absolutely sure that the indentation is correct.
The minus-character (-) in

- platform:
should start at the first column in the file.
The source, name, and so on should be exactly under the p in platform. In your copy (if it is not the forum reformatting), it looks like they are either to the left or to the right of the platform.