I have Installed another 64kWh yesterday and had set the new 214kWh Value in DESS settings, but it keeps ‘setting’ it to the old value 150kWh, i noticed this morning.
Is there a way to verify DESS still uses the new fed value 214kWh?
I did try to set the value in iPad VRM application, beta VRM and normal VRM but it keeps popping back.
Bump. METSTRADE came and went, a good moment to refocus on the year ahead. Therefore I am restating my request/proposal to make DESS a top level category on this forum. My key argument is that a successful future for DESS will require, by nature of the diversity of it’s use cases, a better managed and structured cooperation model between Victron and her most knowledgeable and loyal customer base. What about it @Barbara @guystewart @mpvader
I have the same issue. I am unable to update the battery capacity.
Well i looked in NodeRed for a solution, because DESS gets a bit confused if the SOC is not doing what it calculated.
You can set the value with NodeRed until the VRM DESS battery capacity UI send script is repaired.
If you import this nodes you can set it correctly and check the VRM DESS setting afterwards.
Adjust the inject node to your needed capacity and inject.
[
{
"id": "82413c4eeff5e264",
"type": "inject",
"z": "10d901f9c3a26388",
"name": "",
"props": [
{
"p": "payload"
}
],
"repeat": "",
"crontab": "",
"once": false,
"onceDelay": 0.1,
"topic": "",
"payload": "214",
"payloadType": "num",
"x": 950,
"y": 540,
"wires": [
[
"f262881ede2cc1c5"
]
]
},
{
"id": "f262881ede2cc1c5",
"type": "victron-output-dess",
"z": "10d901f9c3a26388",
"service": "com.victronenergy.settings",
"path": "/Settings/DynamicEss/BatteryCapacity",
"serviceObj": {
"service": "com.victronenergy.settings",
"name": "Venus settings"
},
"pathObj": {
"path": "/Settings/DynamicEss/BatteryCapacity",
"type": "float",
"name": "Battery capacity (kWh)",
"mode": "both"
},
"name": "Set Dynamic ESS Battery Capacity",
"onlyChanges": false,
"x": 1160,
"y": 540,
"wires": []
},
{
"id": "229f670bc28a5af8",
"type": "global-config",
"env": [],
"modules": {
"@victronenergy/node-red-contrib-victron": "1.6.55"
}
}
]
Hi @Ersus ,
This is fixed now! We were triggering a ratelimit between services.
With kind regards,
Jarco
Thank you for reporting back and fixing this.
In portugal, coopérnico has dynamic prices for selling and for buying, they offer the tri-horario, which has prices that are calculated in different times of the day using a different formula. It would be absolutely brilliant if in the flexible buy formula, i was able to give a different formula for different times of the day… do you think that would be possible? so i am able to use the OMIE P value with a different formula for different times of the day… hope that is clear..
thank you so much, Brecht
It looks like this for today for example:
more info: Coopérnico - Previsor de Preços
Any news about this or we are will continue limited to mon-fri + sat-sun?
This part could be more flexible and let users add winter/summer schedules and separate saturday/sunday as this 2 days have diferent schedules.
How can I completely disable DESS?
When I disable DESS in the portal, it is still enabled every time afterwards.
I know that I can still enable and disable it in the dashboard menu, but I would like to remove it completely.
I have the same problem. I’m unable to disable DESS.
I have created the following schedule to restrict charging the battery from the grid:
This morning I noticed that the battery has been charged from the grid in the restricted charge time slot. Details below.
Yesterday evening around 22:30 I increased the SOC to 80% and a bit later the system started loading from the grid:
And it continued after midnight while it was supposed NOT to charge from the grid till 1 AM:
Is there something wrong in my settings ? Or something I overlooked ? Please advise.
I have a DESS feature request called Tariff Peak Shaving.
I noticed that DESS empties the battery to the lowest level set when the dynamic prices are high. The system does not take in account that it could be good to save some energy depending on solar energy tomorrow and peak prices tomorrow.
That is why I tested with , what I call Peakshaving. During the highest prices (yellow and red) the battery is used to compensate local use. Solar energy is always stored in the battery. And is prices are low (green) and there is no solar energy available, energy from the net is used.
In this way the stored solar energy does flatten the highest tariff peaks.
I implented this in our Loxone controller in an effort to use own solar energy more effective over several days. Mayby it saves less money than DESS, but is another way of using own solar energy.
Hi,
i posted in 08’2025 in the german part of the forum: Dynamic ESS gleicht nur die erste Phase aus, nutzt Netz statt wie in der Prognose die Batterie - Other languages / Deutschsprachiger Bereich - Victron Community with no answer.
And i hoped that a update will fix the problem, but the bug is still exists.
My side ID is: 820831
With normal ESS, everything works as expected.
When I activate Dynamic ESS, it only checks that L1 is at 0 W. However, it does not become negative to compensate for the other phases.
When I deactivate Dynamic ESS, it works again immediately.
According to VictronConnect, under Grid → “Feed-in not active” in Multi, the reason is: ESS control prevents feed-in.
Attached is the configuration of the Dynamic ESS. I have deactivated the battery usage restriction, but this does not change the behavior either.
(The screenshots are in the original forum post.)
Hi,
Apparently you have feedin disabled on your system (That’s also the message “ESS control prevents feed-in”)
This alone is not the problem, not allowing feedin is a legit setting.
In 3.64:
Without going into much technical detail: When Feedin is restricted, DESS set a additional inverter-limitation as precaution to avoid undesired feedin.
(This may prevent your single inverter from achieving the required feedin power to compensate L2, L3 as well)
since 3.70
That additional discharge limitation was removed during 3.70 beta as 0 feedin constraints are taken care of by other mechanics - and I believe the absence of that double-safety-check will fix your issue.
3.70 has been officially released 20 Minutes ago. You could upgrade and verify this behaviour.
If it’s still existing, then let us know and we can look into the situation “One RS-inverter on a 3 phase system with enabled DESS” with special regards to this issue.
