Intelligent Octopus Go - limited beta
Have a minor niggle with WW ending smart charging sessions.
My Octopus charging session was scheduled to end at 07:00 this morning and WW picked up all the various changes through the night without issue...
My daughter unplugged her car at 06:49 this morning (before the scheduled end time and whilst still charging) and WW almost immediately ended the session, reverting back to GE battery powering the house, rather than waiting until the 5min slot before 07:00 to swap things back.
Now, it's only 10mins in this instance, but I suspect if she'd unplugged at 06:31 something similar may have happened, meaning I'd have had half an hour of battery draw when it could have still been grid draw at 7p/kWh.
Could you have a look please @admin as WW appears to be picking up the wrong end signal in this scenario? TIA
primary-hotel
- Edited
Thank you for enabling this function for me. All good so far - lots of extra charging slots for my home battery. I will check my bill at month-end to see if they were charged at the 7p rate! One query - I notice that, at the start of the process, an instruction is sent to set my reserve at 4% overriding my setting of 9 or 10%. Is this an essential part of the process? I normally like to keep a small reserve to ensure some systems keep running in the event of a power cut. Thanks again.
tedious-intention We're effectively using the usual Giv default. We'll put something in place for this and let you know.
MrMessy That's right yeah, though you may not have seen this in the activity log.
We're rolling out an update for this now though, which will round up the appropriate IOG mapped slot end time to the next 00/30 mins. So by doing this earlier in the pipeline, everything else downstream should work with these updated end times. You should only see 00 or 30 min end times for IOG going forward.
Server update to be deployed in the next 10 mins.
- Edited
admin apologies for the delay in responding. Wanted to make sure I'd tested this properly before coming back.
The slot end time 00/30 works perfectly. I've had numerous goes at this, unplugging just after the half hour and each time the Giv charging has ran to the expected point.....
...... as long as the EV is physically unplugged and we get similar to this in the Octopus app, saying unplugged:
I presume at this point the Octopus API despatches a signal and this is what WW is reacting to?
The only fly in the ointment is, when I get an early evening charge slot (IOG is so easy to manipulate, if you know how) and then a bit later reschedule to get morning slots. An ASHP chews through quite a few kWh when the temp hasn't been above 0β°C for 3 days.
In this 2nd scenario, I'm guessing there's no signal for WW to react to as the EV hasn't been physically disconnected.
Anyway, as this stop/start EV charging is initiated by me, it's easy to update the times in the GE app, so no big deal.
Overall, thumbs up for this fix.
Off to see what other bugs I can find.
- Edited
I've just (about 3:50p.m Saturday) plugged my EV in, which commenced to charge - as an immediate slot was created by Octopus. However when I checked the Giv app I noticed that charge (3kw+) was being drawn from my home battery as well as the grid. I left it a couple of minutes to see if it would revert to charging the battery as expected (and set in the IOG schedule) but it didn't. I then paused the battery in the Giv app which stopped it discharging then reselected 'play' and the battery then started to charge as expected.
I had this issue also the last time I plugged my EV in a week ago (same solution) but thought it was a blip but it's now happened again. Any advice please?
neat-permission