Can I automatically prioritise export over charging?

[rogerlittin]

I have 11kWp of solar split over two arrays (NE & SW) with a 8kW Sigenergy inverter and 27 kWh battery storage. I also have a 3.6kWh export limit. My import tariff is IOG, and my export tariff is Outgoing Octopus.

Because of the low export limit, I would like to automate the following.

• Charge the battery overnight if necessary and then force export to allow room for excess solar.
• Prioritise solar export over charging while ensuring that the remaining battery will be sufficient to get to the next off-peak rate.
• Force export excess stored energy before the next off-peak period.

The first and last point seem to occur with the default settings, but I can't seem to see how to prioritise export over charging without doing it manually. Predbat will either prioritise charging, or it will set Freeze Export, which does export the solar but clips the excess instead of sending it to the battery.

[gcoan]

Predbat should do all of these things for you, but on the second, its important to note that predbat aims to minimise your electricity bill (import - export), so will tend to charge the battery if it predicts that you will need it to meet house load.

So first thing I would look at is your house load, whether that is correctly being predicted in the plan.

I'd also look at battery and inverter losses to check they are realistic and roughly right.

I assume you have configured your apps.yaml with your inverter limit and export limit?

will set Freeze Export, which does export the solar but clips the excess instead of sending it to the battery.

Freeze Export does not send anything to the battery as per the status description https://springfall2008.github.io/batpred/what-does-predbat-do/#predbat-status

Freeze export is used when predbat thinks your battery has sufficient charge, and any excess solar can be exported

[rogerlittin]

I'm sure it should do what I want. It's just that I can't figure out how to set it to automatically export instead of charging. House loads are being predicted correctly, and the limits are set correctly in apps.yaml. I can artificially lower the export limit which does cause the plan to switch to forced export more, but then it's calculations are wrong for the rest of the day because the actual export will be higher than it thinks. I can also adjust the predbat_metric_battery_cycle setting to trigger the plan to use Freeze Export, but I can't find any settings that does Force Export or Freeze Export without using invalid values.