Huawei FusionCharge Wallbox

[hauke-ruehs]

I tried to setup the evcc.yaml for the Huawei FusionCharge AC 22 kW Wallbox according to the Modbus documentation I was supplied with. It seems as if I need to provide specific keys for the Modbus registers. Could anyone help to modify my definition of the charger in order to make it work? Thank you!

chargers:

• name: wallbox1 # reference name
  type: custom
  power:
  source: modbus
  id: 1
  uri: XXX.XXX.XXX.XXX:502
  register:
  address: 4108
  type: holding
  decode: uint32
  status:
  source: modbus
  id: 1
  uri: XXX.XXX.XXX.XXX:502
  register:
  address: 4110
  type: holding
  decode: uint32
  

[andig]

That needs a custom module to implement the awkward steering by power. Would you want to attempt a PR?

/cc @premultiply by power is already implemented in ocpp

[hauke-ruehs]

Thanks @andig. I could try. Which keys are required for a custom wallbox?

[andig]

See api.Charger for the required interface

[hauke-ruehs]

I am reading the inverter data via modbus with nodered and parse it to evcc via a mqtt broker. All tools are running as seperate docker containers on a NAS. For the wallbox I tried to use the modbusproxy function with evcc and also added the respective port (5021) to the evcc container. When I tried to read the registers from the NAS/evcc (192.168.1.3:5021) there seems to be nothing there. Shouldnt I be able to get the inverter data?

modbusproxy:

• port: 5021
  uri: 192.168.1.2:502 # inverter

[premultiply]

@hauke-ruehs Can you please attach the full document or download link?

[RTTTC]

#8985 (reply in thread)

[hauke-ruehs]

Hi, I got nothing additional to the documentation in the thread mentioned above or the screenshot I was send from the Huawei support and which I have posted in the first place.

[premultiply]

Your screenshot differs from the linked PDF.
So please share your document.

[premultiply]

What are the contents of 0x100e ?

[hauke-ruehs]

this is the original screenshot I received from Huawei with no further documentation.

[hauke-ruehs]

