Speak EV - Electric Car Forums banner

Signing up to Octopus Intelligent without Ohme or compatible car?

6711 Views 83 Replies 22 Participants Last post by  Alnair
Is it possible to sign up to Octopus Intelligent without an Ohme charger or compatible car? So, just using schedule charge between 11.30pm and 5.30am to get cheaper 10p rate?

I realise you’d have to state that you have an Ohme charger to sign up when you don’t have an EV on the compatible list, but other than that is there any other checks. If you never plan to use the smart charging capability, does it matter to Octopus?

Thanks, Steve
1 - 20 of 84 Posts
They do a "test charge" to check IIRC, so no.
We are on GO still for this reason.
  • Like
  • Helpful
Reactions: 2
They do a "test charge" to check IIRC, so no.
We are on GO still for this reason.
Thanks for clarifying. That rules that out then 😊
No. You will have to go onto the 12p tariff.
I am hoping that the Zappi will on the list soon.
No. You will have to go onto the 12p tariff.
I am hoping that the Zappi will on the list soon.
Do we know if they are working on it ?
Unless you invite a friend with a compatible car round for a charge while you’re signing up…
  • Like
Reactions: 1
Unless you invite a friend with a compatible car round for a charge while you’re signing up…
You have to do at least 1 smart charge every 30 days too. So you need to invite them round every few weeks and do a successful charge ;)
  • Like
Reactions: 1
Unless you invite a friend with a compatible car round for a charge while you’re signing up…
Part of the sign up process is signing into the app account for that car though, so you might find they'll start turning said car charging on and off once they've gone home!
Is it possible to sign up to Octopus Intelligent without an Ohme charger or compatible car? So, just using schedule charge between 11.30pm and 5.30am to get cheaper 10p rate?

I realise you’d have to state that you have an Ohme charger to sign up when you don’t have an EV on the compatible list, but other than that is there any other checks. If you never plan to use the smart charging capability, does it matter to Octopus?

Thanks, Steve
Have they publicly defined the API that they require? Clearly they'll want to be able to signal cheaper rates to the charge point, so the OHME integration that appears to allow any car to work with it could be done by any regular OCPP compliant charge point, not just Ohme with some proprietary method, if it's appropriately configured.
I've got to make the switch from Go Faster to Intelligent [Ohme Charger] on the 15th Jan which is a Sunday. Unsure if best to do an online switch on the Friday before or the Monday after?
I've got to make the switch from Go Faster to Intelligent [Ohme Charger] on the 15th Jan which is a Sunday. Unsure if best to do an online switch on the Friday before or the Monday after?
The switch is triggered via the Octopus app (which will then require you to sign into your Ohme account), so it shouldn't matter - but of course you could incur troubles with the process, so perhaps safer to wait for Monday in case you need to get in touch with either company's customer service?
  • Like
Reactions: 2
  • Like
Reactions: 2
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 ?
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 ?
Have you requested the integration via the app/website and encouraged other owners to do the same? ID3 is far more popular than Enqyaq, yet Enyaq is currently being tested for IO but I don't think ID3 is, so can only conclude that Enyaq has been requested more (they use a 3rd party for integration that supports both ID3 and Enyaq so its not an API issue).
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).
  • Like
Reactions: 1
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).
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
  • Like
Reactions: 1
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
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
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.
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.
Not so. the standard AC pilot signal can't do that. CCS, Chademo, GB-T and Tesla proprietary supercharger use different methods to communicate between the vehicle and charge point.
Chademo and GB-T use CAN bus, CCS and Tesla use variants of Powerline networking. None of these require the Internet to be connected anywhere.

The Ohme works by connecting to your car manufacturer's internet-facing API, which in turn will try to communicate via cellular data to your car, to wake it up, and report back on the state of charge. This clearly means that both the Ohme unit, and your car need to have Internet connectivity at the same time, and it also means that the OHME smart charging functionality that this works with cannot work sensibly if you have multiple vehicles, or multiple Ohme chargers, because the signalling goes over the Internet.
From the Ohme website: 'Some car manufacturers provide an API (Application Programming Interface) which allows access to information about your car via your manufacturer’s smartphone app.'

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.
See less See more
  • Like
Reactions: 1
My Ohme charge point was happily getting the SOC from my Ioniq 5 (via Bluelink) until early December. Then it stopped, and no amount of telling it the Bluelink credentials will fix it. Yes, I've checked the credentials. The Ohme to Bluelink API seems to have broken, so it assumes an empty battery every time.

I raised this with Ohme soon after it started but no joy, it is probably something as simple as a certificate expiring but at the moment there is no indication that it is being looked at. The Ohme pages still claim that it can use the Hyundai API to get SOC.
1 - 20 of 84 Posts
Top