V3.70 DESS using grid for consumption instead of battery

@Michael5
pls. double check if the Multi RS is certified for your purpose in your country.
In Germany only 1 Multi RS as 1p is certified.
3p is on the way, but has not been completed according some posts and vids from Intersolar.
Multi RS cannot be paralled, yet.

DESS was supposed to use battery this hour, but actually uses grid.

installation 442946


Thanks, For NL, we are all set.

Any news on this?

Btw, The circumstances are not rare, I see it on all the 3 installations that I have access to.

Yes, we have made changes that are currently beeing tested.

Can’t give you an exact estimate, but probably not making it into the official 3.60 release. (That is to close to really make sure the changes have no undesired side-effects in other situations)

3 Likes

Okay, can the dess team also investigate this issue:

If there is anything I can test let me know!

2 Likes

Hey, I also do have a strange behavior with the forecast, it doesnt get it right…
I always have a load between 150-1000 W in each hour also in the night. The system calculates 0W for tomorrow early morning, therefore it doesn‘t charge up the system properly and its not utilizing the DESS.
Do you think this might also be related to this issue?
BTW: Thanks for your great work!

I manage DESS in this way.
Every 1min check
IF Daily avg. spot price * 2.5 < current spot price AND current spot price < 0.2
AND battery SOC > 40
THEN send MQTT “4” to ESS mode in victron else send “0”

4 - is the rednode mode
0 - is the off mode

This way the system work as intended for me selling when spotprices are favourable and own consumption orherwise and the in off mode two other loopa when to charge battery and stop charging based on spot priced (used during wintertime as PV can manage the energy demand during 7months of the year)

This all in home assistant. System size 4.1kWp/33kWh

Could also be built in red-node on the GX unit

1 Like

Here I have another example of today and tomorrow. Anybody know how i can reset the forecast?

Solar forcast can be reset via VRM portal → Settings → General → Reset solar forecast

Manual reset of the consumption forcast is not possible. Forecast wil adopt by itself.

1 Like

Could it be because it is a one phase system and its not calculating on the installation data basis but on the dynamic ess page?

thanks, i tried this but unfortunately it didnt change the consumption forecast for DESS

That is what is said. It is NOT possible to reset the Consumption forecast.
The Consumption forecast is dynamic and it will learn from your own consumption over time, when measured correctly. It can take up to 28 days.

This topic is not about incorrect consumption data. There is currently no reset possible and you have to wait 28 days. Please use the correct topic:

@dognose Did you see this post?

And can the dess team also implement this feature to prevent grid usage due to minium soc additional to this issue which is about grid consumption when soc is 100% and dess is idle?

This was part of an (earlier) beta, but hasn’t made it into production and further development is on hold. AFAIK it caused Issues that remained unresolved, but can’t tell for sure, it happened before my time.

I’m not in charge to decide which features will be added or dropped, so not much I can do about this.

1 Like

I can’t find it in the current beta.

As long it’s on the radar to be solved in the following months it’s fine by me.

I hope to install another victron dess installation and this fix will then be available.

No it won’t - as said, that has been dropped currently.

Still I think this is an issue, when at night more electricity is actually used there will be grid usage in the morning because minimum soc is reached, which is causing buying electricity instead of using own free/cheap energy.

I will continue using nodered to lower soc at 2AM and increase it and 2PM as a workaround.

Please try to get this issue fixed.

1 Like

What issue are you having, I’ve tried to find it on the thread. I have over 70 installs using DESS and have no issues but just wanted to keep an eye out for the one you are having encase I have missed it?