This repo contains a Dockerfile to build and run the Tesla REST API Proxy. It requires a private key (linked to your app with public key published) and a TLS certificate and key. Please refer to the vehicle-command repository for more details.
The built container listens on port 443 and expects the following to be mounted:
| Mount | Description |
|---|---|
| /config/tls.crt | TLS certificate chain for HTTPS endpoint |
| /config/tls.key | TLS private key for HTTPS endpoint |
| /config/private.pem | Tesla app private key |
This container listens on all IPs and has no authentication of its own - you must use a reverse proxy with authentication to prevent abuse and your Tesla developer app being blocked.
This is for personal/proof-of-concept use and has not been extensively tested - you accept you use this at your own risk.
Tesla rate-limit the Fleet API to 50 requests per vehicle per day. This limits the number of calls that can be made to the API for use cases such as solar charging. In order to minimise the number of API requests, a patched version of the proxy to try BLE first before HTTPS is built when using Dockerfile.ble with your docker build command. The resultant container needs to be run with --network=host and --cap-add=NET_ADMIN in order to use the host's Bluetooth device.
- Tesla developer account (https://developer.tesla.com)
- Third-party application active in your Tesla developer account
- Docker
To use this as a docker container, you will have to build it with the included Dockerfile
if it's running properly you should get an OAuth client error when browsing to
http://IP_ADDRESS/api/1/randomEndpoint