System details: three‑phase setup with 3 × MultiPlus‑II 5 kW inverters/chargers.
In Node‑RED I used to write to Venus Settings → ESS → BatteryLife State. I would inject either 10 or 9 (“Keep batteries charged”) to force the battery to charge or to switch back to normal operation.
Last week I updated my Cerbo GX, and today I noticed that this Node‑RED flow no longer works. I cant select ESS BatteryLife state.
Hello, could someone please check within a Cerbo GX version greater than 3.70~60 in Node-RED whether the previously missing configuration point in ESS Control (output of NodeRed), ‘ESS State’, has since new version has been restored?
Node-RED v4.1.1 is running with @victronenergy/node-red-contrib-victron (1.6.55)> victron-input-ess, at the latest available version.
I would prefer not to upgrade the Cerbo firmware, only to discover the option remains absent and then be compelled to roll back.
Could it be that the issue stems from the Node-RED @victronenergy/node-red-contrib-victron component being absent, rather than from the Cerbo firmware?
Thx EDSTOBI
Hi, I’m running venus OS 3.70~88 and still do not have the “ESS state” in the ESS output node.
But I found another way to edit this setting from node red, you have to directly act on the dbus: dbus · victronenergy/venus Wiki · GitHub
I use the “custom control“ node: for custom I select “com.victronenergy.settings“ and measurement I select “/Settings/CGwacs/BatteryLife/State“
ESS state was a read-only value iirc, hence why it is in the output node only.
The ess control node only lists the mode which is the writeable register for changing modes.
Hi Nick, I’m not expert but:
From what I understood from the wiki ESS state has 12 values that can be read (1 to 12) and 3 that can be written (1, 9 and 10).
And as Marc said, it was available before.
0: No longer used.
Optimized mode with BatteryLife:
1: Value set by the GUI when BatteryLife is enabled. Hub4Control uses it to find the right BatteryLife state (values 2-7) based on system state
2: Self consumption
3: Self consumption, SoC exceeds 85%
4: Self consumption, SoC at 100%
5: SoC below BatteryLife dynamic SoC limit
6: SoC has been below SoC limit for more than 24 hours. Charging with battery with 5amps
7: Multi/Quattro is in sustain
8: Recharge, SOC dropped 5% or more below MinSOC.
Keep batteries charged mode:
9: 'Keep batteries charged' mode enabled
Optimized mode without BatteryLife:
10: Self consumption, SoC at or above minimum SoC
11: Self consumption, SoC is below minimum SoC
12: Recharge, SOC dropped 5% or more below minimum SoC
For changing the ESS state:
1: Change the ESS mode to "Optimized (with BatteryLife)"
9: Change the ESS mode to "Keep Batteries Charged"
10: Change the ESS mode to "Optimized (without BatteryLife)"
IT IS writeable (it works on my system). And no the mode is another setting, here we’re talking about the batterylife setting, that was available in previous versions of the node-red-contrib-victron.
Those 3 states are effectively Self-consumption with battery life, self-consumption w/o batterylife and keep charged. That is what it does. Same outcome as setting the mode.
Edit. To confirm it should work as originally documented and does require a fix but in the meantime use the mode option.
Issue added on git.
