ESS Max charge and discharge option values in Venus settings in the ESS Control Node removed?

I few months ago I have made a simple node red flow to control the ESS Max charge and ESS Max discharge Power values using the standard ESS Control node.

I have recently updated my CerboGX to the latest version 3.62 and the Node red libraries to version 1.6.33 and I noticed that when I open a ESS Control node there is no possebilty to select the Max Charge or Max Discharge Power measurement anymore.


The Venus settings option list shows only these options:

I noticed that my flow still works! I checked the json and these paths are set:

I am talking about these values

Is this a bug or is there another node to set these values?

Is Settings → DVCC enabled?

These options get disabled when DVCC is enabled.

DVCC is disabled.

I am aware that the Limit charge power is not available (in the GUI v1 or V2) when DVCC is enabled.

As you can see in my latest screenshot the Maximum charge power and maximum inverter power values are visible and changeable using the GUI (V1 and V2) But I do not have the option to change them using the node red node ESS Control Node anymore.

When I double click on one of my ESS Control nodes I see the second screen shot.
The measurement field is empty. As soon as I try to lookup the measurement I see screenshot 3
There is no ESS Max Discharge power or ESS Max Charge power in the list.

When I leave it empty and not save the flow, the flow still works.
I checked the JSON of one of my flows and noticed that the path /Settings/CGwacs/MaxDischargePower and /Settings/CGwacs/MaxChargePower are used and are still valid.

So I think these options are missing in the ESS Control node.
Maybe a bug?

Try use a custom control node instead.

Sure @nickdb I could try that but this thread is a kind of question/bug report to victron.
It could be a bug in the ESS Control node.

It may well be, but in the time it takes to be (possibly) looked at, was just offering a workaround.

Noted, thanks for the report @DutchSolarFreak we’ll look into this

1 Like

@mpvader FYI this has not been fixed yet in 3.70~9

There wasn’t a commitment to fix it in the next beta, these things can take time depending on other priorities.
Keep an eye on the changelog. If a fix is applied it is typically listed.
In the meanwhile consider the workarounds proposed.

@nickdb I know but it was just a fyi.

1 Like

One of the reasons I keep far away of that version. Hate regressions. Seen too many in my life as software developer :joy:

Yah, unfortunately it comes with the territory. What we as a community won’t know, is whether it is a bug or if it was intentionally disabled. With holidays, things also tend to slow down a little this time of year.

1 Like