Owners of leased cars without owner credentials cannot add third-party apps

[rawmean]

It is quite usual in EU/UK for people not to have access to owner credentials when they lease a car. This makes it impossible for them to add a 3rd-party app. They get a message like this from Tesla app (translated): "You are not authorized to share this vehicle. Contact the owner of the vehicle to grant third-party access."

Specifically, this happens after the 3rd-party app launches Tesla app to have it install the public key associated with the app on the car.

Is this going to change?

[jbanyer]

I can confirm the same restriction applies to a DRIVER (not OWNER) account for an Australian vehicle.

I hope this will be changed. A person with DRIVER access is able to perform most (all?) commands using the Tesla app, so it makes sense to me that they can also perform commands via a third-party app.

[rawmean]

I hope this will be changed. A person with DRIVER access is able to perform most (all?) commands using the Tesla app, so it makes sense to me that they can also perform commands via a third-party app.

Especially since a Driver can send commands to the car using the Tesla app.

[vbarrier]

How can someone have an owner access from Tesla for Business management website?

From my T4B account I can only assign drivers access... And my T4B admin account isn't not even an owner...

That said, It seems that any car linked to a T4B account can't use third-party apps (commands)

[jbanyer]

Any update here? It appears there is no solution for fleet vehicles (tesla for business), ie there is no way to install a virtual key on those vehicles.

[itsMeDavidV]

So for clarification, you're saying that anyone with a leased vehicle currently can't enroll a 3rd party public key?

[rawmean]

So for clarification, you're saying that anyone with a leased vehicle currently can't enroll a 3rd party public key?

Depends on the car owner/dealer. In Europe more dealers that lease the car, do not give the Owner Credentials for people who lease the car. So, this because a problem if the person who leases a car wants to use a 3rd party app.

[jbanyer]

We received this statement from Tesla (fleetapisupport@tesla.com) which suggests that a fix is coming for this:

The ability for lessees/drivers to grant permissions to third party applications and services will be available with an upcoming Tesla App update. Once released the driver will be able to confirm permission sharing using their Tesla vehicle touchscreen and keycard.

[markglh]

Has anyone received the app update yet or know of an ETA? Kinda blocked from charging using intelligent tariffs at cheap rates until this is fixed.

[dapper27]

Appears that app version 4.29.5 (iOS) has fixed this. I've just downloaded it but not actually gone through the whole process yet. After trying to add a virtual key it says you need to use your keycard so presumably need to be in the car.

[markglh]

I can confirm this works on ios now. Still broken on android though

[fmvdb]

What would be needed to make it work on android phones?

[jbanyer]

I can also confirm it works on iOS and not yet on Android. Perhaps this ticket could be re-opened until Android is working.

[fmvdb]

Today I noticed a new version of the Tesla app on android. This new version fixed this! You need to be in the car with your keycard and confirm the access on the screen of the Tesla.

[Hejmn]

is anyone having issues with the actual in car steps? We are experiencing when the keycard is placed on the center console as prompted to by app, clicking approve on the screen, nothing happens. No success message on the Tesla screen, or anyting in the Tesla App. IOS.

[feyazbek]

Hello. I'm not sure if i did the right thing or not. Here is what I have: 1- Model 3 Not leasing. it is working fine with the command API "Tesla Vehicule Command Proxy" 2- model Y 2023 leasing: does not work with the "Tesla Vehicule Commad Proxy" but works with the REST-API. 3- model X 2023 leasing: does not work with the "Tesla Vehicule Commad Proxy" but works with the REST-API.

Is that the way it is supposed to work or am I missing some setting so I can get the "Tesla Vehicule Command Proxy" to work?

[stevenlenders]

I just followed the procedure after my tesla app on my android was updated to 29.5 and initially I got the same error, but then used the button to do it with the key card and it worked. Tested from my teslafi account.

[Underground56]

I want to use Teslemetry with a leased Model Y. I was able to setup the access for Teslemetry, both in the car an also in the Tesla App Teslemetry is configured and listed as accessible. However, in the Teslemetry console, the status is still Access Type:DRIVER Command Sign:REQUIRED

Does anyone know how to solve this?

[phulstaert]

Model Y - Leased Car Android app version 4.33.5-2673 Car software: 2024.20.1

Not able to add public key

[ViNYLeq]

Model Y - Leased Car Android app version 4.33.5-2673 Car software: 2024.20.1

Not able to add public key

Were you able to fix this issue? I have same situation.

I will answer myself. I created developer account under other email address, then operation went smooth - don't use same tesla account for driver and developer access.

[stevenlenders]

Yes, with the new app version, you follow the process in the car. At a certain moment you need to present your key card to proceed.

On 16 jul 2024 at 01:28, ViNYLeq @.***> wrote:

Model Y - Leased Car Android app version 4.33.5-2673 Car software: 2024.20.1

Not able to add public key

Were you able to fix this issue? I have same situation.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

[ViNYLeq]

This is not required, I have finished my config late night without a need to go and use the card.