Search results

It was something like “Octopus wants access to charging data and ability to start a charge” with allow and deny options. I then got an email in German from Tesla confirming that I’d provided access to Octopus. I didn’t have to create the virtual key, and I can’t as it’s a leased vehicle...

I thought I’d see what it did without adding the virtual key. Did the test charge, created the schedule and I woke up to a fully charged car this morning. Doesn’t look like it needs the virtual key to make it work!

No idea I’m afraid. Very new to all this

Except my car is a company car, so I don’t own it and can’t add the octopus virtual key. See if Arval will let me do that tomorrow…

There appears to be a new enrolment process with Tesla asking to confirm the access that Octopus needs. Also asks to configure a virtual key for Octopus. I’m not at home so I didn’t complete it, but it was talking to the car successfully now.

I got a text confirming delivery as 18th January this afternoon. Just got to rush around getting a charger installed now!

Well… I now have a VIN, Reg Number and a delivery window of January 10th - 25th. Model Y Standard, in white with white interior. Looks like Arval unstuck it!

Thank you for this! I called Tesla this morning to discover I had the same issue, and also ordered through Arval. Arval have been suitably nudged now so hopefully will be sorted out in the next day or two.