Huawei Inverter with smart dongle - Modbus TCP

[RTTTC]

My inverter is SUN2000-12KTL-M2 connected via wifi smart dongle SDongleA-05
I am trying so many different things, changing firmware, etc, nothing seems to work, evcc meter returns read time-out errors.

Using Modbus scan apps for testing I am getting good readings, but usually first one or two also give time out, then all is normal.
So this could be the problem.
Another suspect is timeout - if I reduce timeout in modbus scan app to ~200ms - i never get a reading (just like in EVCC). If timeout is set at ~500 ms - i do get readings, but many errors. Once i set timeout as 800ms - errors are very few, and so on.
https://support.industry.siemens.com/tf/ww/en/posts/delay-in-modbus-communication/81834/ second post in this link explains that it's normal for timeout to be 1500ms or more.. (if i set timeout 2000 ms in Modbus Poll software during my testing, I don't get any errors)
What is the timeout setting in EVCC? Where would I find it?

And - just maybe - there is something wrong with my YAML configuration? I have changed everything there hundreds of times already, but maybe you guys could take another look?

- name: grid # Huawei grid power import export (when smart power sensor is present)
 type: custom
 power:
   source: modbus
   model: huawei
   uri: 192.0.0.61:502
   rtu: false
   id: 1
   register:
     address: 37113 # Grid import export power
     type: holding
     decode: int32

 currents:
   - source: modbus
     model: huawei
     uri: 192.0.0.61:502 # inverter port
     rtu: false
     id: 1
     register:
       address: 37107 # Huawei phase A grid current
       type: holding
       decode: int32

   - source: modbus
     model: huawei
     uri: 192.0.0.61:502 # inverter port
     rtu: false
     id: 1
     register:
       address: 37109 # Huawei phase B grid current
       type: holding
       decode: int32

   - source: modbus
     model: huawei
     uri: 192.0.0.61:502 # inverter port
     rtu: false
     id: 1
     register:
       address: 37111 # Huawei phase C grid current
       type: holding
       decode: int32

and

- name: pv1  # Huawei solar generation power
 type: custom
 power:
   source: modbus
   model: huawei
   uri: 192.0.0.61:502
   rtu: false
   id: 1
   register:
     address: 32080 # Active Huawei Solar generation power
     type: holding
     decode: int32

[ThePunisher1234]

Ich habe das gleiche Problem.
Huawei 30KTL-M3.

[andig]

It's really frustrating that EVCC can not read this yet..

I‘m somewhat sure that it actually can when configured correctly. Unfortunately I have neither seen any configuration attempt that would make use of the provided capabilities (i.e. timeout) nor have access to such a device.

[RTTTC]

I'm sorry, timeout does not help. Just built from master again, and results from evcc --log trace with timeout: 30s

[site ] DEBUG 2021/12/06 20:59:52 ----
[modbus] TRACE 2021/12/06 20:59:52 modbus: send 00 01 00 00 00 06 01 03 90 f9 00 02
[modbus] TRACE 2021/12/06 21:00:22 modbus: closing connection due to idle timeout: 30.0134362s
[modbus] TRACE 2021/12/06 21:00:23 modbus: send 00 02 00 00 00 06 01 03 90 f9 00 02
[modbus] TRACE 2021/12/06 21:00:53 modbus: closing connection due to idle timeout: 30.0156929s
[modbus] TRACE 2021/12/06 21:00:53 modbus: send 00 03 00 00 00 06 01 03 90 f9 00 02
[modbus] TRACE 2021/12/06 21:01:23 modbus: closing connection due to idle timeout: 30.0130369s
[site ] ERROR 2021/12/06 21:01:23 updating pv meter 0: read failed: read tcp 192.168.0.201:50287->192.168.0.61:502: i/o timeout
[site ] DEBUG 2021/12/06 21:01:23 pv power: 0W
[cache ] DEBUG 2021/12/06 21:01:23 pvPower: 0
[modbus] TRACE 2021/12/06 21:01:23 modbus: send 00 04 00 00 00 06 01 03 90 f9 00 02
[modbus] TRACE 2021/12/06 21:01:53 modbus: closing connection due to idle timeout: 30.0114443s
[modbus] TRACE 2021/12/06 21:01:53 modbus: send 00 05 00 00 00 06 01 03 90 f9 00 02
[modbus] TRACE 2021/12/06 21:02:23 modbus: closing connection due to idle timeout: 30.0128434s
[modbus] TRACE 2021/12/06 21:02:24 modbus: send 00 06 00 00 00 06 01 03 90 f9 00 02
[modbus] TRACE 2021/12/06 21:02:54 modbus: closing connection due to idle timeout: 30.007811s
[site ] ERROR 2021/12/06 21:02:54 updating grid meter: read failed: read tcp 192.168.0.201:50295->192.168.0.61:502: i/o timeout
[site ] DEBUG 2021/12/06 21:02:54 ----

