Adds additional BMS entities for H1 G2 and KH inverters on latest firmware

[FozzieUK]

Adds additional BMS entities for H1 G2 and KH inverters running with latest firmware

On H1 G2 inverter this PR will add these entities-

bms_cell_temp_high
bms_cell_temp_low
bms_cell_mv_high
bms_cell_mv_low
batvolt
bat_current
inverter_fault_code

Note for the G2 this update is sensitive to firmware version:

On the H1 G2, if you have Manager: 1.37, Master: 1.22 it will not support all the BMS registers - either upgrade to the latest firmware or in the integration configure the settings and enter the manager version of 1.44
also note Manager firmware 1.44 has incorrect scale on bms_cell_mV, low/high (this is a Fox bug, upgrade to Manager 1.48 to fix this)

see #712

On KH inverter this PR will add these missing BMS entities-

bms_cell_temp_high
bms_cell_temp_low
bms_cell_mv_high
bms_cell_mv_low
bms_kwh_remaining

see #740 (comment)

[canton7]

Thanks!

I've finally got around to putting in support for different manager versions (#739), so we can add these and not break everyone.

That will require a little bit of reword of the PR though: have two Inv members for the two H1_G2 version ranges (and maybe a H1_G2_ALL for convience), and update entity_descriptions.py.

[FozzieUK]

ok thanks!, i'll update my branch with all the latest changes, have a quick read through to digest the version stuff and go from there

[FozzieUK]

@canton7 i've made the following changes -

2 new Inv members H1_G2_PRE144 and H1_G2_144 - I have left the original H1_G2 name but made it the equivalent of 'SET' (I kept the original name as it is used throughout and 95% of the entities are in it)

If config version is entered for 1,44 it will select H1_G2_PRE144 otherwise H1_G2_144

I also extended to the KH and added in BMS cell volts, temps and kwh_remaining as per #740 (comment)

EDIT: Can we pre-release as a beta and find a few candidate testers before we let this go wild.

[WyndStryke]

EDIT: Can we pre-release as a beta and find a few candidate testers before we let this go wild.

I'll be happy to represent the post-1.33 KH contingent :-)

[canton7]

@FozzieUK Perfect, thanks!

I have left the original H1_G2 name but made it the equivalent of 'SET' (I kept the original name as it is used throughout and 95% of the entities are in it)

I might be tempted to rename it anyway for consistency -- then someone reading entity_descriptions can see quickly that it refers to more than one inverter.

If config version is entered for 1,44 it will select H1_G2_PRE144 otherwise H1_G2_144

👍 . I'm tempted to rename the Inv members to better match how Version is used, but I'll do that in one go later.

EDIT: Can we pre-release as a beta and find a few candidate testers before we let this go wild.

Yep I think that makes sense. I should have some time on Sunday.

[FozzieUK]

I might be tempted to rename it anyway for consistency -- then someone reading entity_descriptions can see quickly that it refers to more than one inverter.

No problem, it was bothering me too - i've updated it so now H1_G2 is H1_G2_SET

If config version is entered for 1,44 it will select H1_G2_PRE144 otherwise H1_G2_144

I'm tempted to rename the Inv members to better match how Version is used, but I'll do that in one go later.

Perfect, thanks 👍