Hi
was using the Node since years, now I see that the node I use, does not seam to be correct any more ?
the old “Venus settings / Limit ….” seams not to have the battery voltage any more.
should I change to the “Venus settings / DVCC….” Node now ?
Thx
on my other system it already shows “disconnected”, but still works!
(maybe that is shown, because the value did not change for time)
(after a download it show connected again. ?)
the new Nodes are from “ESS Control”
I use a custom control node as below. Target is com.victronenergy.settings and the measurement /Settings/SystemSetup/MaxChargeVoltage.
There is an equivalent /Settings/SystemSetup/MaxChargeCurrent.
is it a Venus setting or a Ve-Bus setting ?
but I would like to know what has changed, why and when did victron change the nodes?
You are correct that the path changed location. The /Settings/SystemSetup/MaxChargeVoltage path was previously available in the Settings node under the name “Limit managed battery voltage (V DC)”. It was accidentally removed from that node during a refactoring commit (“Shrink services.json file size”) in March 2025.
The path itself was not lost - it moved to the ESS node (victron-input-ess / victron-output-ess), settings category, under the name “DVCC Maximum charge voltage (V)”. So as a workaround in the meantime: open the ESS node, select the “settings” service, and look for “DVCC Maximum charge voltage (V)”.
I’ll be restoring the entry to the Settings node under its original name for the next release.
Regarding the “disconnected” status you see - this is a display state issue unrelated to this, and a redeployment resolves it as you found.
May I offer my opinion? I’m not a fan of finding values scattered across different locations. It makes it unclear and inconsistent to me what the supposedly same value actually means and what its effect is. It would be much better to do a major overhaul and create a clean structure. It’s always difficult and pointless for me to find the node that connects to the value I need; it’s often illogically arranged, and there’s simply a lack of structure and clarity. A significant step towards improving usability and making Node-RED a more enjoyable working experience would be to completely revise all the nodes.
The ESS node houses the DVCC settings, and finding them is a real chore. It would be better (like a menu in Cerbo) to have the DVCC in its own node.
The countless unusable nodes also bother me immensely. Can’t these be hidden?
Libraries (palettes) function… Sometimes the functionality is already missing during installation, outdated, duplicated across different libraries, etc. Then the built-in function doesn’t work, and finding a correct and functioning library becomes impossible. Stronger quality control and a thorough cleanup are needed. Perhaps then more people would be willing to work here again, and the range of functions is crucial for the strength and size of a feature like Node-RED on Cerbo.
I hope I’ve explained my point clearly. If anything is unclear, please let me know.
I know that Node-RED is just a feature and Victron doesn’t directly support it. BUT, it’s one of the cornerstones and most important elements for customizing a system to your needs. Without Node-RED, many things wouldn’t be possible, and that would ultimately only limit Victron. I hope it’s clear what I’m getting at. Node-RED is important and should be treated accordingly by Victron. There’s a lot of untapped potential here that Victron simply isn’t unlocking.
