• General

  • Intelligent Octopus Go - limited beta

PeteC Right yeah, it's weird really why Octopus maps a few slots that fall in the 23:30-05:30 IOG cheap rate window, but perhaps we should ignore mapped slots that fall completely within this IOG off peak window.

      extraneous-pattern Great, thanks for digging that out.

      So it looks like a mapped charge slot was issued for 18:51-04:00 by Octopus, and we picked up the 04:00 AM end charge.

      We need to add a fix where if the end time for a mapped charge is within the main IOG offpeak window, we extend it to 05:30 by default.

          admin

          Added my account and API key

          Tried my first charge today and got slot from octopus but not showing on WW

          Anything obvious I'm doing wrong?

              ray82 What is your WattID please? You can find it at the bottom of the Advanced section.

                  admin

                  It's subtle-fail

                  It did seem to pick it up from 23:30 but it mapped the charge from 20:30

                      ray82

                      Car isn't plugged in but still showing mapped slots. Is that normal?

                          admin

                          They did thanks,
                          Think I've got my head around how it works now 😀 will plug in tonight afterwork and see how it all goes

                              admin I think it's because that's when it's cheaper for Octopus (and presumably lower carbon intensity on the grid). Had the same problem again this morning, and yesterday, so battery very low. Hopefully it will start charging later.

                                  PeteC This should be fixed in Release 690. We now don't save individual IOG slots that get mapped and fall within the default IOG window 23:30-05:30.

                                    I had the same problem that drained my battery again. What happened is that I plugged in the car at 02.43am when the schedule was already set. Octopus added slots all the time up to 6.30am and then from 09.30-11.00. What happened though is that the 02.43-6.30 slot got to WW but didn't work. I had it in the activity log but between 5.30 and 6.30 it didn't work and my battery charged the car. Then the 9.30-11.00 slot worked fine. It seems that the 23.30-5.30 had some priority over the 02.00-06.30

                                      angellevski Right, the issue is that the 23:30-05:30 instruction had already been sent and is set on the inverter.

                                      We need to consider how slots that start within the default IOG window and extend are dealt with.

                                          6 days later

                                          admin great thanks. I had same issue again last night so might be worth looking. Battery was 49% this morning instead of 100%. Car charging ended within the IOG time slot which was until 0400. Battery started draining at 0400 again instead of 0530. Immersion kicked in at 0415 and drained battery.

                                              @admin
                                              Have a minor issue with last night's charging.....

                                              Smart charging from Octopus 23:00-05:30 and 05:30-06:00

                                              WW picked up the slots and initially set 23:00-06:00, but subsequently overwrote with 23:30-05:30
                                              As it turns out, the EV had finished charging at 05:15 anyway, so didn't cause an issue with battery drain, but it would have, had the Octopus EV charge continued.

                                              Could you have a look at this please?

                                              As a sidenote, is there a reason the charge commands are not sent until after the charge period is scheduled to start?

                                              WW-ID:primary-hotel