Tesla Owner API doesn't allow sending vehicle commands anymore

[erwin1]

See https://developer.tesla.com/docs/fleet-api#2023-10-24-vehicle-data-update-on-firmware-versions-2023-38

Tesla now requires end-to-end authentication to send vehicle commands.

Possible solutions:

1. Refactor to use Fleet API instead of Owner API + setup and run tesla-http-proxy from https://github.com/teslamotors/vehicle-command to send commands
2. Use the BLE SDK from https://github.com/teslamotors/vehicle-command to send command directly to the vehicle.

[erwin1]

Tested option 1:

• setup a Tesla app following https://shankarkumarasamy.blog/2023/10/29/tesla-developer-api-guide-account-setup-app-creation-registration-and-third-party-authentication-configuration-part-1/
• created keypair and enrolled the public key in the vehicle
• setup the tesla-http-proxy
• refactored code to use localhost proxy instead of Owner API for commands

This works, but the Fleet API has VERY low rate limits: https://developer.tesla.com/docs/fleet-api#membership-levels
Only 5 charging commands per day, which is far too low for this use case.

[erwin1]

Tested option 2:

• using a RPi located close to the car (inside garage while car is outside seemed to work)
• following instructions from https://github.com/teslamotors/vehicle-command/blob/main/cmd/tesla-control/README.md

This works using the command line SDK. Next step is to integrate the commands in the homecontrol app instead of calling the Owner API to send vehicle commands.

[erwin1]

interesting feature request teslamotors/vehicle-command#52 as this would allow operation via BLE only (no need to use the REST API to get vehicle_data)

[dglaude]

I wanted to make sure you knew about https://github.com/wimaha/TeslaBleHttpProxy as an HTTP way to do BLE control.

Right now I try to make evcc work for me, but since I have an HomeWizard P1 reader, I might have all the hardware needed to switch to your project.