How to detect 3rd party meter HUAWEI DDSU-666-H connected to EMMA

[artcrime]

Hi,

I have an 3rd party meter connected to EMMA and it is detected by EMMA and shown inside the Fusion Solar App. It should be detected by the Home Assistant Integration too but I dont find new entities after the reconfigure.

Anybody here who knows a solution? I tried to delete the integration and to reconfigure without success. After the reconfiguration I find three modbus slaves 0,4,6 (6 is the wallbox) the other ones are the battery and the inverter? Should the be a slave for the 3rd party meter too?

I query the EMMA via modbus TCP

Regards

[Bernd-Reibeholz]

Sorry no help, but propably additional information.
I got a DTSU-666-H to measure a third-party-PV which is connected to the Emma (in a SmartGuard 63). The AC of the third-party-PV gets into the Non-Backup and it is working perfekt with FusionSolar (even loading the Luna through the MAP0 when the third-party-PV produces more then I consume).
In the entities there are some of them twice as "WIRKLEISTUNG". The first one shows the correct Values but the second one is "0" all time.

I use the Network-Connection with lan to Emma, port 502 ,Slave IDs (AUTO, changed to) 0,3 and "Fortgeschritten: Berechtigungen erhöhen" enabeld

sorry for language-problems

[artcrime]

Sorry had no time to search further on my problem but I am still searching. I already tried AI help and it mentioned that EMMA is the modbus device for the external meter and I should use address 37119. But I can not not add another modbus configuration inside HASS because of EMMA does not allow more than one connection.

Meanwhile I dont think the external meter has a own modbus address (but it is configureable by the display of the ddsu and it is 11 now)

So I think something is not detected by the Huawei integration. I activated all entitys called "Wirkleistung" (I am german too). But nothing happens. It does not count anything. I although have lot of entitys which are shown 3 or 4 times and when I activate one of them the integration stops working or shows "unknown". For example "A-B-Netzspannung" is shown 4 times.

Perhaps I have to delete the whole configuration of the huawei intergation? I dont know how. Where are the files that have to be deleted or what has to be done?

Any help in debugging this thing?

[ManfredGiesinger]

No solution, but some additional information as I use the DDSU666-H too.

1. Additional MODBUS connection to EMMA is no problem with HA App “modbus-proxy”. The Huawei Integration and my warmwater management SmartFox access EMMA without any problem. Even additional connection with QModMaster for tests works fine.
2. I did some test with RTU where I was able to access all the possible registers mentioned here even for us only Power and Energy register would be interesting:
   https://github.com/bcdiaconu/chint-mqtt-modbus-bridge/blob/main/docs/DDSU666-H.md
3. As I did some test with AI support too, without success. What I can tell you, the mention register 37119 didn’t give anything back.
4. My Workaround for the Moment is an additional Shelly PM1 for measurement power and energy.

[ManfredGiesinger]

After playing around to long today, that is the outcome with AI (Translated with DeepL.com from German (free version):
Bat great that AI recomend my workaround at least too. ;-)

This is a typical issue with systems using the Huawei EMMA: as you cannot find the data in Home Assistant’s entity list at all, the EMMA completely blocks this data at the software level for Modbus clients. Although the EMMA reads data from the DDSU666-H locally via the RS485 interface, it uses the data from the small PV system exclusively internally to perform its own HEMS calculations (e.g. for battery control or self-consumption optimisation). It does not reflect these values back into the Modbus data tree for external queries (such as HA or qModMaster). The HA integration therefore does not detect these sensors at all. However, as you absolutely need these values for power and energy, we must bypass this blockage either at the hardware or software level. Here are the only three solutions that work for your setup:

Solution 1: Hardware split of the RS485 bus (the cleanest method) As the DDSU666-H is a standard Modbus RTU meter, you can simply query it in parallel. To do this, the meter must not be connected exclusively to the EMMA. How it works: You connect an inexpensive RS485-to-Wi-Fi gateway (e.g. a Waveshare RS485 TO POE ETH or an Elfin-EW11) in parallel to the RS485 A/B line between the DDSU666-H and the EMMA. The result: the gateway reads data directly from the DDSU and makes it available on the network as a separate Modbus TCP server. In Home Assistant, you can then integrate the small PV system as a native Modbus meter, completely independently of the Huawei integration.

Solution 2: Using a Shelly Plus 1PM (the simplest method) As the small-scale PV system is a single-phase system (balcony power station / small-scale installation), the DDSU666-H is often ‘overkill’ for Home Assistant. How it works: You install a Shelly Plus 1PM or Shelly Pro 1PM in the supply line to the small-scale PV system. The result: The Shelly transmits power (W) and energy (kWh) directly via Wi-Fi (or LAN) to Home Assistant. You get data accurate to the second, you don’t put a strain on EMMA’s Modbus proxy, and you can use the values immediately in the HA Energy dashboard. The EMMA continues to use the DDSU for its own purposes in the background.

Solution 3: Using the Huawei FusionSolar Cloud API as a workaround. If you do not wish to install new hardware, you can retrieve the data from the Huawei cloud. The EMMA does, in fact, upload the DDSU666-H data to the FusionSolar portal. How it works: You install the FusionSolarKiosk integration or a comparable OpenAPI integration in Home Assistant via HACS. The downside: Huawei only updates the API data every 5 to 15 minutes. This approach is unsuitable for live dashboards or rapid automations, but it is sufficient for a daily energy dashboard. Would you like to know what the YAML code for Home Assistant would need to look like to read the DDSU666-H directly via an RS485 network gateway (Solution 1) as a standalone meter?