Wattid knowing-pass Tonight I noticed my batteries where being charged at times where the costs are higher than my maximum price set in the advance section Can this be looked at please Charge price below is set at 14p so no slots should be selected above 13.9 pence [URL=https://i.imgur.com/ZWsXOKZ.png][IMG]https://i.imgur.com/ZWsXOKZh.png[/IMG][/URL] Tonight’s agile pricing [URL=https://i.imgur.com/emaokot.png][IMG]https://i.imgur.com/emaokoth.png[/IMG][/URL] Tonight’s charge schedule sent to the inverter with charge slots with pricing over 13 pence [URL=https://i.imgur.com/5jAN0Vq.png][IMG]https://i.imgur.com/5jAN0Vqh.png[/IMG][/URL] can you identify why agile charge cycles costing more than 13.99 pence are being sent to the inverter please. [URL=https://i.imgur.com/wnkBuPq.png][IMG]https://i.imgur.com/wnkBuPqh.png[/IMG][/URL] [URL=https://i.imgur.com/ZkhuKHn.png][IMG]https://i.imgur.com/ZkhuKHnh.png[/IMG][/URL] Rob

Unwanted Agile Charge cycles

Rob2563

Wattid knowing-pass

Tonight I noticed my batteries where being charged at times where the costs are higher than my maximum price set in the advance section
Can this be looked at please

Charge price below is set at 14p so no slots should be selected above 13.9 pence

Tonight’s agile pricing

Tonight’s charge schedule sent to the inverter with charge slots with pricing over 13 pence

can you identify why agile charge cycles costing more than 13.99 pence are being sent to the inverter please.

Rob

admin

Rob2563 You've misunderstood how the Less than threshold works.

You have opted for 40 charge slots between 00:00-23:30.

On top of your cheapest 40 slots within this window, WW will also select any slot under the threshold, regardless of whether it is in your Agile charge window or not. In your case, your 40 cheapest slots will include prices below this value, by virtue of them being the cheapest, but in order to satisfy the 40 slots, other more expensive slots will need to be picked, though still cheaper than the ones that were not selected.

Eg. If I have an Agile charge window from 00:00-11:00 - but there are some negative slots at 21:00-22:00, they will automatically be selected regardless of them being outside your charge window.

Rob2563

admin

Thanks for the response admin
Could you clarify this some more please
I have the price below set to 14p so why would the system choose prices higher than 14p
if there are 40 slots selected for use and the price below option is set at 14p then logic says select any slots under 14 pence and ignore if more than 14.0

The logic statement basically would be if less than 14p set charge period
Else If more than or equal to 14p ignore and don’t charge

The number of permitted slots is set to 40 as there are 48 slots in a 24 hr period with 6 omitted between 4 and 7pm I guess automatically to remove the peak agile period

I have 40 slots set as the charge command would only work if the battery is not 100% charged and I review the price daily to set the below price for the next day

Am I setting this up wrong to only charge at less than 14p for instance in this case?

Thanks in advance
Rob

admin

Rob2563 The charge at less than is basically there to ensure users don't miss out on cheap or free/plunge pricing.

It came from the requirement of users saying things like: "I have a charge window setup between X & Y, but I would like to have any slot outside that window selected if the price is 0 or negative".

That is what it is used for.

The logic is:

1) Select the cheapest number of slots for the user in their defined agile window period (as long as the window is toggled Active).
Once that is done, run the following selection too:
2) For any slots at all, and provided they have not been selected in Step 1, select any slots that meet the Agile price threshold criteria that the user has specified.

Hope that makes sense.

Rob2563

admin
Thanks for the reply
Re - 2 For any slots at all, and provided they have not been selected in Step 1, select any slots that meet the
Agile price threshold criteria that the user has specified.

Can step one be modified to ensure slots are only populated if the price meets the Agile price threshold criteria that the user has specified ie the slot is only populated if the value is below the customers threshold value?
This would ensure no slots are populated at a higher price than the customer requested, providing the value is set

My process is normally to disable the active charge window
Configure my maximum price value to ensure only slots upto the set value are selected
Activate the charge window again

This appears to work fine and the required time slots get populated

I guess there are automated processes that run after my settings have been applied and the unused slots are populated with values higher than I wished

By running the customer set value check in step one would it not stop slots being used for charging at higher prices than requested?

Thanks in advance
Rob

admin

Rob2563

Can step one be modified to ensure slots are only populated if the price meets the Agile price threshold criteria that the user has specified ie the slot is only populated if the value is below the customers threshold value?

We could, but we're not going to, simply because this would change the way that most other users expect it to work, as all of a sudden, no slots would be picked (as none would be under their threshold) where they simply want the cheapest ones selected, the alternative isn't to go without leccy instead.

If there is enough demand for it, we could in theory introduce this on an Agile charge window 'select only slots below x pence'), but because of fluctuating prices, you'd end up having to tweak this all the time.

Happy to hear from other users on this.

MikeC

Yes I agree it is better as it is. So long as we understand how it works it means we are sure to charge at the lowest price possible within our chosen charge window with the bonus of extra super cheap slots if available.
Once you have achieved the ultimate by creating the "predbat" type system and incorporated solar forecasting it won't matter but in the meantime it's works fine.

Pourl

MikeC <plus 1 for what he said.

kerregan

MikeC Me too

Bouff34

MikeC Also agree....

If admin were to change to what the OP is requesting and prices as a whole go up for a day or two (say lowest prices were 20p and peak rates went up to 60p) I would definitely want to be charging but a modified logic wouldn't do this. Please leave as is.

RichardB

From reading this I think you are trying to do what I've done, I set my slots to 1 and my limit to 14p therefor it picks up every slot less than 14p

Rob2563

RichardB
Thanks Richard
I have reduced my number of slots and the charge slots are now only populated if the cost is below the price set in the advance section
In my case I didn’t want any slots selected if it was equal or above my set price and didn’t expect the software to select charge slots above my threshold figure of 14p on that particular day when I set it to prices below 14p

Reducing the number of slots appears to have worked.

KristianS

Please leave it as is. I do not want necessarily to have to review pricing every day to see which charge slots are picked below a value, that I have to review. That would devalue the value of WW IMO.
All I would say is, as per previous conversations, it would be nice to see that 'Price Below' setting on the Agile Octopus page so that you can 'change' the numbers of slots AND see the impact of altering the 'Price Below' in the same space - but again, that is just my personal preference.
PS I really like the 'Hold Charge' thin blue border - this makes it easy to see the difference between charging and holding slots - nice.
Keep up the good work!

admin

KristianS

Octopus page so that you can 'change' the numbers of slots AND see the impact of altering the 'Price Below' in the same space - but again, that is just my personal preference.

Yeah, as long as people are aware this is a global setting that is being altered and persisted.

KristianS

admin True, but only relevant to people who are on an Octopus Agile Import tariff, so is directly tied in that sense