As far as my Ohme is concerned I have a dumb MG ZS. If I tell the truth and connect the Ohme to Nissan Carwings I want to throw it in the bin, lol.Oh - how does that work? AFAIK the simple comms between car charger and AC chargepoint doesn't allow the car to send that kind of information. Obviously when Octopus is speaking to the car directly, it can get that, but when controlled through the Ohme integration, for example, it surely has to do without?
Ah... it seems that Ohme can integrate with some car manufacturers to find the SOC from the car. So I guess it's Ohme doing that bit, rather than Octopus.
Charging with API Support
Must do as there are people on the forum with Ohme/original MG ZS. So on the back of that my Leaf is actually an MG ZS on the Ohme, lol. Carwings integration does my head in hence running it dumb.Not through the existing primitive protocol between car and (AC) chargepoint.
I agree - while it would be nice to have, it turns out that the Ohme can get charge level from only some cars, so IO must be able to work without it. I'd be perfectly happy with being able to tell Octopus I want to charge for a total of 4 hours between now and noon on Saturday, for example. Though it's not much extra work for them if I ask for 40% to be added, once they know that my car is X kWh and my chargepoint is Y kW (taking charging losses into account). Except when I'm doing a 100% charge for balancing, which can be very slow. But that can just be done using the 6-hour timed slot.
Building on what you are saying... Do you only get extra off-peak charge slots if Octopus can see your SOC? CheersOhme are able to speak to some cars via the manufactuer's back end. For others, it still works with IO, but you don't get the charge level feedback.
Can't see any link with Agile unfortunately.An interesting experiment might be to see if those correlate with cheap agile slots.
It certainly makes it easier to understand if Octopus simply make cheap slots available unconditionally on whether the car is plugged in and charging (on the assumption that if the car is plugged in, the Ohme will take advantage of such cheap slots automatically).
Yep, my ramblings are all over the place as I try to figure out this tariff, lol.That's my understanding as well. It doesn't matter if Ohme read the SoC or not because if not the user is responsible for asking a specific amount of kWh by setting the '+XX% added range' in the charge schedule.
If you're preventing the car from charging when Octopus (via Ohme) tells it to, you're missing out on any cheap slots outside of the default off-peak hours...
...which would explain this...
...but not this 🤔 it looks like a bug in the system, but of course one that works in your favour. I've never had such luck
That's the first time I hear of that happening to anyone, and I'm pretty sure Octopus would swiftly act to change that behaviour if it was widespread!
I'll give it a go but at 40p kWhOn another recent thread about IO, it has been mentioned that it is normal behaviour to start charging immediately, but that only lasts a few minutes before it stops and waits for a cheap slot.
Variable pricing worked with Agile without issue.There's another thread talking about IO. As far as I can tell, when IO is using the car API directly, it has to allow the car to start charging so that it can get notified that the car is plugged in. They stop the charge as soon as they have noticed.
For the Ohme charger, it ought to be possible in principle to discover from the chargepoint that the car is plugged in without actually starting to charge - the chargepoint can know from simple signalling between car and chargepoint. Whether it's actually implemented that way is another matter, of course.
I’m just to chicken… 🤣But the point is that it WON'T be 40p peak! As long as you aren't explicitly requesting to charge immediately, you'll always be billed at the cheap rate for any half-hour slot where the car is charging.
Following your advice decided to pull up my big boy pants and it works! 👍But the point is that it WON'T be 40p peak! As long as you aren't explicitly requesting to charge immediately, you'll always be billed at the cheap rate for any half-hour slot where the car is charging.
No, just talking about the ohme plug-in sequence, cheersHmm... does mean that simply plugging in your car at the same time as you turn on your oven for your evening meal, you get all that energy at cheap rate ?
Yeah sorry, I've put a note on the phone of when I plug in so there is a record to check against the next bill. Now I have the confidence to plug in I need to setup some smart gear to trigger other devices when random cheap slots come along...Yes, I got that. I thought you meant that when you first plugged in the car, it started charging, and that was cheap rate because it was part of the IO sequence.
That would seem to be the easiest way. Or the driveway cam could pick up on the dashboard charging lights flashing and trigger x 🤣Are you planning to automate that with a CT clamp around the Ohme feed-in cable?
In that scenario, Ohme said I'd be charged off peak whereas Octopus said the opposite, lol.But the point is that it WON'T be 40p peak! As long as you aren't explicitly requesting to charge immediately, you'll always be billed at the cheap rate for any half-hour slot where the car is charging.
Will certainly be interesting to see the first proper bill. Cheers!Probably another occurrence of being unlucky with the customer care lottery?
Point 5b of the terms & conditions clearly states:
If we schedule your electric vehicle to charge outside of the off-peak hours 23:30 to 05:30, we'll give you the night rate for your EV charging and any underlying household usage in any charging half hours.
So the key point is to make sure that it's them scheduling the charge - i.e. no price cap, no explicit request to switch to max charging, and no preconditioning (as that effectively means max charging) outside of the cheap hours.
I keep double-checking my bills and it's still all off-peak when the car charges 🤷♂️