VRM release notes 25-09-2025

In general, I like the fresh look of the VRM. It’s clear Victron is spending serious R&D effort here to provide a better service (which is free).
So I’m more than willing to take any hiccups that happen during the proces.

Nevertheless, I would like to take the opportunity and to mention a “neverending" story” with VRM, which unfortunately even with this new
visual iteration still doesn’t end: Y-axis scaling/naming:

I understand it can be challenging or next to impossible to have some algorithm to do “the right thing” all the time, but sometimes I really feel that what VRM does with Y axis placing/formatting is about the worst possible solution there could be. See above.

I tried hard to make the Y-axis scaling compatible - which is ok, but as for placing and formatting…

It’s not even keeping the values of the same devices together, no, it has about everything in value formatting there is: no decimal digits, one decimal digit, two decimal digits. Random.

Can’t we get a little bit more control over this behavior? I mean at least in custom widgets?

1 Like

Canbus tank monitor custom names are not working.

Steps to reproduce:

  1. Connect a N2K tank sensor to your N2K network
  2. Connect your N2K network to CerboGX via the canbus port
  3. Set the custom name for the tank (this will fail, not working)
  4. See the result on the VRM main screen

In the screenshot below Fuel [1] and Fuel[100] are N2K tank senders while Center Diesel is a resistive sender. Custom names are working for resistive tank senders but the feature is broken for N2K tank senders.

Hi, when did this work last for you?

Dear all,

Just now the three bugs related to Dynamic ESS settings were fixed:

Fix list:

  • Dynamic ESS settings pages showed the wrong price formulas when verifying them as a user and also wrong in the the summary page.
  • The Dynamic ESS “Price can be negative” setting toggle was showing inverted.
  • An error message about Real-time not being enabled showed when trying to enable or change Dynamic ESS settings. Note that the error message was always showing, but in the mean time the enabling was still working.

All three were introduced with the changes last week. Next we will be checking logs and other data to see if we can inform owners/installers of systems that might have accidentally misconfigured their system as a result of above issues.

Thank you again for all reports and apologies for the trouble..!

Matthijs

1 Like

I think this works for my installations. Which tag are you trying to remove? It could be an automatically assigned tag, which you can indeed not remove.

Hey! The check is non-binding, you can just continue even with €100 battery cycle costs. It’s just a nudge that something misses a comma.

We are aware that it won’t be a correct check in all exchange rates.

The mobile bottom and desktop navigation get a small but impactful design improvement in a week or 2, allowing you to hide the navbar completely if you want to.

8 Likes

Hi all,

An update: per just now, below error has been fixed by an update of the VRM Portal itself. (There is no need to update Venus OS).

Thank you @nielskempen , @vaursechs and others for the reports!

1 Like

@Barbara

Android phone but also occurs on my Amazon fire tablet (which is sort of Android). Not tested on a PC/ laptop.

When in Advanced view, creating a new custom widget, the listing of parameters goes behind the lower menu bar, the scroll bar position is gone and some text is hidden. Attached screenshot shows this.

When this sort of action is being undertaken the menu bar is superfluous and should drop out of sight, or the screen size reduce to avoid overlapping.

2 posts were split to a new topic: Criticism of VRM and Victron

Hi @pwfarnell , good point. I’ll ensure that when something else is focused on (an input field, a part of a graph), the bottom navbar hides itself.

1 Like

EDIT 3: It generally seems like DESS is “working” but the plans are updating very slowly (every 1-3 hours).

EDIT 2: Ok there’s definitely still something wrong. We just changed the min SOC and the plan hasn’t updated to reflect this (~1 hour later).

EDIT 1: weird timing! This just resolved itself. DESS is updating again.

Hi @Barbara, @guystewart - I’m not sure if this is related to the new VRM or not, but for some reason our DESS plan stopped updating yesterday. Nothing on our end changed and we have fixed prices.

I’ve tried toggling the DESS setting on both VRM and the Cerbo, and re-entering the prices (hoping that kicks off something in the back-end, but no luck).

I saw one other post on the forum mentioning this too.

Below you can see DESS as “on”, but the Cerbo showing as “Inactive”. You can also see the scheduled SOC as disjointed (stuck on a value from yesterday). And lastly, the consumption forecast on the DESS section is a bit weird.




Hello developers,

A small cosmetic issue… or not if it’s by design…

In VRM, if you are in the “Alarm logs” or “Event logs” sections and you press on “Remote Console”, firstly the VRM is switching to “Dashboard” and then is showing the console.
If you are in “Advanced” section and you press “Remote Console”, it doesn’t switch to “Dashboard”.

Is there a reason for this?

Not sure if these issues are related or not. All I can say is that I never experienced them before the changes:

  1. I can’t go to Node Red anymore. I have tried multiple times on multiple days on 4 different devices. I always get the same error (see screenshot). It was working before. Everything else within VRM appears to work normally.

  2. When using Firefox on a Win 10 tablet, I kept getting the error that no email entered, although I could see the email. I was forced to use a Win 11 laptop running Chrome. That worked.

I am the only one that in the landscape mode, on Android, it shows so lame… sorry my wording…
Only about 25% of screen height for graphs, screen cluttered unnecessary by the lower bar and upper irrelevant info/menu…
See below…
Really guys?..

1 Like

Cell ID for lowest and highest voltage cell showing “null”:

There are values present in the console:

System is using a set of 8 Pylontech US5000 batteries. Cerbo GX running v3.31~3

Your FW is too old.
I had that in the system of a customer a few days ago too and after the FW update the cell ID is shown in VRM.

You are using an old beta version.

1 Like

Yes, that beta is between versions, previous to the one who tries to also show the cell ids.
I can say that 3.32 is not having this problem, but also doesn’t have the cell ids.

Yes, I know. But that one is otherwise working reliably, so I’m reluctant to upgrade. Maybe sometime the coming winter when there’s more idle time due to lack of solar.

1 Like