Integration Solar inverter huawei 2000L

People without Dongle :


For Option A or without Dongle, HA needs to be connect to your Home Network (eg 192.168.1.X) AND Inverter AP (192.168.200.101).

So HA needs to run on a Host with 2 network interfaces
(eg RPI : LAN = Home Network / Wifi = Inverter AP)

Or you need to Bridge the 2 Networks together (eg router/AP), so HA can access both at the same time.

Thx… No if i connect directly to Inverter there is open port 6607 fine…
But i can not connect with dongle… I enabled in the inverte but nothing.
If i go into the dongle setup i can not see the new firmware

Option A is the preferred/most stable one…
So forget about connecting to the dongle and make HA accessible to both your Home Network and Inverter AP…problem solved (and preferred one)

NOw looks like something happened…
I have an another ip : 192.168.1.194 it is Wifi…
Here is opne the 502 port and here is an error message in HA
2022-03-13 11:59:28 ERROR (SyncWorker_4) [homeassistant.components.modbus.modbus] Pymodbus: SolarSun2000: Modbus Error: [Connection] ModbusTcpClient(192.168.1.194:502): Connection unexpectedly closed 0.025822 seconds into read of 8 bytes without response from unit before it closed connection

What now?
thx

One IP is from the Dongle the other one is from the Inverter build-in Wifi.
As I stated before : Option A is the most stable one.
But it’s your choice to persue the other options…

Tnank you
So i have checked the ips
Now: 194 is the dongle wifi
195 is the dongle lan port
Sorry… I am not an expert… I try something…
I really don’t understand…
I can ping the 194 and there is an open port 502.
Sorry guys… If somebody can help me step by step what i miss take… messenger
Facebook
https://www.facebook.com/farkas.szilard.96
Thx

many thanks 4 your lovelace code wlcrs, I think rikerik used apecharts too :slight_smile: .

first (pie) graph here:

type: custom:apexcharts-card
chart_type: pie
header:
  show: true
  show_states: true
  colorize_states: true
  title: Energy by Source
apex_config:
  chart:
    height: 300px
  legend:
    show: false
  dataLabels:
    enabled: true
    formatter: |
      EVAL:function(value) {
        return value.toFixed(1) + "%";
      }
series:
  - entity: sensor.pv_today_yeld_kwh_energy
    name: PV Energy
    color: green
    float_precision: 2
  - entity: sensor.battery_day_discharge
    name: Battery Energy
    color: orange
    float_precision: 2
  - entity: sensor.gg_grid_consumption_kwh
    name: Grid Energy
    color: red
    float_precision: 2

second graph here:

type: custom:apexcharts-card
header:
  show: true
  show_states: true
  colorize_states: true
  title: Power Flows
graph_span: 24h
span:
  start: day
apex_config:
  chart:
    type: area
  stroke:
    show: true
  dataLabels:
    enabled: true
  legend:
    show: false
  fill:
    type: gradient
    gradient:
      shadeIntensity: 1
      opacityFrom: 0.01
      opacityTo: 0.5
      inverseColors: true
  grid:
    show: false
all_series_config:
  type: area
  opacity: 0.2
  stroke_width: 1
  group_by:
    func: last
    duration: 5m
series:
  - entity: sensor.power_grid_kwp
    name: Grid Pw
    color: red
    extend_to_end: false
    transform: return x / 1000;
    unit: kW
    float_precision: 2
  - entity: sensor.total_house_kwp
    color: blue
    extend_to_end: false
    name: House Load Pw
    transform: return x / 1000;
    unit: kW
    float_precision: 2
  - entity: sensor.power_batt_disch_kwp
    name: Battery Pw
    color: yellow
    extend_to_end: false
    transform: return x / 1000;
    unit: kW
    float_precision: 2
  - entity: sensor.input_power
    color: green
    extend_to_end: false
    name: FV Pw
    show:
      extremas: time
    transform: return x / 1000;
    unit: kW
    float_precision: 2

1 Like

sometime (maybe inverter, meter or HA loose connection each other) I’ve a out range value in 2 sensors:
sensor.grid_consumption
sensor.grid_exported


to avoid that I’ve by template filtered sensors value > 1milionkWh :).
There’s another way to avoid that wrong value?

I reported ealier that I was not able to connect to the dongle. After a lot of contact with the helpdesk and after they reviewed my logs, I today recieved this answer:

Modbus-TCP can be enabled locally only on M1, M2, and L1.

It will be supported by the end of April on M0.

So for all who are experiencing the same issue, a solution should come in 6 weeks from now.

I have 8ktl-m0 and firmware 123 in smart dongle. I can connect to inverter using modbus-tcp by LAN, connecting directly to inverter AP wifi and by connecting to smart dongle wifi. All three methods working for me.

I know there are more people who managed, but I tried all and could not find an open port. And the Huawei helpdesk concluded the same, so must be some truth in there. My type is: SUN2000-5KTL-M0 there might be different hardware versions.

I had this problem only with 140 firmware in inverter. All ports was closed and I had to go back to 139 firmware. I know other person that also had this problem with 140 firmware but after updating it to 141 it worked correctly. But this is only problem with inverter internal wifi. Smart dongle has its own firmware.

I also have 140 in the inverter and I have 127 on the dongle. But I cannot get contact via the dongle wifi, I did not tried via the inverter itself, while it’s to far off. I might need to try with a bridge, but I prefer to use the dongle.

How to update the dongle?

best is to ask huawei helpdesk

Hey Michele, can you increase the logging level of the integration (cfr. last point in the FAQ), and create an issue with the output you are seeing around the time that such a strange value is being reported?

You can either create a GitHub issue with that output, or you can send me a DM here.

1 Like

I am using SUN2000-6KTL-M0 and modbus-tcp is still working fine for me since it was introduced long time ago (in recent firmware I had to enable it, but I never had any problems with this, besides a performance)…

Hello everybody

(sorry my english :grin:)

In 2 weeks they will install my solar system with inverter and Huawey battery …
I have been reading this post for a long time in anticipation of being able to use it on my system.
I found many really interesting things, but they are very fragmented along this really very long post … I thought that perhaps it would be useful for many (certainly me too) to be able to start from a guide referring to one of the many projects adopted so that at least there is a starting point to then at least have only questions related to a specific problem inherent in that project, perhaps in this way you could eliminate many questions, sometimes repetitive …
What do you think…

Thanks again to everyone for the support you give, but I will definitely be back for some clarification

1 Like

I’ve opened the Wiki on my GitHub project. I do not plan to solely maintain it, so all contributions are welcome (and needed!) to make this a success.

@serbat feel free to create a “Getting Started” guide on this Wiki.

Hi Michele, i have had similar results several times, I have found in my case it happends often when the electrical protection or differential circuit-breaker of the installation activated and I push up the breaker to recover / get back the installation. Some examples here:



Coul you confirm if it was your case too? ( due to circuit-breaker activation)