‘Agile octopus price below’ advanced setting improvement

Aaron_davies26

would be good if could set a target charge associated with this.

For example, if the agile price is <0 I would like to charge to 100% no matter what the target charge is for that period

admin

Aaron_davies26 That already happens. We ignore target charge if prices are 0 or negative.

admin

Aaron_davies26 Should be fixed now, we're re-evaluating Agile charge instructions every 30 mins if it's part of a contiguous charging block. And if the slot in question is < 0 price, target SOC is set to 100%.

Aaron_davies26

admin that’s not what I saw happen today. The message that was sent at 5:30 was as follows:

2025-06-22 05:29:14 6 %
Charge instruction set to 30% for 05:30 - 15:00 - Agile Octopus

admin

Aaron_davies26 We'll take a look at that.

Right, but a lot of these slots were not negative...definitely not the start charge slot of 5:20 and the next 3 half hours until 7:30 were not negative.

And adjacent charge slots are treated as contiguous block.

If the start slot had been negative, the target SOC would have been 100%.

Open for suggestions as to how the logic could/should be improved.

johalareewi

admin Open for suggestions as to how the logic could/should be improved.

I reckon that Agile slots should be treated individually rather than rounded up into contiguous blocks.
Or at least, only create contiguous blocks within an Agile window.
Things can get unpredictable when selected slots cross an Agile window boundary especially when you also have export schedules going at the same time.

admin

johalareewi I think contiguous blocks could be fine, but a re-evaluation, especially around conditions and tariffs may be needed. After an instruction for a slot at the start of a contiguous block, we can simply push the start on by 30 mins for proper re-eval.

It would mean more server load and API loads, so we'll have to see how that goes and monitor it.

johalareewi

admin

Contiguous blocks and Agile are generally okay but the following situations don't always work as one might expect:-
Manually adding a slot to the start or end of a contiguous block
Manually removing a slot from a contiguous block
Contiguous slots that cross an Agile window boundary

It will be interesting to test drive the beta Agile scheduler with the extra features.

admin

johalareewi Manually adding a slot to the start or end of a contiguous block
Manually removing a slot from a contiguous block

Yeah, these scenarios are especially problematic if the instruction has already been sent. But every 30 min re-eval hopefully addresses some of these.

johalareewi

admin if the slot in question is < 0 price, target SOC is set to 100%.

Is that a hard coded 0.00p price or the advanced setting "Price Below" value?

admin

johalareewi Hard coded, seems to make the most sense to up target SOC if price is negative.