Cerbo not loading new DESS schedules

Both my installation, and another of a friend no longer seem to retrieve DESS schedules since somewhere yesterday afternoon. The epochs are far in the past by now whereas VRM Portal is looking fine.
Strange enough, the well known no schedule error did not pop-up but behaviour is like regular ESS now ?

I switched to the DESS node-red version which is working fine for me.

Anyone else experiencing this ?

2 Likes

For me (firmware 360~49) dess is on but scheduled battery percentage is at 0%

The dess seems not working and is running in ess mode. All exess solar is going to the battery. On vrm everything looks ok, but it’s not

Hi. I neither see Tibber energy costs in VRM for today, nor does my DESS seem to retrieve any information. (V3.60~49).


Node-Red only overwrites schedules 0 to 3 I believe. If I check the “untouched” DESS mode 1 schedule 4 start epoch it says:
GMT : Friday, 28 March 2025 18:00:00
Your time zone : Friday, 28 March 2025 19:00:00 [GMT+01:00]

Safe to assume we can subtract 4 hours, meaning the service broke yesterday afternoon at 14:00 UTC.

Let’s hope someone from Victron is reading this in the weekend. Again, so far it seems to be the Cerbo not being able to retrieve the schedule. Node-Red DESS version is working fine.

1 Like

I reversed back to 360~48 but no success

I am doubting to reverse to 3.54 but than my mppt is not feeding to grid.

I don’t think the problem is within the venus os firmware. It seems to me it’s a dess problem in vrm

This isn’t a VenusOS problem. I’ve checked a number of systems with varying firmware versions and they all have the same problem.

Perhaps daylight saving isn’t handled correctly. There is also a solar eclipse today. I don’t think that’s related, but who knows.

Today DESS = Dead Energy Storage System :wink:

I’m having the same o problem with scheduling not loading since yesterday

The upside is, my battery 20kwh is already at 87% with this much solar 7725w at the moment in the Netherlands

Same here. DESS charged the battery last night from 02:00. :scream: :angry:
The schedule in VRM looks okay, charging with low prices during daytime.
Venus os 3.54

here the same firmware 3.54

I’m running on 3.54 and the same problem

I thought I’d see if it was an issue with retrieving the pricing data. So I set up the system with static prices. The Dashboard display in VRM is not picking up these prices either in the schedule.

I’m assuming a link between the price data table and the DESS algorithm has been broken.

Hopefully someone in Victron is picking up this thread @Barbara please can you flag with appropriate team?

Same here. The VRM DESS scheduler seemed to have stopped updating about 12 hours ago.

We tried adjusting the fixed tariffs and we can see in the VRM API the buyPriceSchedule updated, but the front end VRM graphs are not showing any changes.

The Cerbo is reporting DESS as inactive. Toggling DESS from disabled to enabled in VRM did not help.

Same here, despite Tibber pricing data being display correctly in VRM!

I’m also running latest beta systemcalc and DESS Reactive Strategy is reported as 99 NO_WINDOW

I have all the same problems in 3.60~49 and 3.54:

  • DESS Status is Inactive with Target SOC 0% in the Remote console.
  • Adjusted fixed tariffs in DESS settings don’t shown in VRM graphs.
  • After battery is fully charged, there is no feed-in PV excess, 2 mppts stopped - looks like feed-in excess limit is set to 0.
  • After any Cerbo reboot, Dynamic ESS settings topic can disappear from Settings menu in VRM

Same here, VenusGX running v3.54, DESS seems to be working according to VRM but Remote Console says Inactive.
It seems no schedules are being pushed by VRM ?
Pulling DESS data with Node Red seems to work though.
Bummer.

Same here, both on v3.60~49 as on v3.54

Same here …3.54

DESS soc target (visible in advanced graph) disappeared around 02:00 and dropped to 0% around 07:00 NL time. VRM dashboard still shows original prediction targets until midnight but none are calculated for tomorrow.

Current prices aren’t being read either. The entire system seems to be down.