• General

  • Intelligent Octopus Go - limited beta

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

                          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

                            J1m Your 15:49-05:30 IOG slot was processed at 15:53. It takes us a min to pick up from Octopus and sometimes they actually send mapped slots that started a few mins prior.

                            So perhaps it's just the min or two delay where WW hasn't quite processed it yet.

                                admin No worries, will try leaving it a bit longer next time. Thanks for the quick response 👍

                                  admin This is my experience now too [mostly]
                                  The watching of the drain battery into car scenario is hard to resist to interfere with, but I am learning to be patient knowing that once the dust has settled, any loss of SoC of the battery will be replenished by the upcoming charge cycle from the assigned IOG slot from Octopus - but it is hard....
                                  I too, like @MrMessy now know how I can play the system a little by using the SoC of the EV and the time expected for my EV to be ready - I am sure Octopus are learning from our interactions ;-) to my advantage thus far.
                                  I personally cannot wait for V2G technology becoming mainstream and whilst that opens up all sorts of cans for dumps of batteries into each other, hopefully API's will also be developed so that ecosystems will understand what each technology is doing and react accordingly.

                                    I agree with the comments from @KristianS
                                    It's taken quite a while, and a certain amount of fine tuning, to have faith that WW will perform and not be tempted to look/panic/interfere but, I think we're pretty much there now, certainly for GE inverters.

                                    Can I join the beta please. My id is obvious-tip

                                      PB579 All done for you now, you should see the Intelligent section under the Octopus submenu.

                                          admin When I input my account number and API I get this comment saying "an error has occurred. This application may not respond until reloaded"

                                          I have reloaded and the issue persists, any ideas?

                                              PB579 Likely the authentication failed, would you mind dropping us a line at labs@wonderwatt.com - so we can diagnose the detailed error further please?

                                              It looks like your API token is invalid.

                                                11 days later

                                                Hi @admin,

                                                Could you please add me to the IOG beta? My WattID is unlucky-field