Both Octopus and MyEnergi have said Zappi integration is being worked on/coming. But absolutely no timelines, etas or promises unfortunately
Both Octopus and MyEnergi have said Zappi integration is being worked on/coming. But absolutely no timelines, etas or promises unfortunatelyDo we know if they are working on it ?
There is the new Plug & Charge protocols
This would increase the complexity of a standard home charger
This therefore increases the price point of the charge poin
Kind of sums up how it is all going. Lots of complexity, lots of cost, great while it works but hard to maintain in production with all of the combinations of car and charge point.My Ohme charge point was happily getting the SOC from my Ioniq 5 (via Bluelink) until early December
It seems to me that the best way to handle this is to separate out the code that speaks to the car, to present a standardised interface. It's the sort of thing the free software community is good at. Then Octopus can concentrate on the proprietary bit of code that does the scheduling (deciding when each car should charge), and hobbyists can concentrate on how to make their car and/or chargepoint start and stop charging. Octopus would obviously have to maintain a reference implementation, but they've already got those.Kind of sums up how it is all going. Lots of complexity, lots of cost, great while it works but hard to maintain in production with all of the combinations of car and charge point.
I thought PnC was also DC only? Interesting to see its on the AC side too.There is the new Plug & Charge protocols, which can use CCS-like signalling for negotiating AC charging, but at present very few cars actually support it (VAG MEB platform is one), and you'd need the support from both the charge point and the vehicle, but at least that way, you could tell which one of your possibly compatible cars is physically connected to which one of your compatible charge points at potentially different locations. This would increase the complexity of a standard home charger by requiring something akin to a powerline modem in there, as well as running a full IP protocol stack on that interface (in addition to any local, or 'cloudy' networking it does). This therefore increases the price point of the charge point.
It's there to support AC bi-directional charging.I thought PnC was also DC only? Interesting to see its on the AC side too.
A car can have multiple contracts loaded, and you can choose which one to present, much like you can with Google Wallet or Apple Pay when using contactless payment.Interesting insight thanks.
One thing, I'm sure its in the specs, but how does Plug and Charge play with multiple companies/apps offering different rates to the same charger? Say with my Enyaq (and V3.1 which has PnC), I rock up to Ionity (which supports PnC), I can charge using either my Skoda PowerPass (Elli), Octopus Electo-whatever or Bonnet. Is there scope to be able to pick which one would be used for PnC? At the moment, Skoda are saying their implementation will only work via PowerPass. AFAIK, and I've not seen it in the wild, you can install the cert from the SkodaConnect app which I assume is somehow linked to PowerPass. Would be ideal if you could plug in and it was like hey, you've signed up with these 3 providers, which one do you want to use, but I'm also wondering if they've missed that trick with it and you can only have one cert and whoever Ionity sign up with is who you're left with if you want to use PnC. PowerPass being VWG, its likely only to work in their little world rather than a real standard to open up operability like it should.
You must be able to get state of charge / level communication between car and charger to some degree surely ?Octopus want to do more than just turn the charging point on and off, they want to read the SoC (and possibly other stuff too).
Not through the existing primitive protocol between car and (AC) chargepoint.You must be able to get state of charge / level communication between car and charger to some degree surely ?
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.They may very well want it but I thought this was primarily about balancing load / demand for car charging. So can be turned off / on as required.
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.
Hmm - one downside I can think of... if IO cannot monitor charge level on car, then it can only know that it turned the chargepoint on for a total of 4 hours. It wouldn't know whether the car was actually plugged in and taking charge. So if I happened to use the car just when IO decided to charge, I'd miss out.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.
Yeah, that's one way they do it. But with an Ohme charger, it can operate without being able to speak to the car at all.IO monitors car charge level, not by the charger talking to their systems, but by the car data that is shared with the owners phone app, also being shared with octopus.
Only because Ohme do the same trick of talking to the car’s manufacturer’s back-end API to get the data. The Ohme-to-car connection is still just a dumb type 2.Yeah, that's one way they do it. But with an Ohme charger, it can operate without being able to speak to the car at all.
Ohme 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.Only because Ohme do the same trick of talking to the car’s manufacturer’s back-end API to get the data. The Ohme-to-car connection is still just a dumb type 2.
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.
I assume there's some constraint to prevent abuse of the system? Eg can I tell it at 4pm that I want 28kWh by 8pm and get peak-time energy at cheap rate ?My understanding is for cars that cant get the SoC, the app offers a number of kWh you want to put in (bit like Zappi on boost). So it will assume you get say 7kW and work out how many half hour slots you will need and go from there. So you could well get extra slots anyway if it thinks you need a lot of charge.
Don't think they ever guarantee that if you tell it that you will get cheap rate. It works the same as telling them when you need X% by, as you can do that if they know the SoC too. It only tries to schedule it as best it can is my understanding so if you tell them you need so much charge, it will probably just say its not possible. Hopefully someone with it can chip in.I assume there's some constraint to prevent abuse of the system? Eg can I tell it at 4pm that I want 28kWh by 8pm and get peak-time energy at cheap rate ?
That is indeed a loophole that has been discovered and abused by some people - but, judging by some comments on the Octopus forum, the fightback is starting...I assume there's some constraint to prevent abuse of the system? Eg can I tell it at 4pm that I want 28kWh by 8pm and get peak-time energy at cheap rate ?