Agile Octopus integration
I want to try it then and hit the "Stop export at" value, I'll try it tonight when we're passed the peak period.
OK - fair few bits rolled out now in 351 release. Thanks again for all the testing, your help is appreciated.
Success
May the wind keep blowing!!!!
Back again :D
Everything worked swimmingly last night to get some cheap electric except for the 00:00 - 00:30 slot which did not activate for some reason.
A minor glitch I’ve spotted with my Growatt system is that it retains the last charge instruction received. This means that it will repeat that last instruction at the same time every day, if nothing else has been received. A few nights ago my last charging slot was 03:00-03:30; the next night my first slot didn’t start until 04:00, but I had an unexpected 03:00-03:30 charge.
Is it possible to ‘clear’ the settings after each charging period has ended to avoid this?
Or possibly just send a 00:00-00:00 charge instruction at 22:59 each day?
I've noticed with the constant improvements to the WW / Agile Octopus integration that I've become far more relaxed and confident about what it's doing, whereas previously I was always checking what slots had been allocated, had it sucessfully charged etc. A great job by the developers
I’ve had an initial go with the new battery Hold charge option, which seems to do exactly what it says it will do (prevent the battery from discharging during the gap slots between the selected charge slots). Unfortunately I have a single Charge window setup, running from 23:00 to 22:59, and today had charge slots selected early afternoon & this evening, so the Hold charge feature stopped the battery supplying the house during the peak 16:00-19:00 period.
Luckily I spotted what was going on a few minutes after 16:00 & manually disabled the feature (interesting use of the Growatt Charge Stopped Soc parameter).
Going forward I suspect I’ll need to alter my Charge window to 19:00-16:00, or have two windows (23:00-16:00 & 19:00-23:00), unfortunately both these options can restrict the automatic selection of the best slots.
Thinking about it more, there are certain times of day or situations when you want to hold the charge, and others when you definitely don’t! Would an alternative implementation, that may side-step the above issue, be to just specify a threshold price (like the Automatically pre-select import slots on the Advanced tab), below which the charge in your battery is held, so your house & EV charger etc can be supplied direct from the grid when pricing is low?
WattID: tedious-clothes
- Edited
Going forward I suspect I’ll need to alter my Charge window to 19:00-16:00, or have two windows (23:00-16:00 & 19:00-23:00), unfortunately both these options can restrict the automatic selection of the best slots.
Yeah that should do the trick.
Would an alternative implementation, that may side-step the above issue, be to just specify a threshold price (like the Automatically pre-select import slots on the Advanced tab), below which the charge in your battery is held, so your house & EV charger etc can be supplied direct from the grid when pricing is low?
Interesting thought, although the evaluation to hold the charge basically is done after a charge slot finishes, and isn't re-evaluated at every 30 min interval (unless at the end of the charge window time).
Furthermore, depending on general price fluctuations, you might still end up holding charge when you don't want to. The onus is then on you to tweak this price threshold fairly often. So I feel that's just moving the problem around a bit.
Alternatively, it might make sense to have an 'exclusion hold-charge' window in Advanced, which would default to 16:00-19:00?
I’m not sure how typical a user I am, but I usually want to charge my battery using the cheapest slots overnight, and then occasionally set 1 or 2 slots manually in the afternoon when there’s been no solar or I’m concerned the battery won’t get us past 19:00 / to the next cheap overnight slot. So overnight, I would generally like to hold the charge (so EV can complete charge etc) and then, when the prices start going up / household demand increases, I want to run off the battery.
Maybe setting one or more ‘Hold windows’, same as the Charge windows, to pre-allocate periods each day, is the best fit for most people’s needs? I’m not sure how easy this would be to implement, as I guess at the end of each charge period, you would need to check if the user was in a hold period & then alter the Charge Stopped Soc if necessary. (I assume the Charge Stopped Soc is automatically reset to 100, in the Growatt implementation, at the start of each charge period?)
Sorry, I’ve just re-read your post above, and realised this is, in effect what you’re suggesting at the end!
- Edited
Giles I am worried about introducing much more complexity and putting other and new users who have not been on this journey from the start, off.
I think for now it’s fairly reasonable to set multiple Agile charge windows up either side of the 16:00-19:00 period, don’t you think?
Or just until 16:00. Because if you’re checking each day anyway, it’s easy enough to manually select the odd slot here and there?
You’re quite right, above all it needs to be simple! The beauty of WW is that it’s largely automatic when set up, and the time-slot grid makes it very intuitive to manually add or remove slots on an ad-hoc basis.
I’m going to run for a few days with multiple Charge windows and see how I get on (23:00-06:00[hold charge] & 06:00-23:00[discharge]). Obviously I’ll lose out on the optimal selection of low-cost slots, but hopefully this won’t be significant.
I am concerned that this approach still doesn’t stop my house battery occasionally dumping into the car, in situations when the last automatic slot ends before the car is fully charged. The only real solution to this would be your suggested ‘exclusion hold-charge' window in the Advanced tab?