Thanks for providing the updated version containing the huawei-ac template. As mentioned above (#10262 (comment)) I only get time-outs when I try to address the wallbox. Further the charger shows some error messages with regard to signal quality from the meter and is only charging with reduced power. It seems as if it doesn't want to "talk" to other devices than the inverter.

[smoki3]

I can confirm that its not working. Do we maybe need an external modbus server?

[hauke-ruehs]

After some intense discussions with the Huawei support I still cannot read any registers from the Charger's Modbus. For some reason they are investigating in the clinets connection to the inverter at the moment. The integration and also the surplus charging with the Huawei software works fine. I can also ping the Charger but if I want to read a Modbus register (in the same way I read from the inverter) either direct or via Modbus proxy I get a time out error.

[kanzie]

Did you ever get clarity on this and whether a separate modbus-server would be necessary?

[hauke-ruehs]

Well, "clarity" in that sense that it is not possible. The inverter is the Master and no external communication is allowed. I was observing network traffic of the Wallbox and there were only UDP but no ModBus TCP packages though.

[kanzie]

But this guy seems to have gotten some data out: #10262 (reply in thread) or is that other telemetry data?

Also the changelog for the latest release seems to indicate it should be same to send data to external NMS. If I haven't misunderstood this part at least it changes the situation from not possible to "it works but has a bug".

And then there was another sub-thread where they got a package but it was malformed and instead of an array of data it contained a parsing error from server. It was read only telemetry and no control support of any kind but that's all I'm looking for anyway.

[tryinit6]

Hello, any News on the integration of the Fusioncharge? Just updated mine on the latest firmware. As "Installer" I can see now the option "3rd party NMS via TCP Modbus" as mentionnend above. This setting seems only allow to connect the Fusioncharge as Client-Device on a NMS Server-Device. In any case on the IP-Address of my Fusioncharge the port 502 is not listening for any connection.

[hauke-ruehs]

Which version did you install? Mine is V100R023C10SPC020. As I recently learned from the Huawei support the feature is not supported at all, wich is quiet contradicting to previous statements:
At the moment the query via Modbus TCP is not supported for charger, as you were able to see from previous interactions.
I would not be able to let you know why the registers are listed although the functionality is not fully supported – as it might be a function that the upper team might work in the future or works at the moment.
We understand the value of real and true information that must be provided and I will redirect your feedback to our upper team. I do apologize for the inconvenient or unpleasant situation that this might generate.
Thank you for your understanding and have a nice evening.

[mucki12]

Wenn ich diese Matrix richtig verstehe, würde das die Aussage des Supports untermauern. Da erkenne ich mit meinem geringen Verständnis wenig Möglichkeiten als „Ziel“:
https://objects.githubusercontent.com/github-production-repository-file-5c1aeb/419381725/13556245?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20240319%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20240319T151140Z&X-Amz-Expires=300&X-Amz-Signature=d493d2e0eb0795e35e90e72784229b75979762e51035b18745ad1e3eadb372c6&X-Amz-SignedHeaders=host&actor_id=92673795&key_id=0&repo_id=419381725&response-content-disposition=attachment%3Bfilename%3DFusionCharge.V100R022C10SPC070.Communication.Matrix.xlsx&response-content-type=application%2Fvnd.openxmlformats-officedocument.spreadsheetml.sheet

[tryinit6]

The installed Firmware Version is the same like yours. Let me know if I can help you with some testing on my charger.

[kanzie]

Same here today. Happy to debug my environment for clues but need someone to help me make sense of the findings.

[RTTTC]

I would strongly advice against purchasing any equipment that is not fully integrated already.
Sometimes it takes years for the manufacturers promised integration to materialize, and sometimes it never does.

[tryinit6]

Today I setted up an modbus-slave logger and I inserted the slave IP in the Fusioncharge "NMS-Option", resulting in a packet stream every 2 minutes coming from the Fusioncharge to my logger.

[kanzie]

Today I setted up an modbus-slave logger and I inserted the slave IP in the Fusioncharge "NMS-Option", resulting in a packet stream every 2 minutes coming from the Fusioncharge to my logger.

Is this not the ten or so decimal registers that the documentation referenced? If so, there's our data!

[hauke-ruehs]

How did you set it up? Is your Huawei Charger connected to a Huawei Inverter? I was monitoring network traffic with wireshark and could not detect any TCP packages from the charger.

[hauke-ruehs]

In my setup I have the Huawei Charger connected to a Huawei Inverter. To use the Modbus output from the inverter I use the Modbus-Proxy from evcc so the registers are available via port 502 from the same IP as evcc. This works fine for e.g. Node-Red. Still I did not succeed in substituting the current grid-meter IP address (provided by the inverter) in the Charger's setup for the proxy IP as it was refused repeatedly.
If I monitor the network traffic of the inverter and the charger I only find UDP (destination 255.255.255.255!?) packages. If I setup my device as the NMS Modbus server I also get those TCP packages, but I don't know how to make use of them. I still cannot read/write any registers.
The Firmware package "FusionCharge_V100R023C10SPC060_FusionCharge-EU-CHARGE.zip" was refused from installation, thus I could not test OCPP.

[kanzie]

I'm confused. I also have the huawei inverter and chargebox. Has nobody gotten this integrated to home assistant at all?

[arnovy]

regarding to https://support.huawei.com/enterprise/en/doc/EDOC1100355823

V100R023C10SPC060 will bring OCPP1.6J so as soon as the new FW will be released full Evcc support should be possible

[mucki12]

As a long time Huawei customer: „will bring…“ the main Huawei slogan SCNR

[smoki3]

Is the ocpp protocol not just for the communication between car and Wallbox?

[arnovy]

@smoki3 no: https://docs.evcc.io/docs/devices/chargers/#ocpp-16j-kompatible-wallbox-mit-smart-charging-profil

[malakudi]

I do not have this Huawei charger but I plan purchasing it since I also have Huawei inverters. Some Huawei inverters were listening to port 6607 instead of 502 for modbus tcp. Has anyone tried port 6607? Has anyone done a port scan?

[hstreitenberger]

i tried evcc configure:

seems port 502 is doing something, but wrong? Port 6607 doesn't answer...
see attached picture

i have installed newest firmware V100R023C10SPC020

[smoki3]

Have to say, even with the ocpp firmware V100R023C10SPC060 it is bot working. Really annoying

[hauke-ruehs]

I would like to help but it seems as if I did not make it as far as @Kmotr.

[hauke-ruehs]

`chargers:

• name: SCharger
  type: template
  template: ocpp
  bootnotification: false
  timeout: 1m`

The charger part looks like this but both evcc and the ocpp integration don't really work because the charger uses the wrong data type for the meter values. On top of that there is no button to turn off the ocpp in the charger and now the normal pv surplus charging doesn't work anymore. Great job huawei. I think i'll have to factory reset the charger.

Did someone figure this out?

[andig]

The only real issue is

SetChargingProfile rejected

Someone will ne to fiddle with the parameters or ask support how to fix this.

[hauke-ruehs]

I send an email to the support and cc'ed also some developers. Hope this helps.

[Kugelfang666]

I also wrote a mail to the Huawei support to help escalate this topic a little bit.

[henrikssn]

Here are some sample messages which are sent if you set up a "third-party NMS" in the wallbox and then listen on that port (first column is byte count, rest is hexadecimal):

0000000 16 03 01 01 16 01 00 01 12 03 03 45 70 f2 96 db
0000020 76 41 4f 78 bd bb ed 83 7f 3d c5 94 e9 fe 9a 66
0000040 66 9d f1 c4 8a 4c 77 6d ab c4 eb 20 d0 a4 ff 41
0000060 48 32 ed f7 2f c2 46 b9 24 e4 4c 5f 23 83 32 d7
0000100 0c b9 f5 ee 61 b4 ad e0 cc 4f 10 cd 00 2c 13 03
0000120 13 02 13 01 13 04 c0 2f c0 30 00 9e 00 9f cc a8
0000140 c0 9e c0 9f c0 a2 c0 a3 cc aa 00 a2 00 a3 c0 2b
0000160 c0 2c c0 ac c0 ad cc a9 00 ff 01 00 00 9d 00 00
0000200 00 08 00 06 00 00 03 52 53 41 00 0b 00 04 03 00
0000220 01 02 00 0a 00 0c 00 0a 00 1d 00 17 00 1e 00 19
0000240 00 18 00 23 00 00 00 16 00 00 00 17 00 00 00 0d
0000260 00 30 00 2e 04 03 05 03 06 03 08 07 08 08 08 09
0000300 08 0a 08 0b 08 04 08 05 08 06 04 01 05 01 06 01
0000320 03 03 02 03 03 01 02 01 03 02 02 02 04 02 05 02
0000340 06 02 00 2b 00 05 04 03 04 03 03 00 2d 00 02 01
0000360 01 00 33 00 26 00 24 00 1d 00 20 56 9d 9c 36 6b
0000400 13 71 8f 22 26 83 3f 14 55 24 61 f9 52 1d 2b 45

0000000 16 03 01 01 16 01 00 01 12 03 03 7d 06 0a f2 fa
0000020 27 ec 0b b5 eb 44 c3 84 de bd bd ed 66 82 ee b4
0000040 9c 9f 2b be 62 ab f7 4f 0e e0 53 20 55 a6 30 35
0000060 fc 91 1d 97 dd 21 6c ab 0d c0 18 c0 fa 45 69 4b
0000100 c3 8c e6 64 62 e9 1d 12 53 a2 3a ad 00 2c 13 03
0000120 13 02 13 01 13 04 c0 2f c0 30 00 9e 00 9f cc a8
0000140 c0 9e c0 9f c0 a2 c0 a3 cc aa 00 a2 00 a3 c0 2b
0000160 c0 2c c0 ac c0 ad cc a9 00 ff 01 00 00 9d 00 00
0000200 00 08 00 06 00 00 03 52 53 41 00 0b 00 04 03 00
0000220 01 02 00 0a 00 0c 00 0a 00 1d 00 17 00 1e 00 19
0000240 00 18 00 23 00 00 00 16 00 00 00 17 00 00 00 0d
0000260 00 30 00 2e 04 03 05 03 06 03 08 07 08 08 08 09
0000300 08 0a 08 0b 08 04 08 05 08 06 04 01 05 01 06 01
0000320 03 03 02 03 03 01 02 01 03 02 02 02 04 02 05 02
0000340 06 02 00 2b 00 05 04 03 04 03 03 00 2d 00 02 01
0000360 01 00 33 00 26 00 24 00 1d 00 20 6c 3c dc 13 65
0000400 bc 11 3d 4f 95 61 c2 be fb 0e 3f af 90 67 60 6a

0000000 16 03 01 01 16 01 00 01 12 03 03 0f f9 78 72 70
0000020 6d 7f 41 d9 02 bd 12 0d 68 64 ed 5d e5 63 71 df
0000040 70 ca 5c 5a 42 7f fd 8d e3 3e 98 20 d3 90 e0 68
0000060 98 2d 91 ac 1f b9 83 7e ff cd ce 51 c0 7e fe 90
0000100 7b a7 e9 89 c0 78 d9 61 e2 64 e3 6c 00 2c 13 03
0000120 13 02 13 01 13 04 c0 2f c0 30 00 9e 00 9f cc a8
0000140 c0 9e c0 9f c0 a2 c0 a3 cc aa 00 a2 00 a3 c0 2b
0000160 c0 2c c0 ac c0 ad cc a9 00 ff 01 00 00 9d 00 00
0000200 00 08 00 06 00 00 03 52 53 41 00 0b 00 04 03 00
0000220 01 02 00 0a 00 0c 00 0a 00 1d 00 17 00 1e 00 19
0000240 00 18 00 23 00 00 00 16 00 00 00 17 00 00 00 0d
0000260 00 30 00 2e 04 03 05 03 06 03 08 07 08 08 08 09
0000300 08 0a 08 0b 08 04 08 05 08 06 04 01 05 01 06 01
0000320 03 03 02 03 03 01 02 01 03 02 02 02 04 02 05 02
0000340 06 02 00 2b 00 05 04 03 04 03 03 00 2d 00 02 01
0000360 01 00 33 00 26 00 24 00 1d 00 20 a7 c3 df 2d cc
0000400 a0 1d f9 08 83 89 9b 8c 60 26 ed 4c 5f d4 b6 6a

Perhaps someone know what protocol this is? Ping @tryinit6 since you seem to have explored the same thing above.

[deadrabbit87]

@henrikssn I would also be interested to know if anyone has succeeded to control the wallbox?

[smoki3]

Long story short: no

[deadrabbit87]

Long story short: no

Also not via OCPP? I've read that there are some firmware versions with OCPP Support?

[smoki3]

No not working actually

[MarcSpring]

Heißt das, dass EVCC auf absehbare Zeit nicht mit der HUAWEI Wallbox funktionieren wird? Warum ist diese Huawei Wallbox dann in der EVCC Doku aufgeführt https://docs.evcc.io/docs/devices/chargers#huawei-fusioncharge-ac ?

[trollsoft7]

some more information - taken from here: wlcrs/huawei_solar#491 (comment)

[snurrgos]

Don't know if it helps but have been trying to get this working for 2 days. Finally found that I had to log in to the fusionsolar via computer and go to monitoring > monitoring > choose the dongle > go to configuration > scroll down to bottom and enable Modbus-TCP and choose unrestricted or choose restricted but then add the ip of the service that needs data.

And sorry if I missed something, might at least help someone if they where looking for the answer I was :)

