FR: Support manual target SoC override in predbat table card`

[gcoan]

Another new Predbat release, another new Predbat feature https://github.com/springfall2008/batpred/releases/tag/v8.29.7

Could this be incorporated in the table card override please?

[gcoan]

I also just noticed in the release notes it says:

The weather alert icon and manual SOC icon will now show in the SOC column of the HTML plan if active.

So this may well have an impact on the current plan render

[gcoan]

Bit more info, if you set a SoC override it changes the SoC colour to pink whilst calculating the new plan

And then when predbat has recalculated it puts a pen icon:

Curiously says 85% even though I set an override for 100% at this time 🤷

[pacemaker82]

yeah saw this last night. If the target is set in an entity then I can show that instead of whatever is in the column. Seems odd he chose 85% when you override it. Would be nice if the override symbols were consistent too. I think he uses a "ⅎ" when you force override the slots elsewhere.

[pacemaker82]

Just a note, his release notes aren't quite accurate.

Added a new feature to allow the user to specify a target charge SOC (for charging only), either via selector.predbat_manual_soc selector or from the WebUI by clicking on the SOC cell (as below).

There are in fact two entities to set:

[gcoan]

yeah saw this last night. If the target is set in an entity then I can show that instead of whatever is in the column. Seems odd he chose 85% when you override it. Would be nice if the override symbols were consistent too. I think he uses a "ⅎ" when you force override the slots elsewhere.

If you can code it up to recognise either the pen or F symbol, I might change the Predbat code to an F to be consistent as you say.

I tried the feature last night, and it clashes with low power charge being set springfall2008/batpred#3052 so that's being fixed this morning

Just a note, his release notes aren't quite accurate.

Added a new feature to allow the user to specify a target charge SOC (for charging only), either via selector.predbat_manual_soc selector or from the WebUI by clicking on the SOC cell (as below).
There are in fact two entities to set:

I think it may be the same as the load override, the input number gives the default override figure which is then copied into the select via the UI.

When I get the fix I will test again

[pacemaker82]

In the release notes:

specify a target charge SOC (for charging only)

Just so I am clear, by setting these two entities for SoC, the force charge ALSO isn't required right - even though this is essentially what changing the SoC could do for a given slot. Like what if I change the 20:30 slot to SoC target of 100%, does it now force charge to goto that new target?

Should/can this only be set where a charge slot is already set?

[pacemaker82]

Ugggh, this change is horrible - I am not supporting it yet until its better. I just set 100% target SoC on my 20:30 slot, and it changed my entire plan from now until 20:30 to charge to 100% and maintain.

[gcoan]

Just so I am clear, by setting these two entities for SoC, the force charge ALSO isn't required right - even though this is essentially what changing the SoC could do for a given slot. Like what if I change the 20:30 slot to SoC target of 100%, does it now force charge to goto that new target?

Should/can this only be set where a charge slot is already set?

I need to play with the new feature more when the bug fix for conflict with low power charge is released.

Current Predbat will work out target SoC's itself to minimise import and electricity costs, e.g. charge on cheap rate, release the battery on expensive rate.
This new code was developed as an extension of the Weather alert code whereby you can define a SoC to be at for a specific time point so I'm expecting it to adjust the plan to add charging and freeze charging so that it achieves the specified target, and no, you don't need to add force charges in yourself.

Adding force charges is a bit of a blunt tool because whilst you can set predbat to charge mode you can't specify what SoC you want predbat to achieve by the end of the charge slot. This new feature adds that capability. So you want to add a bit more SoC for a big wash tomorrow, just specify a target SoC override

[pacemaker82]

Just for clarity, when setting in the add_on plan functionality, this is what is set in the entities. I think the input sensor is just for trefor to remember the last user input value, as he stores the value for the slot in the other entity.

[gcoan]

yes you're right, the input number is the default value for the target soc, and if you change the target soc for a specific time then that changed target is written to the input number

[pacemaker82]

i'll add support for it in next release

[pacemaker82]

https://github.com/pacemaker82/PredBat-Table-Card/releases/tag/v1.9.9.5