question

I'm digging this up again as I just encountered the same problem trying to create a digital twin of my cerbo-gx. I could probably re-create the ESS-Reason codes based on the underlying rules with other values but that would not be ideal.

Are there any registers available that I can get the ESS-Reason codes from using modbus?

@Leoo @GregoryFierens

Is this what you need?

https://github.com/victronenergy/venus/wiki/dbus#ess-formerly-called-hub-4

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

Or something like this?

https://www.victronenergy.com/media/pg/Energy_Storage_System/en/controlling-depth-of-discharge.html#UUID-898081fc-12c0-210f-e2d4-db3e3c8c28fb

1: SOC is low
2: BatteryLife is active
3: BMS disabled charging
4: BMS disabled discharge
5: Slow Charge in progress (part of BatteryLife, see above)
6: User configured a charge limit of zero.
7: User configured a discharge limit of zero.