[RTTTC]

It seems that EVCC opens socket, sends TX, waits for 30s , closes socket. Opens socket again and repeats. But with huawei "smart" (or really stupid) dongle - first TX always fails... in my testing it only responds to second TX , if socket was not closed.
Does it sound like it could be?

[andig]

Possible. That scenario would still require debugging the flow inside the modbus library and playing with the various timeout options.

[RTTTC]

There is definitely something wrong with Huawei TCP Modbus implementation.
I now use 2 windows programs, 4 iOS apps and EVCC for testing.
Some on them - including EVCC refuse to read any data.
Others - connect after second try.
At least one - connects as if nothing is wrong at all.
I can see the difference in response clearly when compared with working ABB/Fimer inverter.

It's either an ongoing problems with Huawei firmware (and from reading different forums seems like they can't get it working for years)
Or simply my devices are defective? Thats why it's important to get feedback from other Huawei users. @ThePunisher1234 ?
Huawei tech support is fairly good in general, but this problem is hard for them to grasp for some reason, strange.
So I hope for a new dongle firmware fix.
(BTW there is even a Sunspec menu option in the latest inverter firmwares, but it can not be activated yet.)

Now it's either a waiting game for Huawei to fix their problems, or hope that someone can create a workaround solution.

[andig]

if i set timeout at 2000 ms during my testing, i don't get any errors

You can set timeout in evcc, too.

In #1930 wird auch für die Plugins timeout ermöglicht. Es gilt die "letzte" Einstellung, die müssen also für eine Verbindung konsistent sein. Leere Werte ändern die Einstellung nicht.

/cc @premultiply bzgl Doku

[DerAndereAndi]

@andig @premultiply ich hab mal die Config nach dem Beispiel oben als PR hinzugefügt: https://github.com/evcc-io/config/pull/86

[premultiply]

Ich glaub die stimmt noch überhaupt nicht. Wollte mal abwarten bis jemand das mit evcc meter testet.

[DerAndereAndi]

timeout fehlt da auch noch

[DerAndereAndi]

habe timeout: 2s mal angehängt und aus versehen grid und pv getauscht. jetzt müsste das jemand mit dem aktuellen code aus master mal testen

[RTTTC]

I will try to comment on the pull, it got all mixed up - hope I don't make it even worse! Trying to learn on the go how this system works.. :)

[andig]

@RTTTC does it work with the timeout parameter?

[RTTTC]

@premultiply
Yes, dongle firmware is 123, inverter FW 139
I did try id 0, 1, 2, 3 - no change. I have also checked in the inverters internal settings menu - it's id is set as 1, tried to change it to 3, but it resets back to 1.
Inverter IP is correct and static.
Using id 1, same IP, same register address I get good readings when I read inverter data using various Modbus TCP read apps, I get power in watts that correspond to power value in Huawei FusionSolar cloud UI , so inverter id, IP and register address should be good..

[premultiply]

Can you update dongle FW to 126?

[RTTTC]

