I guess that when the test charge is done as part of the sign up process for the IO tariff the specific EV is identified for smart charging, which is fine if the car’s app/backend is reliable. Your workaround is great RKJM30, I use scheduled charging from our 2nd EV (can only have 1 car on IO at the...

Yes, the app mileage mis-match is a bug they have known about for a long time, it’s one of the issues I contacted them about many times. This is the last message they sent me about it back in March. I could not get them to commit to it being fixed. “If the vehicle is set in miles. The ICAS1 (which i...

Yeah, Ionity charging is consistently favourably reported. I’ve seen Borns peak at 130kwh from low SoC on various YouTube reviews on those, definitely worth trying.

Best of luck with that! I was always dissatisfied with the DC charging, never saw the “real-world” fastned speed for 10-80% in 31 minutes, let alone the “theoretical” Cupra speeds you’re talking about.

Indeed, looks as if the next revision will make it clearer.

I believe @Elea4 has mentioned that previously, that screen doesn't tell you if your car is 3.1 or 3.2

The reversing camera is a speed thing, once you’re moving forward above a certain speed it goes off. You can also switch it off yourself before that using the X top left of screen.

The Born is an excellent car, as is the Taycan, but obviously miles apart in performance, range, charge speed, size and therefore not surprisingly price. The Born having left hand drive wipers, no vents in the back, no lining in door bins or trim on rear doors and poor wireless charger reinforces it...

Assuming your Tesla charger uses a type 2 connector can't see why not.

I’ll try that with similar app issues in future TheBornIdentity, but after 2-3 days of seeing that error it’s gone away by itself! (before I could try it, wife has had the car all day).