VRM release notes: DESS Adjustable consumption, Split consumption categories, Multisite AI

We have just rolled out some new and exciting VRM features to production.

Multisite AI Agent

On the VRM homepage, we’ve added the Multisite AI agent. This agent helps you find and troubleshoot anything in your installation fleet, like:

  • Sites with a firmware version older than x
  • Sites that reported data in the last hour
  • Sites with an SOC below 15%

This reduces the time needed to get an overview of your fleet.

Split consumption categories

If you have a Victron EVCS or an energy meter with the role of ‘Heatpump’ or ‘EV Charger’, you’ll now see the consumption recorded and forecasted over these different categories. This helps to identify how much of your total consumption is from the heatpump, or whether your solar production is enough to cover EV Consumption.

Improve Dynamic ESS by adjusting the consumption forecast

Luckily, our consumption forecast does not know when you are on a holiday ;). To improve Dynamic ESS on days where you know your consumption differs from the consumption forecast, you can now adjust this forecast yourself. Dynamic ESS will recalculate with your adjusted forecast from the next schedule (every quarter of an hour a new schedule starts).

The original consumption forecast stays visible with a subtle line, so you can use this as a reference or can default back to it.

Microgrid installation groups

You can now specify that an installation group is a microgrid. In the near future, a dedicated microgrid dashboard will provide more insights into your microgrid. For more information on microgrids, please refer to this blogpost: Introducing the microgrid.

Add multiple sites to an installation group at once

On the installation group page, you can now add multiple or all of your installations to the group with one click. An installation group is a powerful tool to share access to a part of your installations with other VRM users.

I hope all of these features make your experience with VRM even better!

In case of questions related to these, please comment below. For other VRM-related questions, please start a new community post :slight_smile:

The two changes “Improve Dynamic ESS by adjusting the consumption forecast” & “Split consumption categories” are amazing, I’d say it’s a game-changer. I’m excited to see how that works out for me - it used to be the weakest point of DESS and basically the only (major) reason for me to disable it sometimes.

THANKS!

Is it also possible to read the splitted consumptions by Mqtt ?

Does split consumption work with every typical energy meter?

(VM-3P75CT, ET112, ET340, EM24, EM540)

Already saw the split forecast, came looking for the info. Great trajectory for improvement (and user input into their system forecasts).

Who can talk to regarding this design and the input (per hour is good but very granular)?

Ae ‘i do not have a heat pump nor a HPpowermeter-role’ so some tweaking to do together:

  • improvement towards the future: show the same forecasted consumption in the evcs section as well (?)

I think many will like the possibility to tweak and improve their own forecasts and it’s a great opportunity for us :blue_heart:

Hi Stefan, maybe the VE MQTT GitHub information can help you find out? GitHub - victronenergy/dbus-flashmq: Plugin for FlashMQ that interfaces between DBUS and MQTT. · GitHub

Or maybe a fast staff member will answer with the ‘topic’ to pick :wink:

Checked via the MQTT explorer but could not find a path.

Reason for the demand is that if I split consumption & power EVC then the value I get isn’t always realistic.

Recalaculating everything gives more realistics instant data but still not really accurate.

This is the calc i make :

let Consumption = Math.round(Grid + System_PowerMeter.AcSolarPower - System_PowerMeter.EvcPower - System_PowerMeter.BatteryPower);

Where Consumption is the normal HousConsumption. Like I said not always correct reason is that the parameters are not published on the same moment in the Dbus.

Update : made a small correction

let Consumption = Math.round(Grid + System_PowerMeter.AcSolarPower - System_PowerMeter.EvcPower - System_PowerMeter.BatteryPower - System_PowerMeter.DcConsumption);

DcConsumption = DcPower - DcBattery

Without EVC charging this gives relative correct value ; but as soon the EV starts charging there a moments consumption becomes negative.

I would guess not as these forecasts don’t ‘live’ on your local Cerbo GX / VenusOS D-Bus but on the VRM DESS cloud servers.
But you can read (and write) them with VRM-API, for instance within Node-RED, and read / convert / proxy them as a (independent) MQQT service if really required.
See also screenshot in this link:

Jan these values are calcullated or far a way in the cloud with a delay or local (like I try). Point is that if you calculate you need all data taken at the same moment or the sum isn’t correct. Reverse calc can give negative consumption due a value that isn’t up to date.

let Consumption = Math.round(Grid + System_PowerMeter.AcSolarPower - System_PowerMeter.EvcPower - System_PowerMeter.BatteryPower - System_PowerMeter.DcConsumption);

This calcullation runs equal like consumption value in the cerbo as long as System_PowerMeter.EvcPower = 0 !

Where System_PowerMeter.EvcPower => N/+/evcharger/40/Ac/Power (mqtt path off the EVC)

Hi, does the splitted consumption also ignore the EV usage to create forecasts? since that is very irregular, or is there an option to ignore it when calculating forecasts

@UpCycleElectric If the data from the meters isn’t from exact the same moment then they are maybe not correct. Let’s keep it very simple : Consumption = Grid + SolarProduction - Battery . When there comes a cloud in front off the sun then Solarproduction goes down but if data in the meter is still the data from 1sec before the cloud then your calcullation isn’t correct. What I want real time correct data … the sums in longer term will be correct. Simpler said all data taken @ the same moment. So not one meter with update every second and the other every 5 seconds.

In het nederlands dat gaat iets vlotter : de update frequentie van de meters moet gewoon gelijk zijn , een veelvoud kan ook maar dan moet je de traagste nemen om in je visualisatie altijd correcte sommen te krijgen. Dit is volgens mij nu niet het geval waardoor de sommen niet altijd kloppen.

Jan no this is not the point. Let’s make it very simpel if you have a powermeter where the measurement of voltage & current isn’t taken synchronic then the Power you calculate is never correct (P=U*I). This what I try to explain to you.

I agree the adjusting of the EVload is very usefull. However the current method of changing on per hour basis is rather time consuming. Please create a better GUI for eg editing all values for the coming two days in a table format? Tnx Hans

Ist der any recommendation?

Fantastic! I’m now finally using DESS too because of these improvements!

I also really like the aesthetic of how this is done. It looks neat and works neat.

Yes, but i mean that DESS Should only count the Base load, and ignore the EV part of it, or at least make it a setting since the EV load is unpredictable, and my installation is too small to support an EV load, so i shutdown the battery once the EV starts charging. So i want DESS to ignore my EV when doing planning.

@Barbara Unfortunately, there’s a bug: the weekly forecast shows heating consumption even though I haven’t configured any heating in the Victron system.
However, it works fine for the daily or two-day forecast. No heating is shown there:

And why does it show EV-charging forecast only the next 2 days, but not for any day afterwards?

Hi! Thank you for mentioning this. Could you maybe share your site’s ID with me so that we can look further into this?

VRM ID deleted (I think Barbara has noted it already)