[hauke-ruehs]

I did exactly that: I only allowed connection to the Modbus-Proxy relaying the inverter/smart meter but it was not accepted by the charger. Communicating with the inverter is not a problem but somehow all attempts to establish a connection to the charger are failing.

[kanzie]

Are you connecting to the inverter over the IP given to the dongle or do you have a cat-cable with reversed cabling from the inverter to your router? I'm trying to understand exactly what I have to do to just get the inverter properly connected to use energy Dashboard in home assistant

[hauke-ruehs]

You need to specify the IP of the Inverter/dongle (see below).

[kanzie]

Ok. If that's all it takes I'll give it another go. But connecting from the huawei solar integration to the IP and port after opening it up in the inverter config did not work out of the box for me. Do I need a modbus-proxy in between or something then or did I just not do it correctly the first time around?

[hauke-ruehs]

Probably not. Only if you have other requests in parallel.

[Criaga]

Good morning, I apologize for asking this question but I have a problem.

Inverter Sun2000 6ktl - fw:141
Battery Luna
Dongle
Smart Charger Huawei

In the last few weeks, using the Huawei Solar integration, I have had constant disconnections.
I use the IP that the dongle has on my network.
I think it is due to Modbus, since the smart charger connects to the inverter with this protocol. If I turn off the wallbox I connect without problems.

