Use of predbat_metric_min_improvement_export to moderate export behaviour

[itm1960]

I have a regular situation with my predbat plans where it exports between 6-7pm, but does not leave enough charge remaining in the battery to cover the remainder of the peak rate period (which ends at 23:30 - I'm on Octopus Intelligent Go). The plan below is an example - selling to the grid @28-29p from 6pm to 7pm, only to start buying back @32.89p from 22:00.
I don't understand the detailed logic of predbat's profit calculation, but I can't get my head around any scenario where you plan to sell @29p with the expectation of needing to buy back @32p just 3 hours later.
I have found an entity called predbat_metric_min_improvement_export (currently set to 0.1), which I was thinking might be able to adjust this behaviour, but I can't find any explanation of how it works in the predbat docs. Can anyone tell me whether this would be a feasible way of moderating exports so that they always leave enough battery charge to cover the predicted net house load until the start of the next cheap slot?

[gcoan]

can't find any explanation of how it works in the predbat docs

It is in the documentation, see https://springfall2008.github.io/batpred/customisation/#battery-margins-and-metrics-options

And increasing this will reduce the amount of forced exports you get, but I think there is something more fundamentally wrong with your config or a bug because Predbat shouldn't be exporting at 28p if it then has to import at 33p later on that evening. And it's not that your load has exceeded the prediction, the predbat plan suggests this is the most cost effective.

Something is wrong and it shouldn't be doing this sp please raise it as a proper GitHub issue for investigation. Include the debug.yaml file and log file, we can't diagnose just from a screenshot of the plan

Cheers

[itm1960]

OK will do - thanks