• General

  • Intelligent Octopus Go - limited beta

admin Not that I'm aware off.
I set up the Planned Intelligent charge slots to charge to 100% a while back and it's been working like a dream until last night.

Below is my config:

Many thanks

      Ardvarky Looks good. We've added some specific additional IOG logging and deployed that to for the IOG functions so we can diagnose and understand what's happened and fix if it happens again.

          admin
          Ok thanks!

          Fingers crossed it's goes back to working overnight and was just a glip.

            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

              MrMessy Yeah, I think you raised this before, so this is all about finishing as close to the 00/30 min on the hour mark, correct?

              We'll get this sorted.

                  admin yeah, that's pretty much it.
                  Whatever 1/2hr segment you're currently in, even by 1 minute, the cheap rate will run to the end of that, assuming you're outside of the core o/nite hrs.
                  eg 06:45 -> 07:00,
                  07:01 -> 07:30

                      MrMessy That's deployed in a server fix now. Front end version number won't reflect this (yet).

                      If there's no Octo mapped slots and we have an active IOG charge running, and not in default IOG window, we only disrupt the schedule at 28/29/58/59 min marks.

                          Just a very minor thing - and everything seems to working great, but for the last few nights the IOG charging schedule appears twice (see screenshot). Any ideas why please? neat-permission

                            J1m Yeah we know why, we're looking further back for IOG slots as they sometimes get issued with start times up to 5 mins ago. But this is a bug at our end and we'll fix this.

                              5 days later

                              admin unfortunately, this is still not working correctly.
                              I would have expected WW to set the end time to 07:00 in this scenario, rather than 06:37.......

                              Could you have a look please?

                              primary-hotel

                                  MrMessy It’s working for the scenario where you unplug the car, but fair point, for general IOG end times this needs to be in place too.

                                      admin so you're saying that if I'd unplugged the EV between 06:30 and 06:37 (before Octopus had ended the schedule), WW would extend the charge slot to 07:00 but, because the EV was still plugged in at 06:37, the charge slot was not extended?

                                          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.

                                            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.

                                                admin fab! I'll let you know in a couple of days, as per usual.😁

                                                We'll be making use of additional smart slots this week to keep the ASHP running on the cheap.😅

                                                  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.🤣