Until a month ago I never had any problems. Help 😅

[kanzie]

Yeah separate issue but I'm keen to learn what you needed to do to get the integration running. I have the exact same setup but the integration says it can not connect to the server on the dongle ip on port 502. I have enabled modbus over tcp in the inverter already. Is there anything else I need to do?

[andrioid]

It was stable for a year without any issues, or until the HA pymodbus update months ago. Now it is clearly conflicting with the charger. It works some days, and not others.

[Criaga]

I found a temporary solution.
Today I connected the inverter's Wi-Fi to the Wi-Fi network of the PC running Home Assistant. First I turned off the wallbox then I integrated the inverter using the IP 192.169.200.1 port 6607 slave 0.
Then I turned on the wallbox….now it works.
As soon as I have time I would like to try installing the previous version of Huawei Solar (I now have 1.4.1)

[Criaga]

Test failed!!! I tried to install version 1.3.3 and as of this morning it has no disconnects. Now I'm connected via dongle IP /port 502/slave 1. Let's see what happens in the next few hours, but it seems very stable

[hauke-ruehs]

I use the evcc modbus-proxy, thus I can read the registers directly for evcc but also access via e.g. node-red.

[kanzie]

So you think they compete about the slave 0 slot?

…

On Wed 26. Jun 2024 at 13:35, Criaga ***@***.***> wrote: Test failed!!! I tried to install version 1.3.3 and as of this morning it has no disconnects. Now I'm connected via dongle IP /port 502/slave 1. Let's see what happens in the next few hours, but it seems very stable — Reply to this email directly, view it on GitHub <#10262 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGFGAEGQPD766L5FGG2J2LZJKRRPAVCNFSM6AAAAAA52KTHOGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQOBRG4ZDQ> . You are receiving this because you commented.Message ID: ***@***.***>

