• General

  • Intelligent Octopus Go - limited beta

KristianS Well I'd set the EV to do a top up charge from around 80% to 100%, as the home batteries were recalibrating, and started to charge from the grid at around 8:30p.m last night. Obviously by doing this the batteries charged at cheap rate as Octopus immediately scheduled a charge. The EV finished charging at 100% not long after midnight. I'd forgotten to unplug the car, and even though the car was fully charged these 3 schedules appeared today which gave me a cheap rate boost. I still don't understand why but I'm not complaining now 😃

      J1m schedules appeared today which gave me a cheap rate boost

      Indeed, don't knock it, sounds like a great glitch. Want to charge solar storage up cheap and you're on IOG? Make sure you keep your car plugged in past its target SOC....

        Ah don't mistake my words, financially, great. But environmentally, currently not the best was all I was saying....

        Can I join the beta please. My id is tired-eye

          Hello, @admin my Growatt battery failed to charge over night. I have checked the logs and there’s no history for last night.

          Is there a way to check to see why?

          Many thanks

            Ardvarky What is your WattID please?

            Odd - we can't find any entry in the logs for this. Schedules weren't paused I take it?

                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