This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.
Hello,
I would like to readout the ESS states #1 and #2 via dbus commands in my bash script, but I can't find it in the "CCGX-Modbus-TCP-register-list-2.51.xls" (or maybe I look over it).
If #1 is active, my periodical running script shall performe some commands.
Any idea how the exact syntax for a dbus command would be? e.g.
Variable=$(dbus -y com.victronenergy.system ??????????????? GetValue)
Best regards
Rainer
I had just come across the dBus paths for the ESS "reason codes".
They are in com.victronenergy.system
/SystemState/LowSoc
/SystemState/BatteryLife
/SystemState/ChargeDisabled
/SystemState/DischargeDisabled
/SystemState/SlowCharge
/SystemState/UserChargeLimited
/SystemState/UserDischargeLimited
for reason codes #1 - #7, respectively
Hi,
the Multis consume quiet a lot of standby power (11 W the MP3000, 18 W the MP5000).
Thus, I want to write an node-red-flow for automatically shutting down the Multis in case of low-state.
(In my situation shutdown the Multis is possible because my Multis only serve ESS, ACOUTs aren't used.)
The problem I'm facing...
When Multis are on, /SystemState/LowSoc is correctly signalig whether or not the batteries still have enough power to serve ESS. So in case on lowsoc = 1, I'm shutting down the Multis. But then, lowsoc always switches to 0.
So I have to calculate my own mylowsoc which is represented by this expression:
soc <= max(soclimit, minimumsoc)
Is there really no value within dbus representing whether the battery can still serve ESS or not?
Regards
Alex