Latest dongle FW is 124. (Huawei firmware file naming can be quite confusing)

This is how they got Huawei modbus TCP meter working in OpenWB: time.sleep

https://openwb.de/forum/viewtopic.php?p=41540#p41540
https://openwb.de/forum/viewtopic.php?p=47113#p47113
https://openwb.de/forum/viewtopic.php?p=47850#p47850

[premultiply]

pi@picharger:~ $ evcc meter --log trace
[main  ] INFO 2021/12/05 01:24:02 evcc 0.70 (9cfbe16)
[main  ] INFO 2021/12/05 01:24:02 using config file /etc/evcc.yaml

grid
----
[modbus] TRACE 2021/12/05 01:24:02 modbus: send 00 01 00 00 00 06 00 03 90 f9 00 02
[modbus] TRACE 2021/12/05 01:24:03 modbus: send 00 02 00 00 00 06 01 03 90 f3 00 02
Power:          read failed: read tcp 192.168.0.225:57930->192.168.0.61:502: i/o timeout
Current L1..L3: read failed: read tcp 192.168.0.225:57932->192.168.0.61:502: i/o timeout

pv1
---
[modbus] TRACE 2021/12/05 01:24:04 modbus: send 00 03 00 00 00 06 00 03 7d 50 00 02
Power: read failed: read tcp 192.168.0.225:57934->192.168.0.61:502: i/o timeout

I can see two requests to Id 0 and only one to Id 1...

[RTTTC]

I was trying so many things at that time, so its my mix up.
Here is a fresh log from this morning. (id2 is a working ABB inverter)
I can see that it even sent out two requests to grid meter before closing the connection

[site  ] DEBUG 2021/12/07 11:47:04 ----
[modbus] TRACE 2021/12/07 11:47:04 modbus: send 00 01 00 00 00 06 02 03 00 54 00 01
[modbus] TRACE 2021/12/07 11:47:04 modbus: recv 00 01 00 00 00 05 02 03 02 00 48
[modbus] TRACE 2021/12/07 11:47:04 modbus: send 00 01 00 00 00 06 01 03 7d 50 00 02
[modbus] TRACE 2021/12/07 11:47:05 modbus: send 00 02 00 00 00 06 01 03 7d 50 00 02
[modbus] TRACE 2021/12/07 11:47:06 modbus: send 00 03 00 00 00 06 01 03 7d 50 00 02
[site  ] ERROR 2021/12/07 11:47:07 updating pv meter 1: read failed: read tcp 192.168.0.225:35756->192.168.0.61:502: i/o timeout
[site  ] DEBUG 2021/12/07 11:47:07 pv power: 72W
[cache ] DEBUG 2021/12/07 11:47:07 pvPower: 72
[modbus] TRACE 2021/12/07 11:47:07 modbus: send 00 04 00 00 00 06 01 03 90 f9 00 02
[modbus] TRACE 2021/12/07 11:47:09 modbus: send 00 05 00 00 00 06 01 03 90 f9 00 02
[modbus] TRACE 2021/12/07 11:47:09 modbus: closing connection due to idle timeout: 5.000809435s
[modbus] TRACE 2021/12/07 11:47:10 modbus: send 00 06 00 00 00 06 01 03 90 f9 00 02
[site  ] ERROR 2021/12/07 11:47:11 updating grid meter: read failed: read tcp 192.168.0.225:35762->192.168.0.61:502: i/o timeout
[modbus] TRACE 2021/12/07 11:47:15 modbus: closing connection due to idle timeout: 5.003373232s
[site  ] DEBUG 2021/12/07 11:47:34 ----

[andig]

Nachdem das jetzt schon ne Weile hin und her geht. Wie wäre es denn mal einem Entwickler Remote Zugang zu geben?

@premultiply willst Du probieren?

[RTTTC]

I would gladly do that, not really sure how its done, but with some help It could be done for sure :)

[premultiply]

https://www.photovoltaikforum.com/thread/148737-huawei-wechserichter-software-update-auf-sunspec/?pageNo=3

