in beta VRM and beta mobile app I found already maybe two weeks ago new button - EDIT Forecast.
I tried to find info about this feature here, but I cannot find any annoucement or discussion about that. I tried to use it already several time, but seems that there is no impact on the DESS energy planning.
Is it just “not yet” or do I miss the correct way hot to use it?
I just noticed it too. It doesn’t adjust the DESS plan for me either. I’m guessing that’s coming soon.
@Barbara I know this was something you mentioned on the roadmap so it’s exciting to see.
Hi @A-P , Yes, this Wednesday we expect DESS to consider the adjusted forecasts on both BETA and Production.
Hi @Barbara . Thank for annoucement. Looking forward 
I would like to implement also energy meter for boiler to have better energy management. Should I use energy meter assign as “heat pump”? Which EM should be used - only Victron (eg. VM-3P75CT) or can some Shelly relay “PM” vesion or Shelly EM can be used also?
I am not yet experienced with Shelly…
Are somewhere information about “load type” documented? Link or some post in this forum would help me
Hi! The Victron Energy meters support the role ‘heat pump’, I don’t know if they shelly’s do this too.
Adding a boiler and labeling it as heatpump works: In VRM, it will show as ‘heating’ which covers your use case.
The adjusted forecast is live btw, so have fun! 
I’m excited to try this out!
My last DESS wish is if only we could tell the scheduler about DC loads too Our Victron system is quite large and has a meaningful idle power consumption, which “drags” down the SOC over time. DESS of course keeps adjusting its plan based on this, but I’m guessing the planning would be more optimized if it was aware of these other baseline loads.
But I know dognose is aware of this as well so I’m hopeful one day this will make it in!
I really like how you did the UX for the forecast adjustments.
How about an ‘edit SoC target’ as well to solve the longstanding DESS Trade sell bias issue at last. (Even if only capable of setting a single SoC target between now and the end of the known day-ahead prices forecast period, or just the for the last hour of that period, as long as it is independent of MinimumSoC)
Quick question: in the hypothetical situation that I would set a single large 'future consumption (or sell) value at the very last hour of that known price forecast period, will that influence the regular consumption forecast algorithm even if not actually realized come that hour?
Let’s test. Before reschedule (adding 25kWh EV charge at the last hour)
And here the reschedule result:
To me this is great news because it provides a deterministic path to finally solve the ‘sell to minimumSoC’ bias problem. Still a hack but a hell of a lot easier than my current hybrid Node-RED / VRM DESS hack.
Apparently the ‘edit forecast’ function does not care about that being AC or DC as long as you set the AC (grid) DESS power limits to your actual physical limits and increase the DC (battery) limits high enough to allow whatever DC draw/charge you want to facilitate (real or imagined)
PS, for the sharp eyes out there: that cluster of 8kW-ish consumption represents a secondary HF boost charger that I compensate (out of the AC consumption widget) by means of a virtual PV inverter with negative power calculated from measured (smartshunt) DC charge power, it shows up in the graphs but does not count towards the actual AC consumption forecasts.
Great feature! Thanks!
I can see the changes made in VRM GUI reflected in the return object of VRM-API installations stats as new ‘…_adj’ (adjusted) objects, see below.
Question: what VRM-API call / path can be used to add/change/delete these forecast adjustments from within Node-RED?
EDIT: apparently a new option / dropdown has been added to VRM-API node: v0.4.1 (dropdown added, beta) in venusOS large beta v3.80~14 :
Configure a VRM API node with:
Also I see a VRM-API node update to production version: v0.4.3 released yesterday 22 Apr 2026. Any news when this gets released in a none beta VenusOS v3.7x or a new beta v3.80~yy ?
Or how to (safely) update the VRM-API node manually in Node-RED while staying on the release v.3.7x version.
Hello,
small feedback after one week usage:
very nice feature that helps to adjust planned changes in consumptio n
UX also very easy to handle and nice - but only for PC and small changes (one-two slots per da y)
Not work well at mobile devices - the table is often disappearing from visible area or disappearing partly, tricky to hit the right column (IOS), unfortunately most of users are using phones to control VRM
missing other “table version” to have possibility to copy paste e.g. from previous day, week…, or something like "draw a consumption line to c hart
Now the most important:
- as I focused now in the consumption forecast - I can see how far away is the model from the reality. I know that it is tricky, but clear is that big consumptions (EVs and heat pumps, boilers) has to be excluded from standard forecast and handled separa tely…
In my household the standard 20kwh can be forecasted the rest 0kwh up to 100kwh daily is controlled and cannot be forecast based on the “past” but only based on weather, energy price, energy excess
Specially now after the weekend with negative purchase prices - the forecast is completely broken - for me by ~3,0x. The two days are influencing too much next day including calm ni gh time.
Please put max. priority to the changes towards EVs charging and heat pump/boiler control by DESS.
