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:
That's just how using the API works. There's nothing to "see", at this stage you either understand what @browellm had said or you don't.
As I understand it, the Tesla will give it's API to any authorised request and can have numerous interaction at the same time so this shouldn't be an issue. IO onboarding 'registering' of the car is just that API request being made followed by a test that it's working. The two properties have different octopus account holders. Requesting the Tesla API during onboarding from two separate IO accounts is unlikely to cause a conflict but the proof is in the pudding by trying it.
So with the lack of any further info to educate me to make me understand I'll stick with my advice to try it, see what happens and share the experience. If it works great if not we learn from the experience and have a test case!
 
  • Like
Reactions: Astrape and BillN
As I understand it, the Tesla will give it's API to any authorised request and can have numerous interaction at the same time so this shouldn't be an issue. IO onboarding 'registering' of the car is just that API request being made followed by a test that it's working. The two properties have different octopus account holders. Requesting the Tesla API during onboarding from two separate IO accounts is unlikely to cause a conflict but the proof is in the pudding by trying it.
So with the lack of any further info to educate me to make me understand I'll stick with my advice to try it, see what happens and share the experience. If it works great if not we learn from the experience and have a test case!
Tesla doesn’t officially give anyone the API

My reading of what others have said is the car needs a test charge at any new location to register it which involves removing it from the existing location. That implies 1 location. The API is irrelevant, it will support a million locations as it doesn’t care, it’s whether the developers at OE allow a car to be registered at multiple locations, which the description of the process seems to say not, is what matters. Their implementation of the API ha# also been a bit naff in the past keeping cars awake needlessly although now that’s said to be fixed.

The discussion is going around in circles. It’s a bit of an edge case anyway, so if you’re yet to be convinced feel free to try yourself, the absolute best you can get here is someone else thinking it might, nobody has come forward and says it can.
 
As I understand it, the Tesla will give it's API to any authorised request and can have numerous interaction at the same time so this shouldn't be an issue. IO onboarding 'registering' of the car is just that API request being made followed by a test that it's working. The two properties have different octopus account holders. Requesting the Tesla API during onboarding from two separate IO accounts is unlikely to cause a conflict but the proof is in the pudding by trying it.
So with the lack of any further info to educate me to make me understand I'll stick with my advice to try it, see what happens and share the experience. If it works great if not we learn from the experience and have a test case!
Agreed. It needs testing. The question remains unanswered until someone has actually tried it. Once they have, that person will then know best.

Will try and test come the end of the current fix, and if the property owner decides they are happy to go on to IO.

Everything else is just conjecture. It’s just a shame some can’t express their opinions politely.
 
Last edited:
  • Like
Reactions: Nd4me
Tesla doesn’t officially give anyone the API

My reading of what others have said is the car needs a test charge at any new location to register it which involves removing it from the existing location. That implies 1 location. The API is irrelevant, it will support a million locations as it doesn’t care, it’s whether the developers at OE allow a car to be registered at multiple locations, which the description of the process seems to say not, is what matters. Their implementation of the API ha# also been a bit naff in the past keeping cars awake needlessly although now that’s said to be fixed.

The discussion is going around in circles. It’s a bit of an edge case anyway, so if you’re yet to be convinced feel free to try yourself, the absolute best you can get here is someone else thinking it might, nobody has come forward and says it can.
In regards to the location this refers to the location of the IO account. Two IO accounts equals two non related locations. As you say, the car doesn't care.
Your right it is an edge case which we all seam to have no experience of. Testing is the answer. As for doing the test myself, I'm not in that edge case situation so it would be difficult for me to create that test environment and not really something I would consider putting that much effort into😃. It would be easier for me just to claim I had done it!
 
Some interesting new endpoints have popped up in the IO API suggesting home battery integration and control in the future.
1669557998391.png
 
  • Informative
Reactions: ACarneiro
Hi - has anyone had issues with the test charge? Just tried this evening (using a three pin Tesla charger) and it failed three times. Battery was at 75% with a limit of 80%. The charger was plugged in correctly and the car was charging. Am I doing something wrong?
 
Hi - has anyone had issues with the test charge? Just tried this evening (using a three pin Tesla charger) and it failed three times. Battery was at 75% with a limit of 80%. The charger was plugged in correctly and the car was charging. Am I doing something wrong?

Failing the test charge sometimes means that Octopus is struggling to reconcile your home address with what the Tesla API reports. Do you ever have issues with your home address location when you check it in the Tesla app?
 
Any of you smart people know what I should do in this situation.

7kw charger needs replacing so limited to granny charger. Do I need to do another test charge on the granny so IO learns the new charge speed (if so how?). Also would I leave the tariff and have to come back on, on the new tariff prices?
 
Any of you smart people know what I should do in this situation.

7kw charger needs replacing so limited to granny charger. Do I need to do another test charge on the granny so IO learns the new charge speed (if so how?). Also would I leave the tariff and have to come back on, on the new tariff prices?
De-authorise the car (in your app profile settings). Re-run setup and choose generic 2.4kW charger.

You will remain on the tariff, on your current prices.