I’ve just started trying to configure my new system and having the same issue so you’re not alone. It simply won’t let me complete the configuration and jumps back to the start page. (Site ID 919609).
Okay, at least I am not alone. Have you received any further feedback from Victron?
No nothing yet.
@dfaber can you help??
Hi @Buddinski88 & @Chris_Roberts ,
We’re looking into it! Expecting it to be fixed tomorrow, don’t have a clear cause yet.
With kind regards,
Jarco
Hi Jarco, thank you very much for the reply. If you need any further information, let me know 
Mind sharing the vrm id this is about? (The nr in the url).
Morning @Buddinski88 & @Chris_Roberts ,
The DESS configuration loop should be fixed, sorry for the inconvenience!
Please do let me know if something’s still not working as expected
With kind regards,
Jarco
Hi Jacro,
Awesome. I just finished setting it up without any problems 
Thank you so much, and best regards,
Bastian
Thanks Jarco. All sorted.
Chris
good morning,
I found no way to DM you, so here is my vrm ID: 742544
In fact I stopped the DESS-experiment today, because I can’t understand the decisions made by the system. I attached the forecast for today.
My settings are / were:
Can you sell energy back to the grid? Yes
Maximum import power 15 kW
Maximum export power 5 kW
Operating mode Green mode
Battery energy capacity 32 kWh
Maximum discharge power 30 kW
Maximum charge power 30 kW
Battery costs 0.05 €/kWh
Buy prices fixed
00:00 - 05:00 € 0.175
05:00 - 23:59 € 0.275
Sell prices type dynamic
Energy provider country: Germany
greetings
Christian
What does the next day’s prices and forecast look like? Always include the next day on your posts for clarity.
I would understand this grid charging behavior if the next day would have a spike in the spot prices and your solar production is not sufficient to 100% top up the battery today from the sun.
I got the octopus go tariff here in germany, so my prices are always the same:
5:00 - 24:00 27,5 ct
0:00 - 5:00 17,5 ct
the solar forecast for the day shown was big enough to get to the next low price zone in the night. next day’s solar forecast wasn’t great, but the right behavior would have been, to wait for the low prices in the night, and not to charge in the high price hours.
In addition, the system sold 1 kWh to the grid at 7:00 (little turquoise), to buy it back at 9:00.
Same here. It will not disable.
I have a Victron system (3× MultiPlus II with Cerbo and Cegasa batteries) along with two PV systems (Fronius and SMA, 9.46 kWp). When I enable dynamic settings, the battery charges from the grid at the scheduled times, but the PV system no longer feeds into the grid—it seems to be curtailed.
How does Victron handle this, and how can I change it? The PV system should still be allowed to export power, but the battery storage should not.
I have got a single phase Multiplus 3000 GX with 9.6 kWh Pylontech batteries. Just two weeks ago I configured the sell price in the DESS settings. Since then nearly every morning between 5 and 8 the multiplus drains the battery nearly to 20 % SOC.
Hence there is often no sufficient energy to support any loads that are bigger than the actual PV power. So power from the grid is fed in.
How can I limit this? I would eager maintain the battery SOC and sell the PV surplus during the day to the grid (less inverter losses).
installation ID 754672
Hi, if you want me I can have a look and find out which setting might have triggerd the behaviour.
Feature Request: Separate “Minimum SoC for Grid Discharge” setting in Dynamic ESS (DESS)
Hi Victron / DESS Development Team,
I would like to submit a feature request for Dynamic ESS that I believe would greatly improve system resilience and user confidence, especially for prosumers operating in grid-constrained areas.
Proposed Feature:
Add a dedicated setting in DESS: “Minimum SoC for Grid Export” (or Grid Discharge Cut-off SoC), independent of the system’s overall “Minimum SoC” (used for loads and backup power).
Use Case & The Problem:
In my setup (MultiPlus-II 5kVA, Cerbo GX, ~30 kWh LiFePO4 battery, 16.8 kWp PV array), I face two conflicting realities:
-
Grid Overvoltage at Peak Solar Hours: During sunny days, local grid voltage routinely exceeds 250V+ due to high density of feed-in prosumers. To prevent MPPT derating or grid tripping, I need a partially discharged battery around midday (~50% SoC) to act as a buffer/sink for local PV power.
-
Unpredictable Weather Forecasts: DESS often plans an aggressive morning battery discharge into the grid (e.g., down to 20% SoC) expecting high PV production later. If the weather turns out cold, cloudy, or rainy, the forecast fails, leaving the battery depleted at 20%. The system is then forced to buy expensive grid power for home loads throughout the day.
The Current Dilemma:
-
If I raise the System Minimum SoC to 50% to protect myself from forecast failures, DESS stops discharging to the grid at 50%, BUT I lose the lower 20%–50% capacity for home consumption during cloudy periods or grid outages.
-
If I keep System Minimum SoC at 20%, DESS risks discharging the battery all the way to 20% into the grid on bad forecast days, leaving zero buffer for the house.
Proposed Behavior:
Having two separate parameters would solve this completely:
-
System Minimum SoC (e.g., 20%): Hard lower limit for home consumption / grid outages / backup protection.
-
DESS Grid Discharge Min SoC (e.g., 50%): The limit at which DESS must stop discharging the battery into the grid.
Example Workflow: In the morning, DESS can trade/export battery energy to the grid, but only down to 50% SoC.
-
If PV generation at noon is strong, the remaining 50% capacity absorbs the local PV surge (mitigating high grid voltage).
-
If the PV forecast fails completely, the house still has a 50% → 20% SoC buffer to powered loads without importing expensive grid energy.
This granular control would make DESS significantly safer to run in Trade Mode without fearing forecast miscalculations.
Thank you for considering this enhancement for future VRM / DESS updates!
Best regards,
Paul
I have voltage problems in my area arownd midday, the voltage goes up to 250V
This is why I want to charge the battery from 11:45 to 15:45 . This is what I need to put in the DSS, low price on export energy between 11:45 and 15:45
I did that, but DSS has a strange behavior, doesn’t charge the battery with the same amount of current, sometimes it stops charging and voltage goes up again to 250V. Easy task but the software is so bad that it is almost impossible to make it work correctly
Any Ideeas ?
Feature Request: Configurable Operating Reserve for Dynamic ESS
Hi Dirk-Jan and the Dynamic ESS team,
First of all, I’d like to thank you for all the work that has gone into Dynamic ESS. It is an impressive system and, overall, I’m very happy with it.
After using Dynamic ESS for several months, I have noticed what I believe is a limitation in the current optimization strategy. I don’t think this is a bug, but rather an opportunity to improve the algorithm for a broader range of real-world applications.
My system
- Quattro-II 24/5000
- 3 × Victron Lithium NG 25.6 V 300 Ah (approximately 23 kWh)
- Cerbo GX
- Dynamic ESS (tested in both Green and Trade mode)
- Dynamic electricity contract (Netherlands)
My installation is on a liveaboard sailing vessel rather than a typical residential home.
I’ve experimented with Green Mode, Trade Mode, different battery cost settings and BatteryLife. While each option changes the behaviour, none of them solves this specific use case. That is why I believe this requires an enhancement to the planning algorithm rather than a different configuration.
The challenge
Unlike many residential PV installations, my daytime energy consumption is usually higher than my solar production.
For example:
- Solar production: 8 kWh
- Daily consumption: 12–15 kWh
As a result, the battery gradually discharges throughout the day.
Dynamic ESS optimizes the battery towards the configured Minimum SoC (for example, 30%). From an optimization perspective, this is exactly what the system is designed to do.
However, in practice this creates a problem.
By the time the battery reaches the planned Minimum SoC, there is no remaining energy reserve for unexpected loads.
Typical examples include:
- Washing machine
- Kettle
- Boiler
- Oven
- Air conditioning
If one of these appliances is switched on during an expensive tariff period, the system immediately has to import expensive grid power because the battery has already reached its planned operating limit.
This is not a bug
I don’t believe this is a software bug.
It is simply a consequence of optimizing based on forecasted consumption.
Real-life consumption is rarely identical to the forecast.
Green Mode versus Trade Mode
Trade Mode is too aggressive for my application.
Green Mode behaves much better, but both modes still optimize towards the configured Minimum SoC.
The only practical workaround is increasing the Minimum SoC to 40–50%.
Unfortunately, this permanently reduces the usable battery capacity, even on days when such a reserve is unnecessary.
BatteryLife is not an ideal solution either, since it was designed to protect battery health rather than to maintain an intelligent operational reserve.
Feature request
Would it be possible to introduce a configurable operating reserve?
For example:
- Reserve 2–5 kWh for unexpected consumption
- Keep X% above the Minimum SoC until the next cheap charging opportunity
- Maintain an evening reserve before high-tariff periods
The important distinction is that this reserve would only influence the planning algorithm.
It would not become a new hard Minimum SoC.
The battery could still discharge below this reserve when necessary, but Dynamic ESS would avoid planning all the way down to the absolute minimum under normal conditions.
Why this matters
I believe this would especially benefit installations where:
- Daytime consumption exceeds PV production.
- Users have dynamic electricity tariffs.
- Batteries are primarily used to avoid expensive evening electricity rather than to maximize energy trading.
- Comfort and energy availability are slightly more important than achieving the absolute lowest theoretical electricity cost.
A different optimization objective
In my opinion, Dynamic ESS currently optimizes for the lowest expected electricity cost.
Many users, however, are actually looking for the lowest expected electricity cost while maintaining a reasonable energy reserve for unforeseen consumption.
These are two different optimization objectives.
Adding a configurable operating reserve would provide a valuable middle ground between Green Mode and Trade Mode, without fundamentally changing the existing optimization strategy.
Thank you again for all the work that has gone into Dynamic ESS. I hope this suggestion can contribute to future improvements.
Pepijn Hijdra