[RTTTC]

Lets do it! :)

I would gladly do that, not really sure how its done, but with some help It could be done for sure :)

[andig]

Forward the internal port to make it externally available. https://www.edpnet.be/en/support/installation-and-usage/internet/manage-fritz!box/how-to-set-up-a-port-forwarding-on-a-fritzbox.html

[RTTTC]

I know how to do it, and have a few open ports from my internet provider. Forward the port to my Raspberry that hosts EVCC or Huawei inverter ?
Direct email maybe better than here?

[andig]

Direct email maybe better than here?

cpuidle@gmx.de

[RTTTC]

Email sent.

[DJ-Huawei]

Hi i´m Dieter from Huawei.

I hope i can bring a bit light in the dark.
You need a SmartDongle with Firmware SPC 120 or newer.
For SPC124 and newer Modbus TCP must be activated locally via the FusionSolar APP.

SPC123 is okay and easy running without any setups via APP.

Timeout: 1000 ms
Delay after start: 10 s

Read every 5 s and wait 2 s for the answer from the dongle. Faster reading generates error!

If there are several inverters, the information must be read separately over the Modbus address.

example:

Modbus address 1 = Inverter 1 with SmartDongle, Smart Power Sensor and battery.

Modbus address 2 = Inverter 2

No Sunspec is running on the inverter.
Register:
32064 = DC Power (32 bit)
32080 = AC power (32 Bit)
37113 = Meter Power (32 bit signed)
......

okay i try it by my own evcc.

BR
Dieter

[premultiply]

Hello Dieter, is this very special behavior for Modbus communication only a problem of the Dongle?

As we already have support for SUN2000 included for a long time without these ugly timing constraints.
For the guys using the Modbus RTU interface over RS485 we never heard of such problems before. It simply runs with the default setting like any other device.

I have never seen or touched a Huawei inverter installation by myself so I am not sure about the system design, options and communication paths.

The question is: Does the installation of the dongle restrict or disable the access to RS485 on the inverter as it uses it for system communication itself?
If the RS485 port would be still free to use the solution for the users is very simple: Just connect a cheap serial-to-ip-converter or Modbus TCP-Translator like the Protoss PE11-H to bypass the dongle usage completly.

Some of the evcc calculations rely on fast access to some data values, especially for the grid meter values. So waiting for values for up to 5 Seconds or more may not be an acceptable delay for things like load management.

[andig]

For the record: we are working on supporting the dongle.

[RTTTC]

@DJ-Huawei I have the latest dongle firmware SPC126. I get data from Huawei using some apps, but many do not work with huawei, not just EVCC. For you to test yourself: iOS app ModComm:Peek & Poke, or Android app Poll ModBus. Does not work with Huawei.

On the other hand - could you partner up and help EVCC developers to get Huawei+EVCC working, using wast Huawei development and coder resources and knowledge? That would be great! #2109

[DJ-Huawei]

@premultiply Yes it´s the Dongle the have a lot of functions. In the end its also a RTU to TCP translator and also the controller of the system if you have more the one inverter.
If you use RTU with EVCC then please NOT use the Dongle at the same time. Then you have to masters in on system and this is not so good. For that you can also use a RTU to TCP converter like the protess (Never tested by me)

So with the Dongle is about 5 sec and andig will make it happen in the future or you run RTU without the dongle( and without the huawei fusionsolar portal) and you have it faster like <1 sec.

[premultiply]

Thank you very much Dieter for clarification.
That is exactly what I expected.

[premultiply]

Maybe it is less painfull to connect directly to the serial RS485 interface?

[premultiply]

If you only have a single inverter this is the way to go for you: Drop the Huawei Smart Dongle and connect a Protoss PE11-H or other serial converter to the RS485 Modbus RTU interface of the inverter and your problems will be gone. The native interface Modbus RTU interface works painless for a long time with evcc and other solutions.
Of course you can also run native RS485 connections over very long distances like 500 meter over a single twisted pair copper line and connect it to a native serial interface on the device running evcc. This would be the least cost and most simple solution.

