Why is the "Force" SoC always set to 100%?

[mprowe]

Sorry if this is a dumb question, but...
There has been an unusual amount of solar available just recently! Day after day, my battery is fully charged to 100% by 10:00 in the morning.
As I write this (19:00hrs) the battery is is still 100% and been exporting all day. Sounds good? But...
With the forecast tomorrow to be excellent, why is PredBat suggesting that I should charge (and hold) my battery to 100%.
I would think that a 50% charge will provide enough battery to run the house until the solar recharge is compete at about 10:00.

I did have the PredBat mode set to "Charge & Discharge" but have now switched to "Charge Only" to see if I can detect any differences. Which I can't!!!
Any suggestions will be most welcome.

Regards, Martin

[gcoan]

Have you got freeze charge turned on as an option in Predbat?

I'm on Cosy and my import rate is very similar and predbat plans to Freeze charge every night in the cheap periods for me so I run off grid as its slightly cheaper than charging the battery

The other thing to look at is make sure the plan length is long enough to include tomorrow's solar and house load

[mprowe]

Have you got freeze charge turned on as an option in Predbat?

Hmm.... not sure? If I look in apps.yaml, I can not find ANY "freeze" strings?

mprowe@Gzunder:~/Downloads> grep freeze apps.yaml
mprowe@Gzunder:~/Downloads>

However, in the web UI, I see this:

Is there another config file I should be checking?

On your second point:

The other thing to look at is make sure the plan length is long enough to include tomorrow's solar and house load

Can you tell me how to find an answer to this question? Again, looking in app.yaml, I see only:

mprowe@Gzunder:~/Downloads> grep plan apps.yaml
  # Number of threads to use in plan calculation
  # car_charging_planned is set to a sensor which when positive indicates the car will charged in the upcoming low rate slots
  # The list of possible values is in car_charging_planned_response
  #car_charging_planned:
  #car_charging_planned_response:
  # In some cases car planning is difficult (e.g. Ohme with Intelligent doesn't report slots)
  # The car charging now can be set to a sensor to indicate the car is charging and to plan
  # To make planned car charging more accurate, either using car_charging_planned or the Octopus Energy plugin,
  # When enabled it overrides the 'car_charging_planned' feature and predict the car charging based on the intelligent plan (unless octopus intelligent charging is False)
  # Set this to False if you use Octopus Intelligent slot for car planning but when on another tariff e.g. Agile
  # The standing charge only impacts the cost graphs and doesn't change the way Predbat plans
  # Watch list, a list of sensors to watch for changes and then update the plan if they change
  # This is useful for things like the Octopus Intelligent Slot sensor so that the plan update as soon as you plugin in
  #  - '+[car_charging_planned]'
mprowe@Gzunder:~/Downloads> 

... only rem'ed out comments. While in the web UI, there is this:

... is that the setting you are referring to? If so, can you suggest a time? 48hrs maybe?

[gcoan]

switch.predbat_set_charge_freeze is correct, so charge freeze is enabled

plan length is input_number.predbat_forecast_plan_hours

do look at the documentation if you are unsure what config does what https://springfall2008.github.io/batpred/apps-yaml/ and https://springfall2008.github.io/batpred/customisation/ cover most of the config settings