No changes with negative grid feed in

So we need to have this feature back activated. Where do i have to complain or report the issue? Is there a chance to get it in the next Update?

I have three MP 2 3000… for two households, two utility-scale generators, a heat pump, and approximately 20-25,000 kWh of consumption. My system has been running solely on DESS since October 2024. I haven’t experienced any major losses through grid feed-in. Yesterday, March 17th, with a significant PV surplus, it was an incredible 0.3 kWh, which, according to my calculations, amounts to an incredible loss of €0.10. I can’t understand your excitement at all.

Good for you. My System is using around 2kWh/d which translates to ~1€/d. If you sum it up for the whole year it is a noticeable amount of money wasted, since there is no technical need. I do not like to pay that just because some Software ignores a negative value.

50 cents per kWh? Respect. All year round? Every day? Or isn’t it the case that when demand is under-supplied, the exact opposite happens?

Volatile prices. The 2kWh are consumed when there is no support from PV-System.


On 04.03 we had the big oven running, else there was enough PV available.

I just don’t want to pay money for technically unneccessary stuff. When turning off dess i get zero grid consumption. But then I’m screwed if there is not enough PV…

So now I have a few more minutes than this morning. One more thing about maintaining the grid set point. If you take the time to observe the system over a longer period of time, you’ll notice that DESS varies the grid set point all by itself. During periods of PV surplus, the system tends to feed in a few watts, and during periods of PV production slack, it tends to draw a few watts. I’ve been observing this for months now. Perhaps it would be more sensible to observe this behavior over a longer period of time before asking for a place in the poorhouse.

The last sentence is absolutely unnecessary and you can keep it to yourself! Be polite please!

Apart from that, I agree with your observation.
I assume by PV surplus you mean the surplus that is stored in the battery.
But if people have a large battery, why should the DESS draw a little power from the grid at night instead of continuing to feed in lightly?
Increasing the grid setpoint overnight only makes sense if you have no possibility of recharging the next day or if the DESS has to assume that the battery would not be sufficient.

I’ve also observed that behaviour since November but now with some sunshine i can number it. And it is way too much if you consider that there is a charged battery and probably grid prices of around 50ct. Most nights we use only half the capacity, why would i like to purchase expensive grid energy when the daylight is able to fully recharge and balance the next day?
I don’t understand what watching that behaviour would change?
It just doesn’t make sense.

We just need to be able to set an Offset to the grid feed in value when dess is active and it should be fixed.

Is victron staff reading here or do i need to write them?

Short Update: i paid around 21€ last month for not beeing able to adjust the value.





The big oven burned two times, which is why battery went out. It needs around 120kWh/burn.

Victron: Please update and let me set an Offset

Ok, i turned dess off :-1:

@Victron Please fix till the sun gets weaker.

@dognose

Do you know if the ESS gridsetpoint settings are working for in DESS now or if it is planed to import this value?

Have you tried beta Venus OS? It has a lot of improvements for DESS. As far as I can tell from the source code, DESS is using a setpoint of 0 in some states and otherwise it’s letting ESS work on its own which will use setpoint configured in GX device.

The ESS gridsetpoint is always used in DESS.

Unless there is a buy / sell schedule, where it ofc. needs to be overwritten to achieve the desired schedule.

So than, we have/had a bug.
As shown in the first thread, a negative GSP in ESS has no effect in DESS.

I’ve send you a pn, If you could give me your site id and the time when you made this -400 watt video, I could review that.

Ofc, if DESS is currently on a schedule to discharge with XY watt, then the grid setpoint has no effect, (dis-)charge rate then dominates, grid will just follow the result of that.

Yeah, but in Green Mode the discharge power should be a dynamic caculated value.

If the battery has enough energy to cover the expected consumption with GSP it should use the GSP for the calculation.

If the battery has not enough energy to cover the Night, DESS should use a self optimized GSP

I have a 46kWh battery, you can stay very long with -100W GSP.

I took a closer look once more (it’s been a while since I did last time) and here are some questionable potions. The question is whether Override really means override here. If yes, then then we have found the culprit. But if it’s more like an offset instead, then the code is correct.

=> Setpoint override is set being to zero here when no feed-in is allowed. Shouldn’t the override not be set to None instead? like here dbus-systemcalc-py/delegates/dynamicess.py at master · victronenergy/dbus-systemcalc-py · GitHub

And for the MultiRS there are some code lines where the AcSetpoint is explicitly being set to zero:

Shout out to @dognose

He fixed it.

It will be part of the next beta

It depends. This line is in idle() - and idling the battery means to keep the discharge as low as possible, so we used 0 here. Idling typically happens when grid is cheap(er) than using battery power, so a negative setpoint is ignored on purpose so to say.

It somehow doesn’t make sence to say “Idle to preserve energy for later, but sustain a user-configured setpoint of -X00 Watts”. The system would otherwise spend energy on this and eventually has to buy back from grid at expensive times later.

And when idling, loads will be covered from grid, so you’ll be far away from a 0 setpoint anyway.

But we addressed the negative setpoint not beeing kept during “self-consume” mode. It was caused by a bat2grid restriction which only allows to discharge into loads, hence also ignoring a negative setpoint [during night]. That will be fixed to allow a discharge covering loads + negative setpoint.