[hauke-ruehs]

Could you please contact the Huawei support (eu_inverter_support@huawei.com) and ask for the release date of OCPP 1.6? It is officially announced for Q4/2023 and still not available. For quick processing of your service requests it is advised to put your devices serial number into the email. Maybe this will eventually help to integrate the wallbox to evcc. Thank you!

[MMK1972]

I sent a question to support ocpp 1.6.

Can someone tell me how to tell the charger to connect to the address of the modbus proxy and not the address of the sdongle.

[hauke-ruehs]

That did not work for me. I also tried to replace the true smartmeter IP with the modbus proxy. Somehow the wallbox knows its not the meter. I suspect there is some communication between the two beyond modbus.

[uejo]

Hi, it seems version V100R023C10SPC120 is now available on the support page, does it help with this issue and OCCP?

[DNAngelX]

I got the wallbox and I'm happy with the internal PV charging feature, what specifically do you need evcc support for?
Here's a more polished version of your message:

To be honest, the internal PV charging feature is quite limited.

Here's my setup:

• 2 inverters (18 kW)
• 1 Huawei Battery (10 kW)
• Heat pump (for heating and hot water)

Ideally, the charger should only start charging the car when the Huawei battery is fully charged or when solar production exceeds the household's consumption by at least 5 kW. Unfortunately, this isn’t happening. The charger kicks in as soon as solar production exceeds household consumption, even if the battery is still empty.

Additionally, it's important for me to have the energy data integrated into my smart home system so I can accurately invoice the charging costs to my company, as it's a company car.

Overall, without these basic features, I wouldn’t choose this device again.

[hauke-ruehs]

Very interesting, I don't get a readout from the registers at all and if I try to read a register from the Charger via Modbus I see an error message in the app indicating poor connection to the meter. How did you address the registers? Are you using the Huawei Fusion Solar App?

