Expose battery.status and battery.status2 as bitvector equal to battery.status

[sfudeus]

This will expose battery.status and battery.status2 as native bitvector equally to battery.bat_status to check their use in real-life.

Ideally, we'd already decode the bitvector for prometheus and emit a marker label per bit, but this is not done for the battery.bat_status and still is worthwile.

This MR was triggered via svalouch/python-rctclient#39, suggesting status2 could expose more informations.

[sfudeus]

I'll prepare a docker image based on this branch to allow running this in a real setup and will see over the next weeks if there is some benefit.

[MichaelMMS]

Hi sfudeus,

I also have two battery stacks.
Two stacks are supported on DC8 and DC10 together with the new BMS firmware released this year.
Currently "rctmon_battery_state_of_charge_percent",
"rctmon_battery_voltage" and all the other battery infos are stack B (if you run two battery stacks).

RCT has added a new battery IDs value set. Something like battery (togehter), battery (stack A) and the old data from battery (stack b).

I asked RCT for the new IDs of their API but they did not respond.

[sfudeus]

Hi @MichaelMMS,
the only references regarding 2 battery towers is power_mng.n_batteries_com, power_mng.n_batteries and power_mng.n_batteries_conf, which only tells the number of configured/detected towers (n_batteries is already supported in rctclient).
I cannot find any more specific infos in the App code (version 2.821).

[MichaelMMS]

@sfudeus, I made a very short video to demonstrate the "issue".

https://www.youtube.com/watch?v=BR3wZG1Uhoo

THX