Support for Hauwei EMMA-A01/A02 (New Product Release)

[Roving-Ronin]

FYI giving the release of the EMMA in Q4 2023, the DTSU-666H, SmartLogger and Dongle look to be superceded as the "default" connectivity option for Huawei inverters/batteries etc. Given this thought it might be an idea to open a discussion upon this new product, even though pending its release currently, to allow planning / looking into it for the future.

Read below and you can work out that EMMA is collapsing the Logger functionality, the meters functions (with its 63A CT sensors, for home installs given 63A that is same as the BackupBox and its replacement the 'SmartGuard') and the network connectivity all into one 6 DIN unit. Atop of this it will also provide some additional smarts / functions.

Going forward this raises the question will WLCRS integration support this hardware (i.e. uses the same registers as now), OR will it use different registers etc and need updates in the WLCRS integration to support it? At least with Huawei merging all these functions into one bit of kit going forward, this will also mean one standard method of connectivity (at least for home installations) making support / troubleshooting etc easier.

IMHO verses all the different connectivity options (Dongle, Elfin or SmartLogger [that doesn't 100% work]) this could be a positive development and well worth upgrading from the DDSU-666H / DTSU-666H and dongle to this 'all in one' solution, whilst also adding AI/Cloud based data for automation and decision making.

---

EMMA-A01/A02 is Huawei's new energy management assistant, the ideal complement for a smart and efficient home with solar power systems with Huawei inverters and batteries.

Huawei EMMA-A01/A02 Power Management Assistant

With this AI-based power management assistant, Huawei provides power generation estimates based on big data such as historical data recorded by Huawei inverters or weather forecasts. Thanks to all this information, it adjusts the entire system to make it much more efficient and intelligent.

• Supports heat pump and smart circuit breaker for comprehensive management of home energy use.

• Supports 63A current measurement with internal CT for easy installation.

• Supports scheduled mode and PV array preferences mode for best electricity savings.

---

Note: Trying to see if access can be gained to at least modbus register definitions for EMMA, to allow evaluation for WLCRS integration compability.

[wlcrs]

As a general policy this integration only supports devices I can test against (ie. the devices that I own myself). Only so can I guarantee the proper working of this integration.

I do welcome contributions that add support for new devices. So feel free to create a PR in the underlying huawei-solar library. I would advice anyone contributing to create a PR early in their development work to get feedback and tips from me.

[Roving-Ronin]

This thread is to highlight:

A) There is a new product coming out, which, from information available will be the default method for Huawei installations to be deployed with.

B) Raises this for awareness and future planning for how can this be added/supported in the integration? (Do we need a GoFundMe to get WLCRS's setup upgraded from a dongle to EMMA in future?).

C) Highlights that, with information being that it will replace the DDSU/DTSU-666H meter, Dongle and SmartLoggers, it would not be worth pursuing support for SmartLoggers (at least for residential users of them). Instead of Huawei is standardising upon the EMMA going forward, it would be easier to just upgrade a SmartLogger to an EMMA setup.

D) Provides a discussion thread for people to follow and communicate upon the EMMA and if/how to support it.

FYI also trying to see if Huawei will release 'Modbus Register Definitions' documentation of the EMMA, allowing a paper evaluation of if the integration will work with it (same registers used), or if anything is different from existing registers.

[Roving-Ronin]

Links to installation and user guides for EMMA, and mention of how it connects up, posted in Issues section.
See: [Feature Request]: Wallbox Integration - #491

Edit: I should add, information received is that EMMA will support connecting to cloud services with the example provided being that it will be able to check for environmental / weather data (no info as to which clould service provider) and based upon this make intelligent decisions, such as ' rain / overcast day tomorrow with low expected kWh to be generated via local PC, then instruct LUNA ESS to charge overnight during offpeak when cost per kWh is lowest'.

[tmycgn]

