[Monkeyhanger]

I have my Ohme app set to only charge while Octopus Go is on the 5p per kWh window 0030 to 0430.

Last night, I plugged in our Family spec ID3 and it started charging immediately. The usually blue screen of the app was red and the app was seemingly telling the car to charge to 100% (reading as 510 miles - I wish it had that range!).

Something clearly wrong, so I unlock the car and unplug. Checked that max charge was set to 80% within the car itself.

Checked all the scheduling on the app - all appears normal to facilitate a 5p per kWh charge, checked the charger - no communication issues, SIM signal strength all OK etc. Plug in, lock the car, same thing again - immediate charging.

I then resorted to turning the charger off by the Matt-E fuse switch, uninstalling my app and reinstalling it.

Plugged in again, and off it goes, red screen on app, crazy range target value and charging immediately.

After doing all of the above a few more times, I tried one more thing - I unlocked the car, unplugged, locked the car (leaving the plug flap on the car open) and plugged the charger back in, Everything is then as it should be - Ohme status lights cycling green/amber/red as if on but waiting for a schedule to kick in and app screen is blue, as it should be and all indications that it will charge within the 4 hour Octopus Go 5p window. Charge went through as normal over night.

Anyone else ever had these issues while charging with Ohme?

I'm not sure whether the car or the app was at fault. Our Life spec ID3 has a 100% no issues charging record. Our Family has failed to charge overnight once, and now this issue last night. Got to wonder whether it's the car with an occasional communication issue.

 

[Kansalis]

I don't have Ohme, I have a PodPoint, but if the charger is working correctly it should not allow the car to start any kind of charge out of schedule should it? Certainly on the PodPoint, if a schedule is properly active the car does nothing when plugged in & couldn't initiate a charge as the wallbox won't let it.

Sounds more like there could have been a comms issue with the Ohme charger/app talking to its server at the time you were plugging in. Perhaps it talks to the central server to confirm the schedule & there was an outage of some kind. That has happened with PodPoint once to my knowledge since they enabled scheduling.

 

[TheDrownedApe]

Only just converted to "Go" and this was my first scheduled charge with my Ohme charger on Tues night. When i connected the car (about 1600) the Ohme app alerted me that it couldn't charge as the current price was over 6p. Everything ok for me come the morning, sorry can't help.

 

[Sully]

I have my Ohme app set to only charge while Octopus Go is on the 5p per kWh window 0030 to 0430.

Last night, I plugged in our Family spec ID3 and it started charging immediately. The usually blue screen of the app was red and the app was seemingly telling the car to charge to 100% (reading as 510 miles - I wish it had that range!).

Something clearly wrong, so I unlock the car and unplug. Checked that max charge was set to 80% within the car itself.

Checked all the scheduling on the app - all appears normal to facilitate a 5p per kWh charge, checked the charger - no communication issues, SIM signal strength all OK etc. Plug in, lock the car, same thing again - immediate charging.

I then resorted to turning the charger off by the Matt-E fuse switch, uninstalling my app and reinstalling it.

Plugged in again, and off it goes, red screen on app, crazy range target value and charging immediately.

After doing all of the above a few more times, I tried one more thing - I unlocked the car, unplugged, locked the car (leaving the plug flap on the car open) and plugged the charger back in, Everything is then as it should be - Ohme status lights cycling green/amber/red as if on but waiting for a schedule to kick in and app screen is blue, as it should be and all indications that it will charge within the 4 hour Octopus Go 5p window. Charge went through as normal over night.

Anyone else ever had these issues while charging with Ohme?

I'm not sure whether the car or the app was at fault. Our Life spec ID3 has a 100% no issues charging record. Our Family has failed to charge overnight once, and now this issue last night. Got to wonder whether it's the car with an occasional communication issue.

Same with my BMW i3 but only noticed when car told me it was full. Same screen as you on the Ohme app but with 311 miles ( I wish) Contacted Ohme who of course blame the car / BMW and can you enter vehicle details again. This has not done anything ie still have red screen, although car is away at the moment so will monitor tonight. I have replied to Ohme explaining the issue is the charging over 5 p when on Go not that it can’t talk to the car. I noticed an Ohme iOS update after the event and have updated but still getting the red screen so Who knows.

 

[Monkeyhanger]

Same with my BMW i3 but only noticed when car told me it was full. Same screen as you on the Ohme app but with 311 miles ( I wish) Contacted Ohme who of course blame the car / BMW and can you enter vehicle details again. This has not done anything ie still have red screen, although car is away at the moment so will monitor tonight. I have replied to Ohme explaining the issue is the charging over 5 p when on Go not that it can’t talk to the car. I noticed an Ohme iOS update after the event and have updated but still getting the red screen so Who knows.

I'm on Android app, but as per the end of my post, it got solved by locking the car (with the plug plap still open and accessible) and then plugging the car in. Doing it that way, I got my blue screen back, scheduling worked, and no crazy range quoted.

I usually plug cable in and then lock car (as is logical).

You might want to try locking and then plugging in if you have same red screen issues.

 

[Sully]

Will investigate further as it was too late last night. I just wish it would do as it’s told and use logic ie only charge between set times and only if set price is achieved. Fed up with the stock answer that it is the fault of BMW.

 

[Monkeyhanger]

Will investigate further as it was too late last night. I just wish it would do as it’s told and use logic ie only charge between set times and only if set price is achieved. Fed up with the stock answer that it is the fault of BMW.

It's only happened once so far, and only on one of our 2 ID3s which coincidentally failed to charge one time. There could be some iffy communication going on either between Ohme and the server, or Ohme and the car. All indications on mine last night were that the Ohme was receiving a proper and full signal from the phone network it's attached to.

 

[Mr_ess_jay]

Mine did this last night, assumed it was something I'd done. Unplugged, replugged, solved.

 

[Monkeyhanger]

Maybe there was a widespread network outage for a short while last night? I was messing with mine at about 2145-2200.

 

[Sully]

It's only happened once so far, and only on one of our 2 ID3s which coincidentally failed to charge one time. There could be some iffy communication going on either between Ohme and the server, or Ohme and the car. All indications on mine last night were that the Ohme was receiving a proper and full signal from the phone network it's attached to.

Well didn’t go to max charge when plugging in tonight but ohme isn’t speaking to the car which is relatively normal. It’s not an issue as can normally fully charge in the 4 hour window. No matter what the issue was last night defaulting to max charge when plugging in without a notification is not good. Glad I’m not on Octopus Agile any longer which the charger was sold as ideal for, any savings soon get wiped out.

 

[idiotzoo]

Contact Ohme support. They may be able to check logs for the charger/account and see what happened. The Ohme does what it’s told or, in absence of that, just charges at full rate. If I’m reading your post correctly, the app suggested it was charging to full immediately, so there’s a likely a problem with the backend not implementing the charge settings.