We've just rolled out an initial version of Intelligent Octopus Go, enabled for a handful of users. Please DM or drop us a line at labs@wonderwatt.com with your WattID or registered Gmail email address if you would like to try this out.

Exciting. Is it just for compatible cars or chargers though, or for any car or charger?

@"Gazzagreen"#p3146 I'm in the beta if you can you have the tariff I believe it will work as its pulling from the Octopus API and controlling your inverter so has nothing to do with the car or charger. It's found my slots first time so really impressive.

Yes I’m interested please: impassioned-spirit

@"Gazzagreen"#p3146 Not related to car charger control. Mainly verifying the mapped charges for your EV and creating a hold/charge for your solar battery to match the dynamic slots, to prevent your battery draining into the EV.

@"psiloc"#p3148 Enabled for you.

I see. I'm happy on flux atm, but if I was to try this later, what I'm trying to ask is I am able to get the intelligent Go tariff from Octopus? I ask because as far as I understand it, they require a car or a charger they can control or you can't get the tariff. e.g a tesla as they can control the charging on the car, or compatible charger. Is this agreed with octopus to be able to use the WW-tariff with a non-compliant car or charger?

@"Gazzagreen"#p3151 Without a compatible EV - for which they will perform a test charge, I don't think you can get OIG. We simply check the dynamic charge slots that Octopus has assigned to your Octopus account. If you haven't got Octopus Intelligent Go, we won't retrieve any smart charge slots from Octopus when we query your account.

@"Gazzagreen"#p3151 Yep you need a car or charger that is compatible.

I might be getting a (2nd hand) Tesla later this year with Pension money :D

Hi there, impassioned-spirit First usage of IOG last night by plugging my car in and I don't think it quite went to plan! :) [URL=https://i.imgur.com/5qtopBZ.png][IMG]https://i.imgur.com/5qtopBZh.png[/IMG][/URL] So at first it picked up my smart charge of 23:30 - 06:30 and had a target of 86% at a rate of 33%, which is fine. It then, from somewhere, picked three more half hour blocks and mapped those. The problem is that in between those half hour blocks, the battery was discharged to power the house. This is not only in contradiction to the proper mapped charge but was unnecessary anyway as IOG always has off-peak rates between 23:30 and 05:30 - in fact of course the battery should still have been charging from the grid due to the dismal forecast. I don't know what happened with those additional blocks but if I check my Octopus app, those blocks are shown there right now too, so WW hasn't pulled them out of nowhere. I do know that in reality Octopus was charging my car as per the original mapped charge of 11:30 - 06:30 and this didn't get interrupted. One thing I recall, yesterday when I plugged my car in, the charge target was just 10% additional, and I _think_ it's possible that the original smart charge schedule was these three blocks. I subsequently changed the charge target to be 60% additional, and it mapped the new proper schedule. I wonder if both sets of instructions were still in the API? Is there something you need to be checking to know whether you have the latest schedule? In any case would it be possible to configure WW so that it always "knows" about the basic 23:30 - 05:30 off peak, and only does something with smart charges in addition to that? Love that you're doing this by the way, please don't take any of this as a moan!

Intelligent Octopus Go - limited beta

tedious-intention

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.

admin

tedious-intention We're effectively using the usual Giv default. We'll put something in place for this and let you know.

tedious-intention

admin I was wondering whether you'd made any progress on this. The reserve gives me an effective UPS for some 'essential' systems and I need to reset after every WW intervention. The benefits of the WW control easily outweighs the inconvenience of this though. But it would be nice not to have to do it!

admin

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.

MrMessy

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

MrMessy

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

J1m

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

admin

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.

J1m

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

KristianS

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.

MrMessy

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.

PB579

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

admin

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

PB579

admin Thank you

PB579

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?

admin

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.

craig_uk

Hi @admin,

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

admin

craig_uk All done for you now, you should see the Intelligent option under the Octopus submenu. Thanks!

admin

tedious-intention Thanks for the nudge. We have put some backend support for this in place already, but it needs more work. We'll keep you in the loop.

disfigured-proposal

Hi, is it possible to be added to the beta? My WW ID is disfigured-proposal

Thanks,

Dave

admin

disfigured-proposal Apologies for the delay, all done for you now.

« Previous Page Next Page »