[passibe15]

Ideally, the charger should only start charging the car when the Huawei battery is fully charged or when solar production exceeds the household's consumption by at least 5 kW. Unfortunately, this isn’t happening. The charger kicks in as soon as solar production exceeds household consumption, even if the battery is still empty.

I think this is specifically an issue if you have two inverters. If there is only one, setting "Max Charging Power from Grid" to 0.0 kW and "Surplus Power to Start Charging" to 5.0 kW should do exactly what you want it to do … It's a really odd/stupid limitation.

Also very unfortunate that Huawei is still not delivering, especially regarding the long-announced support for OCPP.

By the way: I don't really see a future for any modbus-based integration, unless Huawei makes some larger changes, which is not very likely given their focus (if you can call it that) on OCCP.

• Because of the charger's weird concurrent connection limit you would need to fully substitute the data delivered by the virtual dongle meter and
• because you'd have to make sure that the networks of charger and dongle are completely separated as the charger is very aggressive in scanning for the dongle and always trying to make a connection to it. This might not even be possible for people with consumer-grade networking hardware. (Btw, the charger is also generating loads and loads of broadcast traffic, it is really quite an annoying network device.)
• In addition, I am not sure what is going on with the whole certificate thing that you can see in the charger's settings; from some poking around with wireshark I did a while back, I believe there is some form of certificate-based trust establishment before a modbus connection is successfully established.
  TL;DR: I believe we'll have to wait for OCPP.

[Kugelfang666]

@DNAngelX : were you able to solve the 65 seconds issue? I would be Really happy to get the Huawei charger supported in EVCC and so far it seems you made the most progress on this front.

[DNAngelX]

@DNAngelX : were you able to solve the 65 seconds issue? I would be Really happy to get the Huawei charger supported in EVCC and so far it seems you made the most progress on this front.

No, only auto reconnect all 65 sec.

I added the support to set the interval into my adapter, this works 1/2 but the Huawai PV is not able to connect then to the Wallbx while the conenction is active.

[kanzie]

You can not set it lower than 0.5 but even if you do, it never uses pv only even with a full battery. This product is so flawed I wish I could just send it back and go with something actually built for the purpose.

…

On Mon, Sep 9, 2024 at 17:18 Passi Be ***@***.***> wrote: Ideally, the charger should only start charging the car when the Huawei battery is fully charged or when solar production exceeds the household's consumption by at least 5 kW. Unfortunately, this isn’t happening. The charger kicks in as soon as solar production exceeds household consumption, even if the battery is still empty. I think this is specifically an issue if you have two inverters. If there is only one, setting "Max Charging Power from Grid" to 0.0 kW and "Surplus Power to Start Charging" to 5.0 kW should do exactly what you want it to do … It's a really odd/stupid limitation. Also very unfortunate that Huawei is still not delivering, especially regarding the long-announced support for OCPP. By the way: I don't really see a future for any modbus-based integration, unless Huawei makes some larger changes, which is not very likely given their focus (if you can call it that) on OCCP. - Because of the charger's weird concurrent connection limit you would need to fully substitute the data delivered by the virtual dongle meter and - make sure that the networks of charger and dongle are completely separated as the charger is very aggressive in scanning for the dongle and always trying to make a connection to it. This might not even be possible for people with consumer-grade networking hardware. (Btw, the charger is also generating loads and loads of broadcast traffic, it is really quite an annoying network device.) - In addition, I am not sure what is going on with the whole certificate thing that you can see in the charger's settings; from some poking around with wireshark I did a while back, I believe there is some form of certificate-based trust establishment before a modbus connection is successfully established. TL;DR: I believe we'll have to wait for OCPP. — Reply to this email directly, view it on GitHub <#10262 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGFGAF3OI7GL5AJJDH4T2DZVW35LAVCNFSM6AAAAAA52KTHOGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANJZGI3DSNI> . You are receiving this because you commented.Message ID: ***@***.***>

[kanzie]

What did you write and where? With this a bunch of us lurking and waiting for progress can help to put pressure on them. We’re many more than the few brave of you who can do something about it, are least we can use our voice.

…

