When there are a number of consecutive slots , the first slot is checked to see if it fits the parameters for action. If the first slot fails then all consecutive slots are skipped. Is it possible to make it so that all slots are tested. This would stop some of the slots that are subsequently suitable for charging, being missed?
At the moment I have to remove some selected slots to enable this to happen!
Is there another method?
A minor point in a very excellent APP.
Many thanks.
Duncan
Agile consecutive charging slots
dj10gan This has been requested before, and it's a fair point.
We can't easily at the moment, due to us condensing the 30 min adjacent slots.
However...if the slot gets skipped and is part of an adjacent block, we could simply move the start of this continuous block half an hour forwards -> into the future.
Might work quite well actually. We'll have a look.
thank you ill be interested to see.
let me know when i can try.
Duncan
not sure what happened last night some slots were missed from the range of selected slots.
IE: the 1 to 1:30 and the 2 to 2:30
all slots from 00:00 to 04:00 were highlighted. According to my log the following slots were missed
00:00-00:30, 00:30-01:00, 01:00-01:30, 02:00-02:30, 03:00-03:30 ?
This left me with only 7% battery where normally with that number of slots available there would be 80-90%
Any ideas,? Is that to do with the deployment? I did notice that the agile octopus display was showing alternate highlighted slots first thing this morning but, it isn't now!
dj10gan Can't see a slot for 00:00-00:30, doesn't look like that was set.
Slot for 00:30-01:00 seems fine - and was sent successfully and received by Giv API:
Same for 1:30-02:00:
You should be able to see that all these instructions were correctly sent by checking your Giv log too. Can you check, please? Thanks!
remind me where to find GIV log, please
I did notice that the agile octopus display was showing alternate highlighted slots first thing this morning but, it isn't now!
The slots that you see in your Giv logs were the ones that were active and the instructions sent.
However, if you have saved any changes to your Agile Charge window since this morning, or toggled Active/Inactive, those slots in the past will have been repopulated, so that may be the cause of the confusion here.
Thank you.
That is probably the reason.
I'll see what happens tonight.
there is only one entry in the Giv log, for today, 2:30 - 5:30. That being the case I suspect that if the first slot didn't satisfy the parameters the whole block would have been skipped?
I would have expected there to be more entries if it was working?
dj10gan It's correct as it is. You have one Agile user window configured to choose 6 cheapest slots between 2:30-16:00.
WW did exactly that and chose 2:30-5:30 6 slots.
If the criteria for charging had not been met at 2:30, it would have retried at 3:00 and so on. And you would have seen that in the log in the form of a message like:
Battery is at 79%, skipping Agile Octopus charge - checking next slot in 30 mins
or similar.