Release 681 - 20 custom schedules, 12 Agile charge windows

admin

Release 681 now allows 20 custom charge/discharge schedules, and support for 12 Agile charge windows and ability to name them.

This allows users to configure seasonal schedules/windows with unique settings configured, rather than reuse and overwrite schedule/window settings every season.

WindyMiller

admin That's great news and something I'll make use of straight away.

Can I suggest you also give an indication on the two pages of what the new limits are as people will not know the limits unless they read this thread or try to add the 21st/13th entry.

johalareewi

Name feature is great but if I name an Agile window that is not active, the WW logic still processes the window when saved and zaps the auto selections from the active window.

Workround was to name all the windows then go back and toggle the active switch on the active windows.

admin

johalareewi Good point, saving a non-active window which' status has not changed should probably not affect repopulation.

admin

admin Thinking out loud here, a default order of Active, Time, Name would probably work. @Capt_Rich

johalareewi Name feature is great but if I name an Agile window that is not active, the WW logic still processes the window when saved and zaps the auto selections from the active window.

Fixed in Release 686.

Capt_Rich

Having the extra schedules will be really useful. Might be a bit of an ask, but would it be possible for us to choose the order of the schedules? Currently they default to time order. I can see there might be some of us who would like to order them differently, such as name order.

admin

Capt_Rich Thinking out loud here, a default order of Active, Time, Name would probably work.

jrc

Thanks WW team.

This looks good but the interaction with the Agile pricing setting could be clearer.

Can the agile pricing setting be incorporated into the same schedules page, so it is possible to set the max number of cheapest slots but only when under a particular cost threshold?

Currently, I can set i) fixed charge slots, ii) cheapest # charge slots or iii) all slots under a given cost based on the advanced agile price setting. Ideally, I'd like to conbine ii) and iii) to preselect eg. max 4 cheapest agile slots under 12p.

admin

jrc max 4 cheapest agile slots under 12p.

The problem with an approach like this is that for most people, they want to charge based on combination of current SOC and a number of cheap slots.

What if there are no 4 cheapest agile slots under 12p? Would WW not charge and you end up out of battery and pulling from grid anyway? What if the cheapest 4 slots were 13p?

The issue here is that for a hands-off approach, a dynamic setting of 'cheapest' makes more sense than specific threshold prices in pence.

jrc

admin

Thanks for your reply. In short, yes I only want to charge if the price is below my export tariff rate, since then its cheaper to grid charge and export more the next day. Otherwise I don't need a charge - my battery will still last all night.

If I leave the agile price set to 12p then WW sets all slots at any time for charging, with no regard for the cheapest slot. Can you add options to limit agile slots under a cap, prioritized by price?

Edit: Looking further ahead, it'd be great to be able to auto-set an export schedule to drain the battery if the upcoming agile price is below a different cost (e.g. 5p).

admin

jrc If I leave the agile price set to 12p then WW sets all slots at any time for charging, with no regard for the cheapest slot.

Yes, that is how the threshold mechanism (under Advanced) is supposed to work for Agile, it's mainly there to allow people to take advantage of plunge/negative pricing by setting the price to 0.

jrc Can you add options to limit agile slots under a cap, prioritized by price?

We'll see if we can add some condition as part of the Agile charge window, cheapest x slots, and a toggle 'Only if below y pence', with Y value to be specified by user. As long as the understanding is that you may end up with no charge slots in that window at all.

By default this additional conditional toggle would be off.

jrc

admin

This sounds great, thank you.

johalareewi

admin We'll see if we can add some condition as part of the Agile charge window, cheapest x slots, and a toggle 'Only if below y pence', with Y value to be specified by user.

That would be usefull for my overnight window. I am now on octopus fixed outgoing so a "don't charge if over 15p" kind of feature would be of interest.

miffy

Hi. Just wanted to say thanks for the extra schedule slots. The original five weren't quite enough.