Does anyone know whether the Emma and the dongle can be operated in parallel? I would like to use this integration. Otherwise, I agree that all new installations will only be delivered with "new" Emma. I would therefore also be very happy about an integration of Emma. :)

[Roving-Ronin]

@tmycgn
EMMA replaces the sDongle in an installation, as only ONE device (made to provide the internet connection) can exist in a plant (be it 1 or 3 invertes cascaded), hence logic dictates that its would not be compatible with running EMMA + sDongle concurrently.

Have you tried installing the WLCRS integration using the modbus id # (1?) of the EMMA on your LAN, with modbus support activated?
If it doesn't work, your only options currently would be to provide Thijs (WLCRS) access to your HA to develop support for EMMA upon your HA+Huawei instance. The only other fallback that you (may) be able to get working, would mean needing to get something like the Elfin (see Wiki) wired in upstream of the Primary Inverter (or EMMA?) and seeing they both still work (i.e. can access mmodbus and EMMA can talk to FusionSolar portal).

Re new instalations, the sDongle would appear to be remaining as a connectvitiy option going forward, but it also has its own issues such as if people install a Huawei EV charger and connect it to the modbus on the sDongle, that will boot HA from connecting (as it only supports 1 connection). On the flip side, people in future installing the 'Backup Box' will be looking at the replacement the 'SmartGuard' that includes an EMMA and DDSU/DSTU type consumption meter built into it (so they won't have any choice).

As Thijs (WCLRS) comments, as it stands he can't add support for anything until has can get access to this new Huawei equipment that is coming to market (i.e. either people give him remote access to develop, or GoFundMe required).

[wlcrs]

For the moment, Huawei is not able to produce any documentation on how to connect to installations with an EMMA device present. After asking for documentation, they first erroneously sent docs concerning SDongleA devices. After a follow up email pressing for docs for connecting to EMMA via Modbus, we got the following answer:

Unfortunately we do not have any ModBus guidance especially for EMMA-A02.

A second follow up did not result in a more promising answer:

Unfortunately, we do not have any guideline about how access works exactly and how the individual services can be accessed (modbus tCP, MQTT, web,...) especially for EMMA-A02.

I've already had access to an installation that has an EMMA device present, but was not able to retrieve any information from it over Modbus (RTU or TCP). The device did not answer to any Modbus request.

As it stands now, I cannot confirm if this integration will ever work with such installations.

More info in #498

[tmycgn]

Thanks for the information @Roving-Ronin, that saved me a failed invest (sDongle). :) No, I haven't tried it yet as I don't have the system yet. The reason was to verify it in advance. But if I will try it and post it here. ✌️

[Roving-Ronin]

@tmycgn as in you don't have an EMMA, or don't have the Huawei inverter yet? If you haven't got the inverter yet, IF your a 3 phase user (i.e. getting say an M1 inverter), then it wouldn't be a failed investment as some models of inverters (such as the M1) actually come bundled with an sDongle from the factory. Alas 'some' installers like to pocket them / add them to the quote as an optional item for additional cost (cost AUD$99 wholesale typically).

[abrandl70]

Not sure if this is old news, but I can confirm that EMMA and Dongle don’t work together. I had a new installation 3 weeks ago and the EMMA only found the other devices after the Dongle was removed from the installation.

[SwissDani]

I have installed an Emma A02. With the newest update (V100R024C00SPC100) dated 15.07.2024 I got a pdf for the MODBUS Interface Defintions. Maybe this can be used for the integration?
I have no experience with MODBUS. But I am an experienced .NET developer and would be happy to help / support with tests.

Additional Infos form the new Communication Matrix:

SmartHEMS V100R024C00 MODBUS Interface Definitions.pdf

[Roving-Ronin]

ATM I've only had time to list out the RO registers. Scratching my head re how to define the RW ones, let alone then needing to match them to existing registers/sensors. If they have the same register number then the existing entry can just be updated to add the target_device= option, however I have seen one or two already that actually have the same register number as an existing register, BUT are for a different function!.

