Alert causes miscalculation of cheap vs expensive import rate

[brettjenkins]

Describe the bug
When alert is enabled and there is a matching alert, it sets the threshold for what is cheap energy incorrectly causing predbat to think the whole day is cheap energy and will charge during expensive periods.

Expected behaviour
When there's an alert coming up, I would expect predbat in the periods directly before the alert to charge to the hold percentage set (if need be) . Then during the alert I would expect it to be in demand mode until the hold level is reached, at which case it would hold the battery and run off grid, just in case of a power outage, until the end of the period when things return to normal.

I wouldn't expect it to alter the threshold import level, and not affect the plan outside of the alert period and the immediate few previous slots if need be. In the provided data this time it looks like it's performing as expected because of the time of day, but the other day you can see it was making odd decisions, not charging at the start of the cheap period for example (unfortunately I didn't take more screenshots of that plan at the time)

Predbat version

8.31.9

Environment details

Sigenergy with 12kw inverter, and two 9kwh batteries
Docker

Screenshots

Log file

predbat.log

Predbat debug yaml file

predbat_debug.yaml.txt

predbat_plan.html

[thewookiewon]

I have a similar behaviour but not using weather alerts, wondering if my issue is more linked to DFS events being detected.

#3188

[brettjenkins]

Now prediction has moved on a bit, here's what I mean about weird behaviour:

So because it thinks both 7p and 26p are cheap rates, it wants to charge using 7p Saturday Morning and then export all of that when the rate goes up to 26p, completely draining the battery, which I don't want.

I don't think this will actually happen because as soon as the alert period is no longer in the prediction period, it'll go back to normal, but if there's a alert period in the next 48 hours it completely messes up the threshold and you get weird behaviour like this until the alert period is no longer in the prediction. This is very noticable when an alert period is just coming into the 48 hours, and then it starts doing this sort of stuff.

Debug files:

predbat_plan.html
predbat(1).log
predbat_debug.yaml.txt

[gcoan]

I don't know if the latest predbat release 8.31.13 fixes it, but in the release notes it says

Fix issue with rates showing as low when they are not

So it might be the fix for this?

[springfall2008]

Yes, that's the one - please re-test

[brettjenkins]

Yes, that's the one - please re-test

I will do, need to wait for another weather alert :) thanks though!