[RTTTC]

Was it really a disruptive comment? I view it simply as advice for someone who is thinking about EVCC compatible hardware that works easily. "The best problem is the one that you don't have"

I wish i had such advice myself when I decided on which solar inverter to get.
I chose Huawei for it's advertised "new digital age" and yet it fails so miserably on such a simple standard thing as Modbus TCP.

Looks like the problem I have is 50/50 Huawei and EVCC
Huawei does not comply with standard Modbus TCP response, but some of the Modbus TCP apps read its data without any fuss, so its also a limitation on EVCC part. When two half problems are combined - we get total failure :)

I am trying to get both problem sides fixed, but so far no luck. Huawei does not really view it as something that needs fixing (or perhaps it's a "smart" dongle hardware limitation?) and EVCC developers don't have access to test the hardware? Not enough time, not enough Huawei users asking for help? etc.

I am simply out of ideas on what to do with this.

[andig]

Looks like the problem I have is 50/50 Huawei and EVCC

I don't want to play a blame game here. Fact is that evcc works fine with Huawei unless the dongle comes to play. The dongle simply has very peculiar timing requirements that application side needs to work around.

I am simply out of ideas on what to do with this.

While it was working in my tests my test system is currently not available. Waiting for getting access to a Huawei again...

I am simply out of ideas on what to do with this.

I once more (and have had from the beginning) have need for testing access.

[RTTTC]

@andig @premultiply I have figured out how to provide remote access, opened port 502, could you guys try it?

[andig]

I got something working:

[modbus] TRACE 2021/12/23 14:04:34 modbus: send 00 01 00 00 00 06 02 03 90 f9 00 02
[modbus] TRACE 2021/12/23 14:04:37 modbus: recv 00 01 00 00 00 07 02 03 04 ff ff f3 91
[modbus] TRACE 2021/12/23 14:04:39 modbus: send 00 02 00 00 00 06 02 03 90 ff 00 02
[modbus] TRACE 2021/12/23 14:04:40 modbus: recv 00 02 00 00 00 07 02 03 04 00 22 83 b2
[modbus] TRACE 2021/12/23 14:04:40 modbus: send 00 03 00 00 00 06 02 03 90 f3 00 02
[modbus] TRACE 2021/12/23 14:04:42 modbus: recv 00 03 00 00 00 07 02 03 04 ff ff fd 28
[modbus] TRACE 2021/12/23 14:04:42 modbus: send 00 04 00 00 00 06 02 03 90 f5 00 02
[modbus] TRACE 2021/12/23 14:04:44 modbus: recv 00 04 00 00 00 07 02 03 04 ff ff fc b3
[modbus] TRACE 2021/12/23 14:04:44 modbus: send 00 05 00 00 00 06 02 03 90 f7 00 02
[modbus] TRACE 2021/12/23 14:04:44 modbus: recv 00 05 00 00 00 07 02 03 04 00 00 00 ab
Power:          -3183W
Energy:         22619.4kWh
Current L1..L3: -7.28A -8.45A 1.71A

Unfortunately it's currently not possible to do this with our modbus library. Need to think about a clean solution to enable this.

[kesdas]

Great work guys, keep it up! :)

[RTTTC]

@andig I have tried it with 0.81 release, various timeout and delay settings, still no go.
Is it working for you? Could you post your settings?

[andig]

I can confirm that the current release works fine with the dongle:

