Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Wiki Everything you wanted to know about Intelligent Octopus But Were Afraid To Ask

This site may earn commission on affiliate links.
Why write this post?
A lot of people are starting to get interested in IO. I don't think Octopus do a very good job of spelling out the benefits in their website. They have some FAQs, but the same questions keep coming up over and over on the forums.

What is it?
In a nutshell, IO is a split tariff that gives you a cheap off-peak rate for charging your EV and other electrical items in the household, including home batteries.

Isn’t that the same as Octopus Go or Go Faster?
The principle is the same, but in exchange for some benefits which we’ll explain, you allow Octopus to control the timing of your EV charge, so they can choose low carbon intensity and/or cheap wholesale priced time slots.

So I’m not in control of my charge? I don’t like the sound of that!
Well yes…and no. You’re in control of how much to charge and when you want the car to be ready, just like you would be normally. Within those parameters, you’re allowing Octopus to control which half-hour slots the car chooses to get to that target % charge. And you can always override IO if you want to “bump charge” through the day.

OK, but what are the benefits you mentioned for this trade off?
First of all, you get a larger guaranteed off-peak window for using household appliances and charging home batteries, etc. It’s six hours between 23:30-05:30. Go, for example, is a fixed 4 hour window.
In addition, when IO schedules your EV charging slots it sometimes creates schedules that fall outside of the fixed, six hour window. If that happens your EV charging and all your household use in these extra-slots is also charged at off-peak rates.
I have frequently had schedules give me seven or more hours of off-peak rates. On one occasion, I had a total of ten hours of off-peak rates.

Am I eligible?
You need a smart meter and a compatible car and/or charger. Since you’re reading this here, I assume you’ve got or are thinking of getting a Tesla. IO works with the Tesla API to create the charging schedules. The advantage of this is that IO will work with any* home charger. If you have a charger with smart features, you need to disable them so that the charger acts as a dumb switch. IO will control everything via Tesla’s API to start and stop your charging.
*Even your granny charger - but you need to tell IO what the max throughput is when you go through setup so that it can work out your schedules properly.

Some of this sounds too good to be true.
Phantom drain caused by having smart charging enabled in the Octopus app has been fixed as of 30th August 2022. One small side effect appears to be that schedules sometimes take longer to appear in the app after plugging in.

Further questions (to be updated in the main thread body once the edit timer on this post expires)

I have two EVs, can I charge the other while on IO?

Not with IO scheduling the charging, but you can charge any other car in the fixed 23:30-05:30 off peak window or at any other time at peak prices.

What are the rates etc?
Octopus do a decent job of explaining the peak and off-peak rates along with contracts etc. Head over to their pages to discover that.

I asked for a target % of x, but I got less than x.
There are two or three reasons for this.

The first, most common reason, is that Tesla reports battery % differently depending on where you look. The API (that IO uses) reports the gross battery %. This is generally fixed but can fluctuate very slightly. The Tesla app shows usable %. Apps like Teslamate and Teslafi can display both. Quite often, there is a delta of 2-3% which may be down to battery temp or other factors. This usable % will often be recovered as the battery warms up during a drive.

Some users have reported charging % being way off, perhaps 10% or more. This could be down to an error in the onboarding process. Some of the charger database entries incorrectly assume the charger you are onboarding is the 11kW version, without actually saying so in the charger description. The Andersen A2 was an early example of this. If you suspect this may be the case, the easiest thing to do is go through the on-boarding again and choose "Generic 7.4kW charger". It won't affect your functionality on IO in any way.

Lastly, it has to be mentioned that occasionally IO just craps out. It may be down to a comms error, a server error at Octopus' end, or just reasons. IO is a beta product and it's wise to expect one or two quirks from time to time
 
Last edited by a moderator:
There appears to be a new enrolment process with Tesla asking to confirm the access that Octopus needs. Also asks to configure a virtual key for Octopus. I’m not at home so I didn’t complete it, but it was talking to the car successfully now.
That's potentially good news then - it sounds like they may have gone to the Fleet API. My Teslascope account needed refreshing in a similar way.
 
There appears to be a new enrolment process with Tesla asking to confirm the access that Octopus needs. Also asks to configure a virtual key for Octopus. I’m not at home so I didn’t complete it, but it was talking to the car successfully now.
Is that required for systems that are already active, do you know? Or is that only when you add new cars?
 
Can’t exactly add a Tesla Virtual Key for my ‘legacy’ Model S now, but then neither do I want IOG to continue charging the car into peak again like it did overnight. Emailed their smart team to let them know. Might that be the end of IOG integration for me? Who knows.

Also tried skipping the Virtual Key stage and going straight to Test Connection, tries for 7 minutes then fails with “We were unable to control your vehicle.”
 
Last edited:
Weird, I'm trying to re authenticate my car and I don't have anything like that appear. I enter my email, password and authentication code in the Tesla login – then the Octopus app complains and says they can't pull up my information at the moment.

That sounds like the issue I had, changing password on Tesla account resolved it. Assuming that works for you, you’ll then need to reconnect phone as key if you use that and re-authenticate anything else you have connected, such as TeslaFi.
 
Octopus app launches an in-app browser to Tesla site for OAuth2 SSO and grant of authorisation to obtain car info and control charging. Virtual Key is done through a web-page callback that launches the Tesla app to add an octopus.energy Virtual Key - except not for ‘legacy’ Model S/X with only key fob and app access.

1706282095291.png

I found that I could get IOG to pass the connection test by starting the charge manually via Tesla app myself then waiting 10 minutes. However, no automated start/stop of charging via Kraken for the moment until Octopus find a solution.

Short-term mitigation is just to manually schedule charging for 23:30–05:30 off-peak window.
 
Last edited:
Octopus app launches an in-app browser to Tesla site for OAuth2 SSO and grant of authorisation to obtain car info and control charging. Virtual Key is done through a web-page callback that launches the Tesla app to add an octopus.energy Virtual Key - except not for ‘legacy’ Model S/X with only key fob and app access.

View attachment 1012464

I found that I could get IOG to pass the connection test by starting the charge manually via Tesla app myself then waiting 10 minutes. However, no automated start/stop of charging via Kraken for the moment until Octopus find a solution.

Short-term mitigation is just to manually schedule charging for 23:30–05:30 off-peak window.
I finally got the same message where I was not able to grant permission to add the virtual key as it’s a lease car, so I said I added it and proceed to test the connect which all passed and now IO us live, let’s see if it charges tonight now
 
How does Tesla confirm the Octopus access and how do you creat the Virtual Key ?
It was something like “Octopus wants access to charging data and ability to start a charge” with allow and deny options. I then got an email in German from Tesla confirming that I’d provided access to Octopus. I didn’t have to create the virtual key, and I can’t as it’s a leased vehicle.

Charging like a charm.
 
It was something like “Octopus wants access to charging data and ability to start a charge” with allow and deny options. I then got an email in German from Tesla confirming that I’d provided access to Octopus. I didn’t have to create the virtual key, and I can’t as it’s a leased vehicle.

Charging like a charm.
Yes, I went through something similar when I signed up for Tessie last week.
Including the email in German, which I though was particularly helpful ;)
 
It was something like “Octopus wants access to charging data and ability to start a charge” with allow and deny options. I then got an email in German from Tesla confirming that I’d provided access to Octopus. I didn’t have to create the virtual key, and I can’t as it’s a leased vehicle.

Charging like a charm.
Exactly the same for me, I chose the “i have already added the key” and all just worked