We've recently bought another EV. We've been on Intelligent Octopus for about a year so are quite familiar with how it works. The app was connected to my Tesla account which tells us about the charging slots (thus the cheap hours), which was great.
I'm aware that IO doesn't currently support more than 1 EVs so I'm trying to work within its limitation. I've been considering to use the IO-Ohme integration instead, which lets it talk to the charger instead of the car. The intention is that whichever car is plugged in, it might allow us to not only charge at cheap rates over night, but also to get some off-peak rate hours at other times, like 'normal' IO does for us.
What have been confusing me are that:
Ultimately, I'm trying to find out whether it is possible to get the clear charging schedule that the Octopus app provides if we want to charge the 2nd car, in order to confirm the cheap hours that fall outside of the usual 23:30-5:30 range. The Ohme app has not given any confidence that it'll work and I'd like to avoid getting a nasty bill in case I set it up incorrectly. Does anyone have a similar setup?.
I'm aware that IO doesn't currently support more than 1 EVs so I'm trying to work within its limitation. I've been considering to use the IO-Ohme integration instead, which lets it talk to the charger instead of the car. The intention is that whichever car is plugged in, it might allow us to not only charge at cheap rates over night, but also to get some off-peak rate hours at other times, like 'normal' IO does for us.
What have been confusing me are that:
- Once IO has been set up to use the Ohme, it no longer tells me a clear charging schedule. The charge schedule in the Ohme app looks exactly the same (typically at 3.4kW over most of the night with a single boosted charge rate at 7.4kW near the time of departure) whether I'm on IO or not, whereas with IO-Tesla integration: the car would be given 30-minute slots that could get scattered throughout the night.
- Because of this, I was unable to discern how/whether IO-Ohme integration has taken effect.
- There are 2 ways to set up the Ohme:
- Without connecting to the car's API i.e., mostly dumb mode: in this mode, the Ohme does not have access to the car's SoC and any time it is plugged it, it assumes that it shall start charging from 0%.
- For this reason, I struggle to understand how IO could effectly regulate the charging schedule since it is unable to communicate with the car thus has no idea how much charge the car actually needs. If we always set it to 100% then, assuming that IO will oblige, that means we'll always get as many cheap hours as we possibly could, which seems wrong.
- Connecting to the car's API: in this mode, the Ohme does know the car's SoC and perhaps whether it's plugged in. However, I'm unable to see how it can work when the 2nd car is plugged in.
- Without connecting to the car's API i.e., mostly dumb mode: in this mode, the Ohme does not have access to the car's SoC and any time it is plugged it, it assumes that it shall start charging from 0%.
Ultimately, I'm trying to find out whether it is possible to get the clear charging schedule that the Octopus app provides if we want to charge the 2nd car, in order to confirm the cheap hours that fall outside of the usual 23:30-5:30 range. The Ohme app has not given any confidence that it'll work and I'd like to avoid getting a nasty bill in case I set it up incorrectly. Does anyone have a similar setup?.