❯ gor main.go meter --log trace -c cfg/huawei.yaml
[main  ] INFO 2022/01/15 21:16:10 evcc 0.0.1-alpha (HEAD)
[main  ] INFO 2022/01/15 21:16:10 using config file cfg/huawei.yaml
grid
----
connected, sleep
sleep done
[modbus] TRACE 2022/01/15 21:16:17 modbus: send 00 01 00 00 00 06 02 03 90 f9 00 02
[modbus] TRACE 2022/01/15 21:16:17 modbus: recv 00 01 00 00 00 07 02 03 04 ff ff f0 c2
[modbus] TRACE 2022/01/15 21:16:19 modbus: send 00 02 00 00 00 06 02 03 90 ff 00 02
[modbus] TRACE 2022/01/15 21:16:19 modbus: recv 00 02 00 00 00 07 02 03 04 00 22 86 0c
[modbus] TRACE 2022/01/15 21:16:19 modbus: send 00 03 00 00 00 06 02 03 90 f3 00 02
[modbus] TRACE 2022/01/15 21:16:20 modbus: recv 00 03 00 00 00 07 02 03 04 ff ff fc ee
[modbus] TRACE 2022/01/15 21:16:20 modbus: send 00 04 00 00 00 06 02 03 90 f5 00 02
[modbus] TRACE 2022/01/15 21:16:20 modbus: recv 00 04 00 00 00 07 02 03 04 ff ff fc 76
[modbus] TRACE 2022/01/15 21:16:20 modbus: send 00 05 00 00 00 06 02 03 90 f7 00 02
[modbus] TRACE 2022/01/15 21:16:21 modbus: recv 00 05 00 00 00 07 02 03 04 ff ff ff 89
Power:          3902W
Energy:         22625.4kWh
Current L1..L3: 7.86A 9.06A 1.19A

battery
-------
[modbus] TRACE 2022/01/15 21:16:23 modbus: send 00 06 00 00 00 06 02 03 90 89 00 02
[modbus] TRACE 2022/01/15 21:16:24 modbus: recv 00 06 00 00 00 07 02 03 04 00 00 00 00
[modbus] TRACE 2022/01/15 21:16:26 modbus: send 00 07 00 00 00 06 02 03 90 8c 00 01
[modbus] TRACE 2022/01/15 21:16:26 modbus: recv 00 07 00 00 00 05 02 03 02 00 00
Power: 0W
SoC:   0%

This is the config:

meters:
- name: grid # Huawei grid power import export (when smart power sensor is present)
  type: custom
  power:
    source: modbus
    timeout: 10s
    connectdelay: 5s
    delay: 2s
    model: huawei
    uri: <ip>:502
    id: 2
    register:
      address: 37113 # Grid import export power
      type: holding
      decode: int32
    scale: -1
  energy:
    source: modbus
    timeout: 10s
    connectdelay: 5s
    delay: 2s
    model: huawei
    uri: <ip>:502
    id: 2
    register:
      address: 37119 # Grid active energy
      type: holding
      decode: int32
    scale: 0.01
  currents:
  - source: modbus
    model: huawei
    uri: <ip>:502 # inverter port
    id: 2
    register:
      address: 37107 # Huawei phase A grid current
      type: holding
      decode: int32
    scale: -0.01
  - source: modbus
    model: huawei
    uri: <ip>:502 # inverter port
    id: 2
    register:
      address: 37109 # Huawei phase B grid current
      type: holding
      decode: int32
    scale: -0.01
  - source: modbus
    model: huawei
    uri: <ip>:502 # inverter port
    id: 2
    register:
      address: 37111 # Huawei phase C grid current
      type: holding
      decode: int32
    scale: -0.01
- name: battery
  type: custom
  power:
    source: modbus
    timeout: 10s
    connectdelay: 5s
    delay: 2s
    model: huawei
    uri: <ip>:502
    id: 2
    register:
      address: 37001
      type: holding
      decode: int32
  soc:
    source: modbus
    timeout: 10s
    connectdelay: 5s
    delay: 2s
    model: huawei
    uri: <ip>:502
    id: 2
    register:
      address: 37004
      type: holding
      decode: uint16
    scale: 0.1

[RTTTC]

Thank you!!!
It works ! I was missing connectdelay

- name: grid # Huawei grid import export power
  type: custom
  power:
    source: modbus
    connectdelay: 1s
    model: huawei
    uri: <ip>:502
    rtu: false
    id: 1
    register:
      address: 37113
      type: holding
      decode: int32
    scale: -1

