ifttt-tesla

A simple golang based service to allow ifttt to talk to the tesla owner api

Build

$ git clone https://github.com/scottweston/ifttt-tesla.git
$ cd ifttt-tesla
$ docker build -t ifttt-tesla .

Configure

Create a config file:

$ mkdir -p ~/.config
$ cat <<EOM >~/.config/tesla.yml
client_id: "e4a9949fcfa04068f59abb5a658f2bac0a3428e4652315490b659d5ab3f35a9e"
client_secret: "c75f14bbadc8bee3a7594412c31416f8300256d7668ea7e6e7f06727bfb9d220"
username: "[email protected]"
password: "your_tesla_password"
auth_tokens:
  - some_random_auth_token
  - another_random_auth_tkn
EOM
$ chmod 600 ~/.config/tesla.yml

Be sure to put in your own Tesla login details and create more secure auth_token(s). The included client id and secret do currently work and are the only publicly available ones at the moment - they could get invalidated at any time at which point this service (and many others) would fail.

Run

$ docker run --name=ifttt-tesla --restart=always -p 127.0.0.1:3514:3514 -v ~/.config/tesla.yml:/tesla.yml -d ifttt-tesla

Reverse Proxy

Setting up a reverse proxy is outside the scope of this document however you should create a SSL'd reverse proxy http server to access this service. If you want a quick and easy way to do this with automatic LetsEncrypt SSL protection look into using caddy

Caddy example

Setup your FQDN and then create a Caddyfile like:

api.tesla.my.domain {
  proxy / localhost:3514
}

Caddy will then try and obtain and use LetsEncrypt certs for your service. As the only protection to calling the API is the AuthToken it is important that you at least SSL protect the service so that the AuthToken is not able to be packet captured in transit. Not SSLing your service opens it up to potential abuse. I have specifically not put in the ability to remote start a Tesla because even with SSL there is a non-zero chance of this API or IFTTT being exploited.

Setting up IFTTT

The following endpoints are supported:

• /honk/{vehicle}
• /unlock/{vehicle}
• /lock/{vehicle}
• /set_charge_limit/{vehicle}/{limit}
• /start_charge/{vehicle}
• /stop_charge/{vehicle}
• /start_hvac/{vehicle}
• /stop_hvac/{vehicle}
• /flash/{vehicle}
• /open_charge_port/{vehicle}

If you only own 1 vehicle then {vehicle} will be 0

Now create IFTTT applets for if *google_assistant* then *maker* that look like:

Obviously you'll need to replace api.tesla.my.domain and some_random_auth_token with your own values for your installation. Also take care using the + Ingredient button to add the NumberField into the URL, I've noticed it also adds in a space (that needs to be removed).

Hints

You can use pwgen 64 1 to quickly create random AuthTokens, you only need 1 AuthToken per 3rd party service. If you suspect a token to have been compromised you can simply remove/replace that AuthToken and not have to reconfigure any other 3rd party services. Whilst I wrote this service specifically for IFTTT it could easily be used to integrate Tesla control into other services with the ability to call out to remote webhooks.