Hi Andi
Awesome - i’m in the process of getting a wallbox. Planned to do all this stuff in a advanced flow so looking forward to use that feature. Would it be possible to even have my luna (battery) as a priority? Use Case: i want all my pv surplus (in my head thats solar power - household | ignore battery power) to go to the car. i know in the end its the same but i’d prefer to have all the surplus in the car (maybe until xy %).
I have more use cases currently:
use the sgready pv mode when the battery is full. (shouldnt be an on/off thing - since the heatpump is changing the mode)
starting the dishwasher when xy Watt surplus is there (sep. flow)
Hi, thanks for the detailed feedback — very helpful!
EV vs. battery priority: the EMS already works the way you’re thinking. The surplus budget is calculated from the grid meter (export = positive surplus), not from the battery. So when the inverter is charging the battery and exporting at the same time, the EMS sees the export and sends it to the car — the battery doesn’t “compete” for that power. If you want to be more aggressive (e.g. temporarily stop battery charging to push more into the EV until it hits X% SOC), that would require setting the Luna2000’s max charge power via the new battery flow actions — possible, but needs a manual flow today.
SG-Ready PV mode when battery is full (and all other devices) The EMS is fully Flow-based — it fires trigger cards, and you decide what happens next. This applies to every device type: the EMS never sends commands directly, so you have complete freedom to wire any trigger to any action, combine conditions, or chain multiple actions in one flow. For SG-Ready: the ems_battery_full trigger fires once when SOC crosses the threshold, and you connect it to whatever SG-Ready action your heat pump app provides — the EMS just fires the trigger, the rest is your flow.
Do whatever you want with any device (Flows will be created initially with a flow card action and can be changed afterwards by replacing existing action cards or add whatevery is required - just make sure to not overwrite/update them again in the app):
Dishwasher / dehumidifier on surplus threshold can be added, if required
Wallbox tip If you haven’t decided yet: I’m running an Easee and can recommend it. The reason it works particularly well with the EMS is 3-phase support combined with per-phase current control — the EMS can adjust in 1 A steps on each phase independently, which gives very fine-grained control over exactly how much surplus goes to the car (minimum ~1.4 kW on 1 phase, up to ~11 kW on 3 phases). Single-phase-only chargers are limited to 6–16 A on one phase, so you lose a lot of the precision.
Thx Andi I will check it out. Just had a 5min quick check on the new EMS device today morning
I’m going for the go-e charger gemini flex, that should also have that option. Thx for your effort, let you know when I invested some time with the options.
I have currently 7000 Watt “Maximale Ladeleistung” so there is never an export (max. my inverter can produce is around 7000 watt). I’d love to set the max charge power with a flow action, but i have a follow up question:
This flow card sets the following values in the fusion portal (EMMA Navigation)
-> isn’t that the value for the maximum charge from the grid? (AC charge power… i never charge my battery from the grid, used it sometimes when i had Hochtarif/Niedertarif to fill the battery with cheap energy but we only have one tarif now)
i’m missing the flow card for the max. charge power from the inverter → in my opinion this one from the portal
tried to add the luna200 via modbus (none emma) but none of the unit ids are working (with the scanning option or a manual try to connect). maybe i have to go with the option via TOU option. or maybe i’m missing something to add it as normal lunda2000 modbus.
EDIT:
the inverter (direct modbus) unit id 2 is green, but not the luna
Those values is the correct once. The card used to work but stopped working a while back. What do the partial write failure indicate? I tried a diff value (5000) an hour ago (sins you wrote last time you had tried 5000 on your system) on the effect just as a test incase there was a check against the max discharge setting. Sins i have the same value configured there to limit the max discharge limit when im not force discharging. Wish i remember in what version it last worked . But it worked from day one when i started using the app but stopped a couple of weeks ago. First i had problems with a AND card as you might remember. So it would have started just before that or around that timeframe.
This is how it looks in FusionSolar before execution and after no change at all. As you can see it retain the setting from my last run yesterday on the 50% discharge when i cut down the amount of stored energi on the batteri around 22:00 ish that i had to start from the FustionSolar app sins the flow card dont work atm for me.
Could you use a Huawei FusionSolar Manager — Modbus Debug Export? or you got that covered in the diag file?
Did a minor test just to verify what happensthe first 3 columns is me doing pre tests with the FusionSolar app to see what it actualy changes when i set force charge and force discharge. The last column is what forced discharge thru the card does. It looks like it is actualy changeing the 47247 registry entry but not the 2 others 47101 should have been 15 but remained 28 from the test in prev column. 47100 remained 0 when it should have been changed to 2.
After writing this i got an idea i was thinking on testing. Going to test individual flow cards for these
Using the individual flow cards for setting 47101 and 47247 works like a charm … BTW the set force SOC% target desc text say 47104 when it should be 47101 (Pure cosmetical but just so you know). When those 2 settings was set i tried to set the indivicual force start mode to discharge that should have set it to 2 but i got a error when trying todo it. It doesnt say why. So for me the 47100 registry thru the individual mode flow card doesnt work for some reason it bugs out on me.