On Mon, Oct 7, 2024 at 14:46 Kugelfang666 ***@***.***> wrote: I also wrote a mail to the Huawei support to help escalate this topic a little bit. — Reply to this email directly, view it on GitHub <#10262 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGFGAAYU4QHAVZ3PAPVAFLZ2J7DDAVCNFSM6AAAAAA52KTHOGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOBWG4ZDIOA> . You are receiving this because you commented.Message ID: ***@***.***>

[hauke-ruehs]

I monitored the traffic coming from the wallbox on port 502. The problem is that you only get TLS request so unlike the Modbus connection with the inverter the modbus of the callbox is encrypted. See also #10262 (reply in thread)
I have no idea how to load a public key onto the wallbox or how to access via ssh. As mentioned before our best option is OCPP #10262 (reply in thread).

[hauke-ruehs]

@Kugelfang666 I was given the following address of the local product manager: mailto:viktor.rosin@huawei.com
Another reply from the support was that they want to check with development about the OCPP issue. In response I only got this:
"... After escalate your case the R&D come back with the answer that the OCPP is not supported."
It is getting really absurd and I do not have the feeling that this issue is taken seriously.

[arnovy]

I monitored the traffic coming from the wallbox on port 502. The problem is that you only get TLS request so unlike the Modbus connection with the inverter the modbus of the callbox is encrypted. See also #10262 (reply in thread) I have no idea how to load a public key onto the wallbox or how to access via ssh. As mentioned before our best option is OCPP #10262 (reply in thread).

Hi @hauke-ruehs,

if you connect directly to the wallbox as installer you can upload cerificates:

[Kugelfang666]

@Kugelfang666 I was given the following address of the local product manager: mailto:viktor.rosin@huawei.com Another reply from the support was that they want to check with development about the OCPP issue. In response I only got this: "... After escalate your case the R&D come back with the answer that the OCPP is not supported." It is getting really absurd and I do not have the feeling that this issue is taken seriously.

Thanks for sharing the contact, I'll send a mail to that person.

Today I had a telephone call from the Huawei Support in Rumania regarding the OCPP feature. The engineer remote updated my Wallbox to SPC120 claiming that this version (while not featuring OCPP in the list of inherited features) still has OCPP. Unfortunately, I cannot confirm this and looking through all venues I could not find any reference to OCPP...

[Kugelfang666]

@Kugelfang666 I was given the following address of the local product manager: mailto:viktor.rosin@huawei.com Another reply from the support was that they want to check with development about the OCPP issue. In response I only got this: "... After escalate your case the R&D come back with the answer that the OCPP is not supported." It is getting really absurd and I do not have the feeling that this issue is taken seriously.

I just send the following mail both to the contact you shared and to the German head of Huawei based in Düsseldorf. Lets see if I get any response:

Dear XXX,

I trust you’re doing good. I would like to raise a concern to you regarding a feature announced to be deployed via firmware update in Q4’23 to the Huawei Smart Charger: OCPP-compatibility.

Unfortunately, this feature is still missing and I’m feeling a little mislead by advertising this feature to be on the roadmap. In fact, when I check the product homepage right now, the feature is still mentioned (see link and screenshot attached)

An open and nonproprietary interface combined with a deep integration into my solar installation (2x Huawei M1 Inverters, 15kW LUNA2000, sDongle) was the main factor driving the decision towards buying the Huawei Wallbox over a competitor product.
Unfortunately, I had to learn that both, the native solar surplus charging features is implemented poorly (LUNA is discharged, no prioritization) and usage of 3rd party solutions to remedy this shortcoming like EVCC is impossible due to the missing OCPP interface.

To make matters worse, German government is starting to require a means to remotely control Wallboxes (§14a) and I had to sign a contract with my local grid operator that my Wallbox can be connected to their management system if they request so. In addition to all that I was even more confused when I found a statement presumably from a Huawei representative stating that OCPP is already available dated JAN 24 (pdf enclosed)

Apologies for bothering you with this but I sincerely hope that that you’re the right contact or can relay my inquiry to someone responsible to help clarify this situation.

In case you would like to follow up on this matter I’m happy to have a call with you or someone managing this product.

Best regards
XXX