Thanks for the quick response.
Yes, either or both these would be good. But just as you automatically select cheap rates for charging, so it would be good to automatically select the most expensive rates for discharging.
As an example, for my schedule tomorrow, I will have completed charging by 4.30, but don't want to discharge until 7.30. Then I would recharge later in the morning at a lower rate and hold until 16.30 when the rate peaks.
kerregan Yeah, makes sense, though in fairness we pretty much know the most expensive rates for charging will be 16:00-19:00, right?
Not sure that currently requires the need for ever changing/dynamic export slots? I might be missing something obvious. Unless you're saying between that peak 3 hour period (6 30 min slots), and depending on battery capacity and discharge rate, if you dump at full rate, you may be done in 2 hours, which means WW could pick the 4 most expensive slots for export?
Could we use the Agile import rate price to determine the higher Agile export? I suppose there's a direct correlation...
Hi last night I tried the advanced setting by setting a minimum of 9.8p but it didn't work, any idea what I didn't do or what went wrong?
I think your right that the best time to force a discharge is between 4pm and 7pm and that the export schedule is OK for this. If your battery is 100% during a sunny day, then you will export automatically anyway.
When you are exporting regularly like this, then is it not time to be on the FLUX tariff, not agile.
Mat Did you have any slots selected (or WW had) already? Or change the value to 9.8p after slots had been pre-selected by WW?
That probably explained why the slots were not touched, going forward this should be applied when the new rates are available.
You highlight a good point though, we probably should go through the slots and apply that rule anyway, and add the ones that meet the criteria.
Mat Ah, sorry - yeah, right you don't have an Agile Charge window configured.
We'll get a fix out.
In fact, the better work around for your scenario is to configure any Agile Charge window eg. 00:00 and 01:00 and choose a number of 0 charge slots (we currently require it to be at least 1).
That way, the window will be looked at and the pricing rules you configured will be applied.
We will update the validation rule to allow this.
admin
I was thinking of self-consumption rather than export. Imagine for example I have a fully charged battery at noon, and no solar generation expected. I would rather consume from the grid until 16.30 and only use my battery after that time, when import is at its peak rate. This requires charging to be maintained from noon till 16.30 to prevent earlier discharge.
Another way of looking at it is that I should be charging my battery (or maintaining it at 100%) in any slot where the import rate is lower than in the immediately subsequent slot (with caveats for expected solar generation and for expected consumption during the subsequent slots).
kerregan I think that's a great suggestion as currently, if we're not charging from the grid, we are using our battery to run the home even if the half hr prices are on a par with what we chose to charge our battery. I would like to see something like a value we can set which automatically kicks the battery into supplying the house, for example over 25p. Failing that facility, a timed period would be a good compromise
admin
‘Hold charge’ is a good way of thinking about it, and hopefully something that would be relatively straightforward to implement.
It could though get more complicated over time 
. For example, I have just seen an earlier discussion which suggested being able to charge up to and hold a specified % of battery capacity - chosen to cover expected consumption over a peak period.
admin
Another twist on this. Last night I was due to charge from 4.30 to 7.00. But because the battery was already 95% full, this slot was skipped. The effect was that the battery discharged in this low cost period rather than being preserved until after 7.00 when the rate is higher.
‘Hold charge’ would be much better than skipping the slot altogether.
I like the hold charge idea, but stress to everyone not to rely on automation too much, every morning you need to check what slots are needed for the circumstances and check yourself throughout the day how your battery is holding out. Depending on the weather etc. If you rely on Automation you will get knock backs more often than not, at least until human like AI comes into it.
The more code you add, the more things can and will go wrong.
That’s true in the short term, whilst the users are enthusiasts. But the mass market needs a fully automatic solution, accepting that it will not be 100% optimised.
Reload the whole page, and use 01:00 in the To slot instead of 1.00.
Shouldn’t cause an error like this though. We’ll check the logs.
Thanks for reporting it.
