Tiered storm reserve targets based on weather warning severity

[liambresnahan]

I’m currently using Predbat’s MeteoAlarm integration to retain battery SoC during weather warnings. The existing alerts.keep setting applies a single reserve percentage to all matching warnings.

Would it make sense to support tiered reserve targets based on warning severity? For example:

• Yellow warning: 60% SoC
• Amber warning: 80% SoC
• Red warning: 100% SoC

Ideally, Predbat would also proactively charge to the appropriate target ahead of the warning, using the cheapest available import periods where possible, rather than simply retaining the current SoC once the warning begins.

I’d prefer to keep this within Predbat’s existing optimisation logic rather than introduce external Home Assistant automations that might conflict with it.

Questions for maintainers:

1. Is tiered alert handling already possible with the current configuration?
2. Does the existing keep mechanism proactively plan charging ahead of an alert?
3. If not, would severity-based reserve targets and anticipatory charging be reasonable enhancements?

[thesilentmiaow]

I was thinking the same thing. i.e. having a tiered keep SoC based on warning severity. Alternatively make the keep setting configurable to a home assistant input number helper rather than just a static number. Then I could write an automation to configure that input number based on the alert severity. But it would be neater if predbat did that internally rather than creating dependencies on HA.

I used the WeatherAlert for the first time with storm Boleo. It does charge up in advance of the alert which is great. I initially used 100% but that lead to high import charges which seemed unnecessary for a moderate storm. So I dropped it to 70% and it managed it and avoided the peak import slots. But if it was a red severity storm then I'd probably ramp it up to 100%.