[Stinsy]

Why don't they get it working with pod point. It's a smart charger that works over net it turn charging on or off on command.

It's by far the most numerous charger surely.Every EV on my road has a pod point charger it's the one I see most frequently attached to houses.

The pod point chargers could easily be made to work but podpoint is owned by EDF so maybe they won't allow it. Or octopus don't want to because of this ?

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).

 

[Stinsy]

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

Correct. The Ohme works a bit differently to a standard charging point in that it talks to the car in the same way that a rapid charger does.

 

[Stinsy]

Are you planning to automate that with a CT clamp around the Ohme feed-in cable?

You can do that with Agile and ITTT, eg set your smartplugs to come on anytime the price drops below a threshold you set, but for some reason you can't do that with IO (so I hear).