[APP][Pro] Huawei FusionSolar Manager

Right now I use the following registers which fully work if there is only one battery:

BATTERY_REGISTERS

Register Länge Typ Beschreibung
37046 2 UINT32 Max Charge Power (W)
37048 2 UINT32 Max Discharge Power (W)
37760 1 UINT16 State of Charge (%)
37762 1 UINT16 Battery Status (Running State)
37765 2 INT32 Charge/Discharge Power (W) — + = Laden, − = Entladen
37780 2 UINT32 Total Charged Energy (kWh)
37782 2 UINT32 Total Discharged Energy (kWh)
37784 2 UINT32 Today Charged (kWh)
37786 2 UINT32 Today Discharged (kWh)

STORAGE_CONTROL_REGISTERS

Register Länge Typ Beschreibung
47075 2 UINT32 Max Charge Power Setting (W)
47077 2 UINT32 Max Discharge Power Setting (W)
47081 1 UINT16 Charging Cutoff Capacity (%)
47082 1 UINT16 Discharge Cutoff Capacity (%)
47086 1 UINT16 Storage Working Mode
47087 1 UINT16 Charge from Grid (0=Disable, 1=Enable)
47088 1 UINT16 Grid Charge Cutoff SoC (%)
47100 1 UINT16 Force Charge/Discharge (0=Stop, 1=Charge, 2=Discharge)
47102 1 UINT16 Backup Power SoC (%)
47242 2 UINT32 Grid Charge Power Setpoint (W)
47299 1 UINT16 Excess PV Energy Use in TOU
47589 1 UINT16 Remote Charge/Discharge Control Mode

Eventually I have to add a second type of driver for this case.

Based on the list on Sun2000 Modbus Register – Debacher-Wiki there are additional registers for Energy storage unit 1 and Energy storage unit 2 which could solve your problem. Right now, I just use the generic ones.

Ok cool! I guess that the issue then. If you implement the second one that might work for me. I added the dongle as its own unit now and it gives to total amount from both batteries, you can see the difference in the picture. Lets see if the dongle is enough, I haven’t thought about my use cases yet, was just so happy today when I found a new potential working app :slight_smile:

About the sDongle: The sDongle should show the overall consumption and should be exlcuded from Energy. Otherwise the Homey Energy Dashboard will show wrong values.

Please install the TEST Version of my App:

And send a screenshot of the output:

Found the issue. My 2 AP’s have upgraded yesterday evening/night but not my router so they didnt get along very well this morning. Upgraded the router and it came alive and have worked witout issues sins. Will see rest of the day and tomorrow. But i dont think it is a issue anymore. Thx for checking for me :slight_smile:

Yes, the dongle should be handled like most of the overall energy monitors, i.e. not included

I downloaded the test version and this is how it looks:

Your screenshot shows no installed unit 1 and 2 and only 1 module. This means, that there is no other battery so far.

Which exact models are u using?

New Debugging Features in Version 1.1.23

  • Automatically scans your entire network, detects Modbus‑enabled devices, identifies open ports and Unit IDs, and recognises Huawei devices using register‑based fingerprinting
  • Capability overview for installed devices
  • Displays live Modbus register data for real‑time diagnostics for installed devices

Aufzeichnung 2026-05-10 172446

That’s how it should look like:


tonight it should value, strange indeed… I have luna2000-1, 2 of them

Been trying the new scan feature and it doesn’t work that well on my network..

A few minutes back it found 2 devices on unit 1, now nothing and it doesn’t find any on unit 2

Not sure if it depends on that modbus is to “hectic”

I guess my setup is in some way strange.. I have had problems with other integrations, we have an app called Tibber in Sweden which deals with the electricity and when they integrated to Huawei it didn’t work with my setup either, I needed to turn of the integration and the developers didn’t find why it behaved so strange

Would be interesting to see if someone else with double inverters and double batteries with one S-dongle could get this to work

@Tjoloho
Now it’s clear that this Unit ID only contains a single module, so using the module‑specific registers would definitely not work from my understanding:

Modbus can be really unreliable. Sometimes you get a response, sometimes the device is busy handling other requests. The best approach is to increase the polling interval on all devices so the regular polling doesn’t block the port while the connection tester is running.

Could you please run the scanning tool several times? Eventually it should return a response.

BTW: That’s how it should look like:

been trying for 41 minutes :wink:

this is the only result I get on device 1, not even the battery 1 ends up :slight_smile:

@Tjoloho
:frowning:

Firmware up 2 date?

How old is your SDongle?
I’m asking because I replaced mine about six months ago — the old one from 2021 had become really slow. This post helped me understand how the replacement should be done.**

Das Elend mit dem langsamen Huawei SDongleA-05 hat ein einfaches Ende · evcc-io/evcc · Discussion #22534

After the replacement I had the following additional option in Fusionsolar (Do you have this option “real time data”?):

Hey, aha! Yeah the problems they described in that thread is similar to what I experienced over the years, trying to get modbus working properly, but I always have given up…

I don’t have the option you showed in your Screenshot. I contacted my installer now and he will send me a new one he had laying around.

Let’s see in a few days

By 2 inverters, do you also mean, for example, one from Huawei and one from SMA? Does your power from SMA run on the battery?Do you have this problem too?

I have 2 sun2000 inverters and 2 luna2000 batteries. Each battery is connected to respective inverter and one battery is 5kwh and one is 10kwh.. we built this setup to extend the battery capacity over time to 30kwh in total.. and there is one dongle steering both pairs

1 smart meter

I’ve added several new features to the Device Tester. You can now check each device individually, and if a connection fails, the previous results for that Unit ID are preserved.

Please check again if you’re able to detect teh second battery on another Unit ID

Hey, tried it out.. Was able to identify all devices on unit 1 but then when I tried to check Unit 2 I couldn’t do so, since they where reserved on unit 1, not sure if it was intended that way?

to test unit 2 I needed to restart the app, since you cached the data :slight_smile: and then I was able to identify the battery on unit 2, yaay

but still can’t add it :slight_smile:

@Tjoloho
Please try debugging the device and adding the battery using version 1.1.28

Hey! Did you do something else in this version? Now after 2 attempts I was able to add it(not sure if it behaves correctly yet.. but its there :slight_smile:

Hopefully not the same device twice :nerd_face: