TeslaBleHttpProxy

TeslaBleHttpProxy is a program written in Go that receives HTTP requests and forwards them via Bluetooth to a Tesla vehicle. The program can, for example, be easily used together with evcc.

The program stores the received requests in a queue and processes them one by one. This ensures that only one Bluetooth connection to the vehicle is established at a time.

Table of Contents

• How to install
  • Docker compose
  • Build yourself
• Generate key for vehicle
• Setup EVCC
• API
  • Vehicle Commands
  • Vehicle Data

How to install

You can either compile and use the Go program yourself or install it in a Docker container. (detailed instruction)

Docker compose

Below you will find the necessary contents for your docker-compose.yml:

services:
  tesla-ble-http-proxy:
    image: wimaha/tesla-ble-http-proxy
    container_name: tesla-ble-http-proxy
    volumes:
      - ~/TeslaBleHttpProxy/key:/key
      - /var/run/dbus:/var/run/dbus
    restart: always
    privileged: true
    network_mode: host
    cap_add:
      - NET_ADMIN
      - SYS_ADMIN

Please remember to create an empty folder where the keys can be stored later. In this example, it is ~/TeslaBleHttpProxy/key.

Pull and start TeslaBleHttpProxy with docker compose up -d.

Build yourself

Download the code and save it in a folder named 'TeslaBleHttpProxy'. From there, you can easily compile the program.

go build .
./TeslaBleHttpProxy

Please remember to create an empty folder called key where the keys can be stored later.

Generate key for vehicle

(Here, the simple, automatic method is described. Besides the automatic method, you can also generate the keys manually.)

To generate the required keys browse to http://YOUR_IP:8080/dashboard. In the dashboard you will see that the keys are missing:

Please click on generate Keys and the keys will be automatically generated and saved.

After that please enter your VIN under Setup Vehicle. Before you proceed make sure your vehicle is awake! So you have to manually wake the vehicle before you send the key to the vehicle.

Finally the keys is send to the vehicle. You have to confirm by tapping your NFC card on center console.

You can now close the dashboard and use the proxy. 🙂

Setup EVCC

If you want to use the solely TeslaBleHttpProxy, you can use the following configuration in evcc (recommended):

vehicles:
  - name: tesla
    type: custom
    title: Your Tesla
    icon: car
    capacity: 60
    chargeenable:
      source: http
      uri: "http://IP:8080/api/1/vehicles/VIN/command/{{if .chargeenable}}charge_start{{else}}charge_stop{{end}}"
      method: POST
      body: ""
    maxcurrent: # set charger max current (A)
      source: http
      uri: http://IP:8080/api/1/vehicles/VIN/command/set_charging_amps
      method: POST
      body: '{"charging_amps": "{{.maxcurrent}}"}'
    wakeup: # vehicle wake up command
      source: http
      uri: http://IP:8080/api/1/vehicles/VIN/command/wake_up
      method: POST
      body: ""
    soc:
      source: http
      uri: http://IP:8080/api/1/vehicles/VIN/vehicle_data?endpoints=charge_state
      method: GET
      jq: .response.charge_state.battery_level
      timeout: 30s 
    limitsoc:
      source: http
      uri: http://IP:8080/api/1/vehicles/VIN/vehicle_data?endpoints=charge_state
      method: GET
      jq: .response.charge_state.charge_limit_soc
      timeout: 30s
    range:
      source: http
      uri: http://IP:8080/api/1/vehicles/VIN/vehicle_data?endpoints=charge_state
      method: GET
      jq: .response.charge_state.battery_range
      scale: 1.60934
      timeout: 30s

If you want to use this proxy only for commands, and not for vehicle data, you can use the following configuration. The vehicle data is then fetched via the Tesla API by evcc.

- name: model3
    type: template
    template: tesla
    title: Tesla
    icon: car
    commandProxy: http://YOUR_IP:8080
    accessToken: YOUR_ACCESS_TOKEN
    refreshToken: YOUR_REFRSH_TOKEN
    capacity: 60
    vin: YOUR_VIN

(Hint for multiple vehicle support: #40)

API

Vehicle Commands

The program uses the same interfaces as the Tesla Fleet API. Currently, the following requests are supported:

• wake_up
• charge_start
• charge_stop
• set_charging_amps
• set_charge_limit
• auto_conditioning_start
• auto_conditioning_stop
• charge_port_door_open
• charge_port_door_close
• flash_lights

Example Request

(All requests with method POST.)

Start charging: http://localhost:8080/api/1/vehicles/{VIN}/command/charge_start

Stop charging: http://localhost:8080/api/1/vehicles/{VIN}/command/charge_stop

Set charging amps to 5A: http://localhost:8080/api/1/vehicles/{VIN}/command/set_charging_amps with body {"charging_amps": "5"}

Vehicle Data

The vehicle data is fetched from the vehicle and returned in the response in the same format as the Fleet API. Since a ble connection has to be established to fetch the data, it takes a few seconds before the data is returned.

Example Request

(All requests with method GET.)

Get vehicle data: http://localhost:8080/api/1/vehicles/{VIN}/vehicle_data

Currently you will receive the following data:

• charge_state
• climate_state

If you want to receive specific data, you can add the endpoints to the request. For example:

http://localhost:8080/api/1/vehicles/{VIN}/vehicle_data?endpoints=charge_state

This is recommended if you want to receive data frequently, since it will reduce the time it takes to receive the data.