2nd EV on IOG

JonMoore

I don’t seem to be getting intelligent charge slots passed to my GivEnergy inverter when plugging in a recently added 2nd EV

ChrisR

JonMoore No, you won’t as the GE charger is not compatible with IOG. You need to have a compatible car linked, and you can only have one car linked to IOG.
When you need to charge your second car simply turn off smart charge in the Octopus App and set a timed charge from 23.30-05.30.

JonMoore

Sorry but I’ve got a Zappi charger and GivEnergy battery inverter. IOG is set to control x2 cars not the charger.

When I get intelligent charge slots on the Tesla wonderwatt detects and asks my inverter to charge the battery at the same time and works perfectly.

With the mini wonderwatt never seems to sets the intelligent charge slots.

Make sense?

JonMoore

Just plugged the mini in and got the IOG charge slots as shown. Given the car battery is low I got slots beyond my scheduled charge of the GivEnergy battery from 23:30-05:30.
Wonderwatt fails to detect yet when I plug the Tesla in it works fine.

MrMessy

I wonder if, now you have 2 devices (ie. 2 EVs) integrated to Octopus, you may need to generate a new API in Octopus, and then add that to WW.
Maybe the make it generates is different for each EV.🤔

Just a guess, so don't shoot me if I'm wrong.

JonMoore

I’ll give it a go and report back

MrMessy

JonMoore Just curious if you've made any progress with this.

JonMoore

MrMessy not yet. I’ve reset the API and now waiting for my wife to run the car down enough to get a decent charge. Hopefully tomorrow night.

JonMoore

I can confirm regeneration of the API made no difference 🙁

Does the WW developer monitor these?

KristianS

JonMoore He does.... @admin One for you

admin

JonMoore The only explanation would be that we don’t get the slots from Octopus. What’s your WattID please?

And can you let us know when you have the Mini plugged in next pls.

JonMoore

admin ID is mellow-region

Tesla charging tonight so mini will almost certainly get connected tomorrow evening

JonMoore

admin mini is charging tonight and been given an extra hour from octopus but not getting detected by wonder watt.

admin

JonMoore Nope, we are not getting any plannedDispatches from Octopus. See our detailed Octopus API response, and the plannedDispatches array being empty.

IOG raw response for user mellow-region - {"data":{"plannedDispatches":[],"completedDispatches":[{"startDt":"2026-01-23 18:00:00+00:00","endDt":"2026-01-23 18:30:00+00:00","delta":"-0.80","meta":{"source":null,"location":"AT_HOME"}},{"startDt":"2026-01-23 17:30:00+00:00","endDt":"2026-01-23 18:00:00+00:00","delta":"-1.20","meta":{"source":null,"location":"AT_HOME"}},{"startDt":"2026-01-23 17:00:00+00:00","endDt":"2026-01-23 17:30:00+00:00","delta":"-1.19","meta":{"source":null,"location":"AT_HOME"}},{"startDt":"2026-01-23 16:30:00+00:00","endDt":"2026-01-23 17:00:00+00:00","delta":"-0.52","meta":{"source":null,"location":"AT_HOME"}},{"startDt":"2026-01-23 16:30:00+00:00","endDt":"2026-01-23 17:00:00+00:00","delta":"-0.02","meta":{"source":null,"location":"AWAY"}}]}}

Can you query this with Octopus? Is this supposed to be for the same account details?

JonMoore

admin I’ll certainly try although have mixed results talking to them.

JonMoore

admin response from Octopus. I wonder if a workaround would be to use the Zappi integration rather than car?

Hi,

Thanks for sharing the API response, based on what you’ve sent, nothing appears to be malfunctioning.

When a second EV is plugged in, Intelligent Octopus Go doesn’t always create future plannedDispatches. This usually happens when Octopus can’t reliably determine that charging is required — for example if the vehicle or charger isn’t fully integrated, or the system can’t see a clear battery state / charge requirement.

In those cases, no future dispatches are scheduled, so the plannedDispatches array remains empty. Charging can still occur (which is why you’re seeing entries under completedDispatches), but the system only confirms those after the fact rather than planning ahead.

This behaviour is most commonly seen with:

Multiple EVs on the same account

Vehicles or chargers that don’t report battery state consistently

Charge limits or targets being set in the vehicle rather than via Intelligent Octopus

In short, if the system can’t see a clear need to charge, it won’t schedule future dispatches, and the API output reflects that.

If you want to improve consistency, the only real options are ensuring the charger/vehicle is fully supported and setting an explicit charge requirement rather than just a percentage cap. Otherwise, this is expected behaviour with IOG at the moment.

Hope that helps clarify what you’re seeing.

For more info - https://t.co/BaoisIc5Vl

Best regards,
Raman

admin

JonMoore Basically totally out of our hands. All we can do from an IOG point of view is check the cheap charges that Octopus give you - for which we use their API.

MrMessy

JonMoore I wonder if a workaround would be to use the Zappi integration rather than car?

Yep.
You can either request Octopus sets up charger integration for you (as you have "compatible" EVs, their system will normally try to force integration with them), or you can do it yourself by selecting and non-compatible EV with a similar size battery to your Tesla. Something from Kia.

The only difference with charger integration is you set "% to add", rather than "target charge %", because the charger has no idea of the EV's battery size or SoC.

As you have 2 EVs with different batteries, you'll need to do some quick maths for the amount to add, depending on which is connected.

MrMessy

JonMoore I wonder if a workaround would be to use the Zappi integration rather than car?

Yep!

You can either request Octopus sets up charger integration for you (as you have "compatible" EVs, their system will normally try to force integration with them), or you can do it yourself by selecting and non-compatible EV with a similar size battery to your Tesla. Something from Kia.

The only difference with charger integration is you set "% to add", rather than "target charge %", because the charger has no idea of the EV's battery size or SoC.

As you have 2 EVs with different batteries, you'll need to do some quick maths for the amount to add, depending on which is connected.