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:
In these cases current limiting of the supply by the charger is a good option.

My supply Is 100A but I might have 15kW of night storage heating and 7kW of charger on at 11:30 and go for an electric shower.

The Zappi measures the current drawn at the meter with a current transformer and keeps the charger current matched to the 100A supply capability. This load management is going to be necessary in some cases.

When the electric shower goes off the charger will go back to full output. Similarly the night storage heaters go off once they have their required thermal charge, allowing the charger to give full output even if some other demand is in use. Using the load management means the charger doesnt have to be set constantly to a lower current, and can make better use of the slots.
In planning load management for the EV charger, where should the current transformer be placed?

My smart meter cables go to a junction box that sends one pair of wires to the distribution board in the house and the other pair to a mini distribution board (RCD and MCB) for the charger.

I see two options. Put the CT on the cable to the house distribution board and set the 32A charger to turn off if the house load exceeds, say, 40A. Seems simple, keeps total load below 72A (my supply is 100A). The charger will turn off at 40A and only turn when the house load falls below that.

Alternatively, put the CT on the smart meter cable so it measures total current (house + charger) and set the charger to turn off if the load exceeds, say, 70A. Maybe not so simple. Suppose the car is charging at 32A, immersion heater and other loads are running and I boil a kettle, putting the total load over 70A. The charger turns off and the total load falls below 70A, so the CT tells the charger to turn on again, putting the load over 70A and so it turns off again. From school physics, I seem to recall vaguely the concept of an oscillator.

I suspect that I am missing something here but can’t see what. Thanks in advance.
 
Your CT clamp is supposed to go anywhere before your house (total load) and the purpose is ideally not to turn off the charger but to reduce the load to the charger but it could indeed turn it off if it deems it to be necessary as it will always prioritise the rest of the house.
 
Sorry, this may have been covered else where, if so please link me back to the right place.

Just looking at agile pricing over the last week using this - Agile Portal and well, wow. With a 10kw battery and careful timing of hot water cycles on the heatpump, I could have been averaging ~10p/unit I think. But there has to be a worst case? How do I explore that with data?

I tried Octopus compare, but it doesn't allow for modifying behaviour. Are there historic bad days on that dashboard I can look up and use as example days? Any longer term stats on what the last 6 months has looked like?

Thanks!
 
Sorry, this may have been covered else where, if so please link me back to the right place.

Just looking at agile pricing over the last week using this - Agile Portal and well, wow. With a 10kw battery and careful timing of hot water cycles on the heatpump, I could have been averaging ~10p/unit I think. But there has to be a worst case? How do I explore that with data?

I tried Octopus compare, but it doesn't allow for modifying behaviour. Are there historic bad days on that dashboard I can look up and use as example days? Any longer term stats on what the last 6 months has looked like?

Thanks!
Select your preferred region, of course.
 
Select your preferred region, of course.
Thank you! Wow, December has a lot of negative priced days up here in Scotland!

I take it the approach is to use an HA script to divide the day into absorb, grid use and avoid times dependant on your own needs, generation and storage capability and then automate batteries, cars etc around that?
 
Thank you! Wow, December has a lot of negative priced days up here in Scotland!

I take it the approach is to use an HA script to divide the day into absorb, grid use and avoid times dependant on your own needs, generation and storage capability and then automate batteries, cars etc around that?
You can do that but Octopus have a web-based scheduler for Agile that can automate that with a bunch of batteries etc that are supported. Zappi (and Ohme I think) also has built-in Agile intelligence for EV charging.
 
  • Like
Reactions: Avendit
After my initial concerns, I’m now completely sold on the IO integration with the Zappi. It’s way better than the integration with the car. There’s no instant charging that I have to stop manually and the schedule is already showing in the app by the time I’ve gone back to my phone straight after plugging the charger in. It’s all very quick and just works without any hassle.
 
Notmeguv - I suspect this might be the case, ie: API is better served using a charger rather than the car?

New to this but learning quickly. Apols for the following dumb Q's but trying to read 152 pages isn;t going to work, so here goes:
1. I'm told to plug the car in as soon as I get home and let Octopus IO do the rest (scheduling etc). If the car starts charging immediately, I presume this would be at peak rate while Octopus talks to the car and uplaods a schedule. Octopus will then stop/start the charge at will according to the schedule?
However - it can take ages for the schedule to appear, so I manually 'stop charge' on the Tesla App until the schedule arrives.
Does this disrupt the schedule or even cancel out the benefits of IO during that plugged in cycle?

2. Why does the IO App take ages to programme a schedule - sometimes it just doesn't happen and then I have to either deselect the smart charge button on the IO app or log off the app and log back in. Anyone have experience of this?

Thanks in advance
 
However - it can take ages for the schedule to appear, so I manually 'stop charge' on the Tesla App until the schedule arrives.
Does this disrupt the schedule or even cancel out the benefits of IO during that plugged in cycle?
No it's fine to do. The delay comes from the way IO currently integrates with the Tesla API. Improvements on that score may be coming in the future.
 
Why does the IO App take ages to programme a schedule - sometimes it just doesn't happen and then I have to either deselect the smart charge button on the IO app or log off the app and log back in. Anyone have experience of this?
Sometimes it's a function of the time of day you plug in. Generally with Tesla intgration, IO is looking 12 hours ahead with the "planned dispatches" charges slots. You can sometimes force a schedule to display by logging out of the app but it's not necessary.

I can understand new users being nervous when they start with it though. Again the upcoming API should hopefully bring some confidence and benefits in this area too.
 
Notmeguv - I suspect this might be the case, ie: API is better served using a charger rather than the car?

New to this but learning quickly. Apols for the following dumb Q's but trying to read 152 pages isn;t going to work, so here goes:
1. I'm told to plug the car in as soon as I get home and let Octopus IO do the rest (scheduling etc). If the car starts charging immediately, I presume this would be at peak rate while Octopus talks to the car and uplaods a schedule. Octopus will then stop/start the charge at will according to the schedule?
However - it can take ages for the schedule to appear, so I manually 'stop charge' on the Tesla App until the schedule arrives.
Does this disrupt the schedule or even cancel out the benefits of IO during that plugged in cycle?

2. Why does the IO App take ages to programme a schedule - sometimes it just doesn't happen and then I have to either deselect the smart charge button on the IO app or log off the app and log back in. Anyone have experience of this?

Thanks in advance
We have our Tesla set to charge from 23:45. This way when we plug in it does not begin a charge immediately whilst waiting for IO to see it, set a schedule and shut it off. This approach hasn't prevented IO from setting a schedule (which can take some time after plugging in) or acting on the schedule. Where the car timing results in the car starting a charge prior to the IO schedule it seems IO shuts it down pretty swiftly. IO then takes control according to the schedule it set. This may be incorrect but has been working for us.
 
  • Like
Reactions: WarekiwiT