I have only added connectdelay: 1s and everything works. It cycles through all my meters in ~5 seconds (my other ABB inverter now at night is off, and gives 5s timeout delay. So it may even be faster tomorrow during daylight)

Few questions :

1. What is the function of delay in your config? Do I need to add it too?
2. I have rtu: false in my config, is it not needed?
3. for energy meter - what should it measure and for what purpose? register 37119 is "active energy fed by the inverter to the power grid" / Is that right? Or should we use 37121 "active energy supplied from the power grid"

[RTTTC]

My Huawei system is now operating fine, with no errors.

Thank you all for all your help, suggestions and hard work that was put into this!

I also hope that with time Huawei will improve their firmware, so that no "special treatment" is needed.

Here is my working configuration:
Inverter is SUN2000-12KTL-M2 connected via wifi smart dongle SDongleA-05. This should work with any SUN2000 series inverter with smart dongle connection, WIFI or LAN.
Also I have optional Huawei smart power sensor installed. This can provide data for grid and battery meters

Inverter firmware is V100R001C00SPC140
Dongle firmware : V100R001C00SPC126
Modbus TCP for the dongle is enabled in Inverter internal menu (!)

I have no battery installed.

If anyone has any questions I would be glad to help.
Also I could provide remote access to my system for developers, if needed for further testing.

This is my exact working configuration:

meters:

- name: grid # Huawei grid import export power
  type: custom
  power:
    source: modbus
    timeout: 10s
    connectdelay: 1s
    model: huawei
    uri: 192.0.2.2:502
    id: 1
    register:
      address: 37113 # Huawei import/export active power / IF Huawei smart power sensor is installed
      type: holding
      decode: int32
    scale: -1

  energy:
    source: modbus
    timeout: 10s
    model: huawei
    uri: 192.0.2.2:502
    id: 1
    register:
      address: 37121 # active energy import from the grid
      type: holding
      decode: int32
    scale: 0.01

  currents:
    - source: modbus # Huawei phase A grid current
      timeout: 10s
      model: huawei
      uri: 192.0.2.2:502
      id: 1
      register:
        address: 37107 # Huawei phase A grid current / IF Huawei smart power sensor is installed
        type: holding
        decode: int32
      scale: -0.01

    - source: modbus # Huawei phase B grid current
      timeout: 10s
      model: huawei
      uri: 192.0.2.2:502
      id: 1
      register:
        address: 37109 # Huawei phase B grid current / IF Huawei smart power sensor is installed
        type: holding
        decode: int32
      scale: -0.01

    - source: modbus # Huawei phase C grid current
      timeout: 10s
      model: huawei
      uri: 192.0.2.2:502
      id: 1
      register:
        address: 37111 # Huawei phase C grid current / IF Huawei smart power sensor is installed
        type: holding
        decode: int32
      scale: -0.01

- name: pv # Huawei Solar generation power
  type: custom
  power:
    source: modbus
    timeout: 10s
    connectdelay: 1s
    model: huawei
    uri: 192.0.2.2:502
    id: 1
    register:
      address: 32080 # Active generation power
      type: holding
      decode: int32

[proxymus]

Hi RTTTC,

I've used your configuration file for my SUN2000-15KTL-M0 (V100R001C00SPC141) with SDongleA-05 (V100R001C00SPC126) and power sensor (DTSU666-H). I have no battery installed yet.
It is working! Thank you for sharing it!

Off-Topic:
@RTTTC Is your inverter on at night? Mine turns off at sunset, so I have no consumption data at night.
@andig this causes error messages in evcc (inverter not reachable).

Kind regards
Proxymus

[RTTTC]

Mine is SUN2000-12KTL-M2 , it is on during the night. Not sure if there is a setting for that or just model difference?
May be worth contacting Huawei tech support and ask if night operation can be enabled?

