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:
Thanks - moved over on Friday and after the testing all seems to have gone smoothly so far. Arrived at work today, moved the slider from 50 - 90 and it charged at work no issues. Will see what happens when it gets home and if it tries to schedule a charge (ie follows the car setting) or if it follows the app and doesn't need to charge (app is set to 50%). Good tip on the 2.15 might also try that if have a trip the next day.
Subsequent to that post I realised it does definitely say in the blurb it only applies at your home location so in theory it is geolocated and it should not interfere with work charging.
 
She is incorrect.
The email sent to SEG customers specifically said the tariff would be migrated by the end of that week.
Which it was.
I'm just coming back to outgoing fixed after trying to "chase the cash" with an application to Scottish Power (never got set up as their payment portal is dire and doesn't work). I called octopus support this morning and I'm due to be back on outgoing fixed on 20 September
 
The 12 months fix just means the tariff is guaranteed for 12 months.
AFAIK, as there are no early exit fees you are still free to change whenever you want.
Some of Octopus’s recent fixed tariffs, such as an Intelligent fix (rather than sticking with the variable version) do have early exit fees. They explain it on their website that they apparently need to pre-purchase the energy upfront and have to cover themselves in case prices drop further.
 
Having had no problems with IO since joining in the Spring, on return from holiday I find it no longer works. I plug the car in, a schedule appears, the car briefly charges in the night and then stops, in the morning I find the charger, an Andersen has tripped and the car shows 45 amps at this location.

During the daytime I suspended IO, all worked correctly, car showing the correct 32 amps. I then reinstated IO and bumped the charge, and again all worked well. In the night however the same problem, the charge stopped, but on one occasion there was no tripping, so I suspended IO and received a badly needed charge.p that night.

Last night the same initial behaviour with charge starting and tripping the Andersen.

Any ideas?
 
For anyone interested, MyEnergi / Octopus have today started beta testing IO integration with the Zappi.

The integration is pretty simple, you log in with your ME account and link only the charger to IO. You tell IO what car you have so it knows the battery capacity. The Zappi remains on Eco+ so it can PV surplus charge. You configure in the Octopus app how much you want to charge (%) and it will map boosts to charge that much.

First day, today. I have it configured so we’ll see how it goes tonight.

It’s a pity it doesn’t also integrate with Tesla to pull the SoC. I prefer just telling it to charge to a specific SoC every night. I’ll need to see if something can be done with Home Assistant to automate this.
 
ok so that didn’t work..

plugged in yesterday evening, had my zappi set to eco+ from a previous day so it didn’t start charging. I expected the octopus app to still set a schedule though? It says ‘when connected’ and the tesla knew there was a cable connected, just that there wasn’t power yet.

In the end I forgot to change mode on the zappi so it seems to have just done the usual overnight block eco+ boost timing.


so do I have to switch the zappi into fast mode? Wanted to avoid peak usage that you normally get from that
 
ok so that didn’t work..

plugged in yesterday evening, had my zappi set to eco+ from a previous day so it didn’t start charging. I expected the octopus app to still set a schedule though? It says ‘when connected’ and the tesla knew there was a cable connected, just that there wasn’t power yet.

In the end I forgot to change mode on the zappi so it seems to have just done the usual overnight block eco+ boost timing.


so do I have to switch the zappi into fast mode? Wanted to avoid peak usage that you normally get from that
When using the Tesla integration, IO can’t override the Zappi’s Eco+ mode. You need to set it to Fast for IO to work correctly. If using Eco+ with a boost timer, only the scheduled charges during the timer period will occur.
 
When using the Tesla integration, IO can’t override the Zappi’s Eco+ mode. You need to set it to Fast for IO to work correctly. If using Eco+ with a boost timer, only the scheduled charges during the timer period will occur.

it didn’t seem to have set a schedule even though which surprised me. although I didn’t check until this mornign so maybe it disappeared already? might try that again.

what was the sequence people were using to avoid fast charge then? Was it tesla-side
 
it didn’t seem to have set a schedule even though which surprised me. although I didn’t check until this mornign so maybe it disappeared already? might try that again.

what was the sequence people were using to avoid fast charge then? Was it tesla-side
it actually did not set schedule yesterdy when I was doing something similar on my podpoint (for HA integration and automation) - plugged in but not charging (no power available). although it set up schedule once started to charge as per normal slot after half pas 11... need to check agian.. maybe a fluke from IO.
 
  • Like
Reactions: Mrklaw
so do I set the tesla to not start to charge until eg 11:30 adn then I can safely plug the zappi in 'fast' mode and IO will change the tesla start time remotely? That the best way to avoid the use of peak rate when I first plug it in?
Personally I just stop the charge on the Tesla app after I plug in. Others use the hack (or some variation) you suggested above.

The reason I don't is that you will get a small charge spike at 23:30 across the grid which is not really good for the grid when you multiply it across a large number of cars charging and exactly the sort of thing they are trying to avoid.
 
  • Like
Reactions: Obie
so do I set the tesla to not start to charge until eg 11:30 adn then I can safely plug the zappi in 'fast' mode and IO will change the tesla start time remotely? That the best way to avoid the use of peak rate when I first plug it in?

The car will wake and start charging at 23:30, then sometime later octopus will detect this and stop the charge restarting when one of the planned slots arrived
 
The car will wake and start charging at 23:30, then sometime later octopus will detect this and stop the charge restarting when one of the planned slots arrived

so the octopus app won't even know the car is connected until the car sees some juice? Thats odd - the car knows its connected (but not charging) as soon as I plug in, you'd think that'd be surfaced by the API

so simplest thing to do is just leave zappi in fast mode, plug in, then stop in the tesla app? Thats what I was doing last time I was on IO. I can't wait until later as I need to consider adjusting the battery discharge times if it gives me extra slots..
 
so the octopus app won't even know the car is connected until the car sees some juice? Thats odd - the car knows its connected (but not charging) as soon as I plug in, you'd think that'd be surfaced by the API

so simplest thing to do is just leave zappi in fast mode, plug in, then stop in the tesla app? Thats what I was doing last time I was on IO. I can't wait until later as I need to consider adjusting the battery discharge times if it gives me extra slots..

There are 2 APIs - one that gets interrogated and in doing so wakes the car or keeps the car awake and one that pushes a limited set of data
So if you're too slow in plugging the cable in IO will already have stopped requesting that data to allow the car to get to sleep, you can tell if this has happened as you won't get served any slots.

Even if you have slots the car will awake at the chosen time as that's what you've told the car to do, eventually Octopus will notice the car has awoken and that it is charging and take over.

Personally I charge my home battery from 23:30 - 05:30 and whenever slots outside this become available (I check the IO API at the start of every 30 minute boundary as they do get shuffled around)
 
Okay, 130 pages of posts is a lot. Could we sticky a beginner guide to IO at the beginning? I have M3RWD and just changed to Octopus. I have an Ohme Pro wall charger and I don't know if its best to set up IO with the wall charger or just the Tesla. I wont need to charge every night as I can charge at work, so would need it 2 or 3 times a week depending on mileage done.

Also I have the option to change to IO from now, is it worth waiting until after October 1st or is this tariff not affected by the lower price cap?

Anyway thanks for the huge thread!
 
Also, I have just had a heatpump installed so would it be a good idea to get the car to start a charge, then stop it so that I can power the heatpump for the house on the cheap rate overnight? or does this not matter and I get cheap rate every night even if I don't charge the car....?