Hey Andi, thank you very much for this App! I used the other SolarEdge / Growatt app to control my battery earlier, but had problems with the force charge / discharge, as the parameters in FusionSolar regarding the time and charge/discharge were erased from time to time, causing my actions in Homey to not do anything. This app you’ve developed seems to remove that obstacle, at least regarding Charge. Will perhaps “Start Force Discharge” also come as a card?
Hi Andi! Brilliant integration for Homey. Been waiting for an app like this. Cudos!
Everything works great except getting data from the smart charger. I have an Emma and the inverter, powermeter and battery works flawlessly. The smart charger can be added using modbus on EMMA, ID 1, but my HomeyPro tells me the device is not available. No data is fed. The charger can be seen in the FusionSolar App so communication works to EMMA. What am I missing?
Changed to MODBUS ID 8 and got some data, but not all, especially not the one I’m most interested in → “Charging Power”. How do you find the right ID? I assume they are assigned during installation of the system and are not fixed to specific values?
Have been fiddeling a litle i think a change is needed so people dont miss set things assuming to much… I saw you created a card for “Start charging with W untill SOC %”
Could you create 3 more .. end result should look like this then:
“Start charging with W untill SOC %”
“Start discharging with W untill SOC %”
“Start charging with W for duration minutes”
“Start discharging with W for duration minutes”
FYI @Andi if you try to send one of the new starting cards if it already is in that state you get a network error. They work just that they trigger a network error if already in the state. I put a temp solution in with 2 AND cards for checking your not in the state your setting.
I see. The value is not available … as of now anyway. Too bad. Perhaps the FusionSolar app is calculating the value somehow, because I can see the value when accessing the charger in the app.
Still super happy with this app for homey. Great job Andi!
Is there anyone else who has a Homey 2019 and experience same issues?
I own a Homey 2023
-Could be a ressource issue (pause some other apps)
-Could be something in the background (f.e. npm version Homey 2019 could be different to Homey 2023 and incompatible to my app)
-could be a limitation from the system itself
-latest firmware installed?
After tossing my modbus-based solution out, I’ve switched to this app to control inverter and battery but I’m stuck at controlling operational mode, register 47086. Am I missing something or is it not implemented? Together with the registers for maximum charge/discharge power - 47075/47077, which I use to prevent battery drain at the wrong times - those are the ones I have the most use for - any chance they can be added if they’re missing?
Good news — all three registers are already implemented in the app, but register 47075/47077 are exposed in a way that might not be immediately obvious.
Register 47086 — Storage Working Mode
Fully supported. It’s mapped, read back every 5 poll cycles, and wired to the “Set storage working mode” flow action card (luna2000_set_working_mode). You can switch between Adaptive, Fixed Charge/Discharge, Maximise Self-Consumption, TOU, Full Feed-in, and Third Party — both from flows and from the device settings panel.
Registers 47075 / 47077 — Max Charge / Max Discharge Power
Also implemented, but currently exposed as device settings rather than flow cards. You’ll find them in the LUNA2000 Modbus device settings panel as “Max charge power (W)” and “Max discharge power (W)”. They sync from the inverter every 5 poll cycles and write back to the inverter when you change them manually.
The catch: there are no flow action cards for these two registers yet. So while you can set them manually in the device settings, you can’t currently automate them through Homey flows (e.g. “when electricity price is low → set max discharge power to 0 W”). That’s probably the gap you’re running into.
That’s awesome, thanks - I thought I’d checked all the different registers but clearly missed 47086. The other two can be in a flow but via calling a script to set them - I’ll try that for now.
Looks like the Max grid charge power (W) doesnt want to pick up the correct value from the registry. I have it at 6500 but the batteri device thinks it should be 15000 regardless what i do. Tried restart app and so on.
Perhaps the FusionSolar app is calculating the value somehow, because I can see the value when accessing the charger in the app.
