Override SOC Target when meeting Agile Price Threshold

burlebob

Hi, loving the app and as a new solar install I was relieved to find something that simplifies Growatt control!

When the Agile minimum price threshold is triggered outside of any charge window I note that the SOC defaults to 100%, but if the slot falls within a charge window the configured SOC target is used.

Is it possible to include an option (maybe in the charge window configuration) to override the SOC target and maximise charging from cheap slots?

burlebob

Hi,

Thought it would be useful to give a real world example of what I’m requesting here.

I have my minimum price threshold set to 5p, I’d expect (and I’m sure I’ve seen it before though it hasn’t happened much recently!) that any slots lower than 5p would be automatically scheduled and the battery charged from grid up to 100% which is what I’d want with cheap electricity so my battery fills quicker and I export more though the day at 15p.

However when these slots fall within an already configured agile window, the slot configured SOC is taken into account rather than 100%.

For example yesterday morning my threshold was met, however checking the activity log shows that WW has skipped due to SOC because it has scheduled that slot against my night time agile window:

2024-06-05 04:29:10 52 %
Battery is at 52%, skipping Agile Octopus charge 04:30 - 05:00

Is there another way of achieving this that I’m missing (apart from manually increasing the window’s SOC values whenever I see sub-5p slots)? What do other users do?

Thanks,

Ian

important-truth

admin

burlebob 2024-06-05 04:29:10 52 %
Battery is at 52%, skipping Agile Octopus charge 04:30 - 05:00

I see - and was this a slot that met your under 5p threshold?

kerregan

burlebob I don’t actually see the point of the minimum price threshold. To take your example, why would you want to charge at 5p if the next slot(s) were 2p?

It’s more logical to charge if the price is rising and not charge if the price is falling.

burlebob

Hi, apologies for the prolonged silence, I had started to question myself and whether me twiddling was in some way affecting what I was seeing. This past weekend Agile pricing has provided the ideal conditions for me to monitor activity without twiddling and confirm that I'm not going mad (at least I don't think I am!)..

My settings are as follows:
Agile Octopus Import Threshold: 0:00p
I have the following charge windows configured:

On Friday morning multiple Agile slots were below the 0 pence threshold:

My wish would be that the battery would be charged to 100% overnight, making the most of the free electricity on offer. However the charge instruction was instead only set to 30% (my charge window target):

Later that morning when threshold conditions were again met, the charge instruction was this time set correctly at 100%, presumably because the start time falls outside of my configured charge windows:

The following day slots were again below the 0 pence threshold, this time around lunchtime:

This time however because the slot time coincided with my configured charge windows, the instruction was again set to the charge window SOC target (75% in this instance):

As the Agile Price Threshold feature does charge to 100% by default for automatically selected slots, I think it would be beneficial to be able to do this for slots that fall within configured charge windows as well.

Thanks,
Ian

important-truth

admin

burlebob Yep, thanks for your detailed illustration. I think at a minimum, if an existing slot's price is 0 or below, and falls within an Agile charge window it makes sense to ignore the charge window's SOC target and use 100% instead.

We'll get a fix out.

Should be addressed in Release 708. Thanks again!

burlebob

admin that’s great, thanks for looking into this 🙂