See all Agile charge, discharge, hold and eco settings on one screen.

WindyMiller

I have been using Wonder Watt for several months now and have found it brilliant at maximising my exports when Agile pricing is low. I usually enable the charge slots with hold set during the day and hold clear at night (to maximise solar export), move a few slots around to create discharge windows then use the scheduler to put in the discharges in the gaps. However it is quite error prone and yesterday I managed to set a hold during a night slot which meant it only discharged slowly and consequently charged back to 100% earlier than it should have missing out on some cheap charge slots.

I would find it much more helpful if I could see my settings on the one screen. Each half hour slot could display charge, discharge, hold or ECO and it would be much clearer when I have scheduled slots conflicting with the Agile Octopus slots. Does this idea have much merit or it is difficult or flawed to implement?

PS I know PredBat can do this but I haven't set that up as I don't have suitable hardware.

My id is elaborate-routine if you want to see what I have setup for tonight and tomorrow as there are lots of very cheap slots available.

admin

WindyMiller Yeah for people on Agile, we'd like to bake in hold, charge and discharge/export in the same screen using different views.

It's tricky to implement, but we're aiming to get that integrated.

WindyMiller

admin Excellent

KevinD

That would be really useful, at the moment I use a notepad and pencil to jot down potential charge / discharge windows.

admin

We've added a quick and hopeful useful addition to the Agile Octopus page.

Just as we use the black start and end arrow heads to indicate Agile Charge windows, we now indicate with smaller red arrows any active discharge schedules that you may have set up in the Schedules section.

Available in Release 702.

admin

admin Fix on the way, issue with Tomorrow's rates in combo with this new functionality.

WindyMiller

admin Absolutely love this. It's so much clearer now when I have charge/discharge conflicts. Thanks for implementing this so quickly. Can you also do something similar to show when hold charge will also be set? Perhaps using blue and black arrows to distinguish them?

kerregan

admin Thanks. This is very useful. But I think it is still necessary to leave a 5 or 10 minute gap between the end of a charging slot and the start of a forced export, and vice versa. Is there any chance that the system could spot touching import and export slots and add the required gap automatically?

admin

WindyMiller the hold slots are outlined with a thin blue line, as opposed to the thick blue line for charge.

WindyMiller

admin Oh are they. I never realised that or even noticed the different outline thicknesses. I should pay more attention. :-)

admin

WindyMiller Maybe we should make it a dotted or dashed line as thick as the charge slots…

WindyMiller

admin Or perhaps a green box but as thick as charge slots?

4watts

Hi,

I am finding the new red arrows confusing as the end stops seem to be 30 minutes late.
Can the red arrow either be at the end of the period they end (right-hand side) or at the start of the period they end in? Currently, the graphic looks like they end 30 minutes later than they do.

admin

4watts It depends how you set your cut offs. If your discharges are ending inside a charge slot, even by 1 minute, we use the end arrow for the end of the agile slot, for the simple reason that a charge slot starting from the top of the hour would still lead to a conflict.

4watts

admin
Thank you fir that explanation. I will modify accordingly

johalareewi

I have been looking at this too and was wondering if it would be possible to manually select Agile slots for discharge like we can for charge. Would save having to use the discharge scheduler for ad hoc discharges and we could just use the Agile screen.

admin

kerregan Yeah we’ll need to look at this anyway, if we’re going to be introducing half hourly discharge slots on the Agile screen.
Might need some refactoring of the architecture though.