RO registers, still needing filtering to see if existing can be used and also renaming to follow existing format (and add EMMA_ as a prefix) are:

Edit:

[Roving-Ronin]

Not used to GitLab, so doing my updates in GitHub, from where I'll then paste them into GitLab. As it appears to be GitLab updates into the GitHub Huawei Library (not the other way around).

I'm done for the night, but there's some updated code at: https://github.com/Roving-Ronin/huawei-solar-lib/blob/dfd6f5dce7d20052c3a35e01994bfa2c1a866950/src/huawei_solar/registers.py#L1302. This supercedes what I posted in the above post (that I'll now remove from there).

Line 1302 to 1465. Please note that the registers where the rn. is NOT then followed by an EMMA_ prefix still have to be cross checked and see if there's existing registers (with the same number) that can be used. Also need to see if the name of them needs changing to align with Thijs's format (currently just taken verbatim from the EMMA doco).

There's some comments in there also, such as Line 1347, that I have no clue has to define 'no default value', and others where they have to have a CLASS defined in register_values.py.

Thijs - Would you have an idea as to Section 3.3 'Register Definitions for a Charger' and how this should be defined? This appears to use some of the same existing register numbers, like 'Offering Name' (aka Model Name) on Register 30000. Does this need a:

a) target_device=TargetDevice.EMMA_CHARGER added? and;
b) EMMA_CHARGER_REGISTERS = { section created also ?

From reading the EMMA documentation and comparing to the last list of possible Huawei EV Charger modbus registers ( #491 (comment) ) this EMMA list looks like its a cut down list published via EMMA, in that is does't have any RW registers to allow setting Charge limits etc. So there would potentially still be a 'full blown' EVCharger list of registers to add seperately in future / for people not using an EMMA.

[tmenguy]

Hey, great and thx to start the mapping! ... but just to be sure, as of now no one has been able to connect to an EMMA, correct?

[tmycgn]

@Roving-Ronin I just asked the Huawei Support / Product Team again about the RW registers for the EV Charger via the same ticket I used on July 9th to request the creation of the Modbus definitions. Thanks for the hard work in adding the RO registers, the extraction via the 4o gpt bot failed after hours due to the amount of data. :/

[wlcrs]

I've implemented initial support. Please go to #498 (comment) for more information.

This is untested, so I'm 90% certain that it will (partially) crash. If somebody is willing to provide me with remote access to an EMMA installation, then please give me a shout.

[Roving-Ronin]

Thijs,

Looking at the Huawei Library and in registers.py you've added some example EMMA entries, and updated some lines where EMMA and existing devices share the same register, i.e. 30000). I also note that a while ago you added a separate section for EMMA registers, at line: 1270

Should we be placing registers that are shared/common between EMMA and existing devices in the section starting at https://gitlab.com/Roving-Ronin/huawei-solar/-/blob/master/src/huawei_solar/registers.py?ref_type=heads#L741
and EMMA only/specific registers in the EMMA section starting at line 1270?

If so, then https://gitlab.com/Roving-Ronin/huawei-solar/-/blob/master/src/huawei_solar/registers.py?ref_type=heads#L746 and https://gitlab.com/Roving-Ronin/huawei-solar/-/blob/master/src/huawei_solar/registers.py?ref_type=heads#L771 will also need to be moved the to EMMA specific section.

Also I note in the modbus register documentation reference to a 'U64' and 'I64' type of register, that appears to be new. Is this something that you are able to add support for (in ???).

Thanks.

[wlcrs]

Yes, move them to that EMMA section. I've added U64 and I64 register support on the feature/emma branch.

[wlcrs]

I've integrated a small part of your work for now. I think it is important to first validate that we are able to properly retrieve those first few registers before doing all the dull work of inputting in the registers.

[Roving-Ronin]

Hi Thijs,

Agree, as you've posted on the other threads, now we just need some of these EMMA owners to test and assist.
PS, apologies been flat out last week or so with day to day work.
Let me know when/what is needed for doing some more of the 'dull' work, post user feedback.

On a side note, I think we are still waiting for one user to see if he has luck getting Modbus info for the EV charger. Given EMMA appears to have some registers for it, but they appear to only be a limited subset versus the expected list (or Emma ones dont include active power info or stop/start charge iirc).

[StefanOltmann]

I managed to update my EMMA to the recent update.

Did anyone manage to receive valid values so far?

If I run this script I always get "Slave Device Failure":
https://github.com/StefanOltmann/sun2000_modbus_test/blob/main/src/main/kotlin/Main.kt

Encryption is disabled, client IP is set to the computer executing the script.

[SwissDani]

Hi Stefan
Today i cloned your repo to try it with my EMMA.
Unfortunately, I was not successful. In EMMA I activated ModbusTCP without TLS and set the client IP of my laptop. In your code I set the correct local EMMA IP. Unfortunately, I cannot establish a connection. Do you have any idea what else is needed?
My Emma is connected via WIFI and not via LAN. The laptop is in the same WLAN.
However, the WLAN is not the installer WLAN of EMMA.
I double-checked the IP addresses via the router.

[StefanOltmann]

My EMMA is connect through LAN cable, but I’m certain that if must work via WIFI.
It worked with the dongle over WIFI before, so I don’t see why it shouldn’t.

What error message do you get?

[SwissDani]

Just a normal java socket exception. Like something is blocked or EMMA is not actually listening on port 502.

[StefanOltmann]

Did you verify using nmap -p 502 that the port is open?

Maybe there is some kind of firewall in between.
On Windows you may try to pause the Windows firewall.

[SwissDani]

There should be no firewall. Windows Firewall outgoing is open and my laptop and EMMA are in the same subnet.
I will try by LAN next week. Maybe I have more luck.
Thanks for your help.

[onkelandy]

I'd love to test this, however I'm too stupid. I have connected to EMMAs WiFi to update to the newest firmware. I can make it connect to region003eu5.fusionsolar.huawei.com on port 27250, but cannot find anything about ModbusTCP activation. I only have a user account though, do I need an installer account for making it work?
Port 502 on internal LAN is closed, when doing a port scan 31220 (unknown), 31221 (ftp) and 31240 (ssl) are open.
When running the Main.kt script I got connection refused of course (or read time out when trying one of the above ports.. no wonder ;))

[StefanOltmann]

You need to use the installer access in the FusionSolar mobile app - the web app won’t work.

your installer needs to tell you the password.

If you have the recent firmware you can activate modbus in the settings.

The port will only show up if you explicitly scan for it.

[m1h5]

Could you please describe where I can find the ModBus settings in the FusionSolar app? I have installer access, my EMMA is running firmware V100R024C00SPC100 and on my iPhone the most recent version of FusionSolar app. However I just can't find any ModBus settings.
I was told that these settings can be found in Devices -> Emma -> Parameters, but theres nothing ModBus related.

[tmycgn]

@m1h5 Check here: #498 (comment)

[zekolosse]

[zekolosse]

c is all good it works I restarted the whole and I was able to configure the system. thank you very much

[Geroldin]

Hi all,
i'm still new to Huawei Solarsystem but been following this integration for some time now.
My solar system was installed this summer with the following setup.
Emma A02 - RS485 (CAN-Bus) - Sun20000-8KTL-M1 Inverter - Directly connected - LUNA20000-10KW-C1 Battery Controller with Luna2000-7-S1 Battery
The Emma is connected via WAN Port to my Home lan and as soon as I get the install codes I should be able to manage the above part of my installation (should be happening next week).
However, in addition I have a Huawei SCharger-22KT-S0 which is connected to the Emma LAN Port to support "PV Power Preferred" charging.
Are there any plans to integrate the Charger in this constellation? I've read in the "Issues" Section that the Charger will not be supported directly which I can understand. However, since here the Emma is used and it's already supported I was wondering if there are any plans for this?