I also have ABB inverter, that turns off during the night, and also causes error messages in EVCC.
Thats is expected behaviour for EVCC

[proxymus]

I've asked the Huawei support. They told me the inverter (SUN2000-15KTL-M0) has no auxiliary power for AC and DC. I am not a specialist for this. So it does not seem to work to see the consumption data over the night. Maybe @DJ-Huawei can give us an understandable explanation.

[liamwibo]

can you add me on dc "liamwibo" if you want and help me out because i am also having problems getting the SUN 2000 to work

[DJ-Huawei]

yes it´s tru! M0 inverter from 12-20KTL can not support meter data at night. Newer versions like the M2 have this function.

[premultiply]

Can you please specify "not support" more precisely?
Is there anything we should do or may work around to assume a power of 0W etc. if a specific situation is entered?

[DJ-Huawei]

The inverter power down and you can not get any data from it. There is unfortunately no work around.

[premultiply]

So the only workaround in this case could be to completly ignore / silence connection loss errors and just return 0?

[proxymus]

yes it´s tru! M0 inverter from 12-20KTL can not support meter data at night. Newer versions like the M2 have this function.

@DJ-Huawei Thanks for the feedback. Too bad that I can't get any values from the power sensor (DTSU666-H) even it is not powered off at night.

[RTTTC]

My Huawei sdongle communication issues still not resolved by manufacturer as of firmware 133, and above workaround is required.

@DJ-Huawei Hello Dieter, I have noticed that there are now two lines of sdongle firmware, indicating that there is a new version of sdongle hardware.
Could you please tell us how is the new hardware version different?
Maybe it has modbus comunication timing issues resolved and tested?
Thanks!

[nicx]

@RTTTC could be the new SDongleB-06 with 4G & WLAN, but no LAN. Hopefully this ist faster than the old hardware.

[soccermax]

Hi @RTTTC, thanks very much for posting your working config for your setup. I'm about to realize the same setup with a Heidelberg Wallbox. Is it still required to configure custom types as you did in your posted config: here.
I thought this is not necessary anymore as Huawei devices should be supported by ev cc by existing templates or am I wrong?
In particular the custom section here:

- name: pv # Huawei Solar generation power
  type: custom
  power:
    source: modbus
    timeout: 10s
    connectdelay: 1s
    model: huawei
    uri: 192.0.2.2:502
    id: 1
    register:
      address: 32080 # Active generation power
      type: holding
      decode: int32

If this is the current way to go wouldn't it make sense to include this as template into evcc?
Thank you very much for your help 👍

[RTTTC]

This was an old post, just when we got Huawei working. Later tweaked to perform better.
Template config is latest and gratest , and is sufficient for most cases for most users ;)
Configuration could be made both ways, manual or template, evcc works the same. (I am using manual configuration myself)
This line from template may be of interest for pv meter use, (Huawei with Sdongle and smart power sensor)
address: 32064 # Input power DC (if no battery in your system - for more precise readings use 32080 # Active generation power AC)

https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/huawei-sun2000-dongle-powersensor.yaml

[soccermax]

Thanks for the fast reply. Looking at your configuration I have another question: There are multiple options to get the setup running, I could connect the Sun2000 via the Smart Dongle with evcc directly or I could use the smart power sensor as proxy right? (as you're doing it, right?) If it's possible via the smart power sensor this would be quite convenient as I would get all the required data from one device: Battery SoC, Grid, and PV Data. Or am I missing something?

[RTTTC]

Since you have the battery, simply use the evcc configure

[soccermax]

I'll use evcc configure for sure. But as I'm new at this I'm trying to understand the basics. Just for me to understand:
The smart power sensor is connected to the inverter via RS485 and the inverter will be connected to my home wifi with the smart dongle is that correct? So what I'm trying to understand is: which device is communicating with which device?
My current understanding is:
smart meter measures the grid and sends via RS485 to the inverter and the raspberry with evcc can get grid, battery, pv data directly from the inverter via the smart dongle. Is that also correct?