I’ve just released a new Homey app for Huawei FusionSolar solar plants — supporting Kiosk, OpenAPI, and Modbus connections.
The app offers three fully independent integration methods: Kiosk URL — simple plant-level access without needing an account FusionSolar Northbound OpenAPI — official cloud-based data Direct Modbus TCP — communicating locally with the SUN2000 inverter, LUNA2000 battery, and DTSU666 smart meter (this is the recommended and most capable option)
Each device type is added to Homey as its own device.
• SUN2000 inverter: solar power, PV string voltages and currents, daily and total yield
• LUNA2000 battery: state of charge, charge/discharge power, plus full control of the storage working mode
• DTSU666 smart meter: three‑phase grid import/export, fully integrated with the Homey Energy Dashboard as a P1‑class meter
• Kiosk & OpenAPI devices: plant‑level daily, monthly, and yearly energy statistics
All measurements are available in Homey Insights and can be used in Flows — for example to start a heat pump when export begins, or to shed loads when the battery state of charge drops below a chosen threshold.
Feedback, bug reports and pull requests are all very welcome — either here in the thread or directly via GitHub Issues.
I just installed it. Connected through Modbus. Looks good so far. I like the fact that I finally have a full view on my battery in the Homey Energy tab.
I’ll keep an eye on it for a few days. If everything works out, this will probably end up replacing my custom solution built on the Modbus and Device Capabilities apps.
Installed it. Realy nice work. Running modbus devices all 3 types. It have everything you can want so far in term of abilities i gues the people with emma devices will ask you for a additional device for that. Love the battery in energy tab now i can remove my workaround solution for that.
Thank you for all the feedback so far — it really helps to improve the app. If you run into any error messages, it would be very helpful if you could share a screenshot along with details about the devices you’ve added.
I’m currently testing with my own setup (SUN2000 inverter, DTSU666 power meter and LUNA2000 battery), so I can only validate everything on these devices.
If anyone is willing to help test additional or different devices, I’d be more than happy to collaborate and support the process.
Thanks for reporting this! This is a known quirk with Huawei inverters and SDongles — they occasionally reject the first incoming TCP connection when their internal connection slot is busy or recovering. A second attempt right after always works because the slot is free again by then.
I’ve pushed a fix in the next version: the app now automatically retries once (after a short pause) when the first connection attempt fails during pairing. You shouldn’t need to hit “Connect” twice anymore.
Ik heb thuis 1 omvormer van SMA en 1 van Huawei met een batterij van huawei.
Wat dien ik aan te klikken om deze te installeren.
Ik zie dat er een apart batterij en een apart omvormer staat, ook zie ik dat er “fusion solar plant” is. Is dit dan het beste om deze 2 samen te nemen ( batterij en huawei omvoermer?)
Wat is het beste om te doen => API of Modbus?
We hebben ook een energie meter tussen de beide omvormers staan. zo dat de huawei de stroom van de SMA niet als “vreemd” bekijkt. Graag had ik deze gelinkt met huawei batterij zodat de stroom die over is van de sma naar de batterij kan gaan. Welke meter dien ik dan te installeren?
Just installed it and works great with EMMA (Unit ID 0) and LUNA2000 S1 (Unit ID 2) via Modbus TCP port 502!
However I can’t get any data from the SUN2000-M (3-phase) inverter. It connects without error but all values show “56 years ago”. Tried Unit ID 0-11, ports 502 and 6607 — no luck.
My setup: EMMA-A0x → SUN2000-M (3-phase) connected via RS485. EMMA is on WiFi.
Any idea what Unit ID or settings I should use for the inverter via EMMA?
Dear Andi. I have a Huawei Solar Inverter SUN2000-8KTL-M1. I also have a profile on the Fusion Solar via web + smartphone app. On this profile, the inverter is connected. The inverter itself, is connected to my Deco mesh wifi network via a Dongle. The dongle type: SDongleA-05. I tried to connect to the inverter in the app you created.
I tried via OpenAPI. There I entered my Username and Password, the same I use accessing Fusion Solar webapp. However, I get the following notification: ‘Login failed (20400): Invalid username or password’. This is not possible as I do get access to the Fusion Solar webapp using exactly the same credentials.
I also tried to login via Modbus. I found the IP address on the Deco mesh app. I entered the IP address, tried both the port nr. (502 and 6607), left modbus unit id on 1. After clicking on connect, I get the following notification: ‘Socket error: connect ECONNREFUSED 192. (..ip adress).
Do you know what the reason is for the inverter not being able to connect?
I have one SMA inverter and one Huawei inverter with a Huawei battery at home.
What do I need to click to install these?
I see that there is a separate battery and a separate inverter listed, and I also see “fusion solar plant”. Is it best to combine these two (battery and Huawei inverter)?
What is the best option => API or Modbus?
We also have an energy meter placed between the two inverters so that the Huawei does not view the current from the SMA as “foreign”. I would like to link this to the Huawei battery so that any remaining current from the SMA can go to the battery. Which meter should I install then?
I’ve received your diag: There is no error but i found the source of the problem –> Control registers written back on every app start
Fix: A flag _updatingFromModbus was introduced in both drivers. It is set to true before any setCapabilityValue() calls originating from a poll read, and reset to false afterwards in a finally block. All write listeners check this flag and return immediately if it is set, ensuring that only explicit user actions (UI or Flow) trigger Modbus writes.
Kiosk URL — simple plant-level access without needing an account
now i can remove my workaround solution for that.
