Copyright Erkki Seppälä 2022-2023
..for Matrix and Slack. Licensed under the MIT license.
TeslaBot allows interfacing with your Tesla vehicle over Matrix or Slack. It provides functions such as turning climate control on or off, determining the location of the vehicle (with a list of pre-configured locations for labeling location or for limiting information), and adding timers for those functions.
First choose if you want to control the bot via Matrix or Slack. Can't do both with one bot this time.
Chose Matrix? Good! Then you need to create a new Matrix id (aka mxid)
in the homeserver of your choice. Once you have that, use that as the
configuration key matrix.mxid (see the example config.ini).
The homeserver also needs to be configured at this time. You will also
need to enter a password here.
On the first connect TeslaBot will create an access token and a device id and write that to the state file. After this point the password no longer needs to be available in the config file.
The bot supports end-to-end encryption. To make use of this you need to add the list of trusted mxids in the configuration. This is not very secure against active attacks where e.g. an attacker is able to introduce new devices to the device list, but it should be secure against passive attacks where an attacker gains access to the (encrypted) messages.
You also may want to add the bot device as a trusted device in your Matrix client of choice.
Contributions for a more secure way to do this are welcome, but ultimately it will be solved once matrix-nio supports cross-signing, making the normal operation of this function quite a lot less tedious.
Controlling your corporate fleet? First you need to create a new app for this in the Slack workspace.
The bot uses websockets, so no need to configure any inbound hooks, just any random box will do.
TODO: make these instructions a bit more complete
Invite the bot to the room in the configuration.
Set environment variables:
- ENVIRONMENT: if running on google cloud, use gcp
- CHANNEL: slack channel
- SLACK_ADMIN_CHANNEL_ID: Channel's id that's used for authentication
- CONTROL: slack
- EMAIL: tesla login email
- STORAGE: type of storage (local / firestore)
- GCP_PROJECT_ID: speaks for itself
- SLACK_APP_SECRET_ID: secret id for retrieving slack app key in google secret manager
- SLACK_API_SECRET_ID: secret id for retrieving slack api key in google secret manager
Firestore requires the bot to be run on gcp, because authentication is done automatically there.
On the first startup the bot needs given an authorization to the Tesla
API. This can happen by using the cli tool in
https://pypi.org/project/TeslaPy/ to generate cache.json for you and
then pointing tesla.credential_store in the configuration to that
file. Alternatively you can visit the URL the bot will tell you (in
the admin room if one is available, otherwise you need to fish it from
the logs), and once you have entered your Tesla credentials, you will
end up to a page with an error. But this is fine, at this point you
just copy the URL from your web browser and send the command
!authorize <paste URL here>
to the bot admin room and you're done
mkdir tesla-data
curl https://raw.githubusercontent.com/eras/TeslaBot/master/config.ini.example > tesla-data/config.ini
emacs tesla-data/config.ini # edit for your needs
# Use -ti first time to easily see if everything is alright; once it works, replace it with -d
# Also consider --restart always
docker run -ti --name teslabot -d -v $PWD/teslabot-data:/data ghcr.io/eras/teslabot:latest
You should not use latest but the correct version tag. The image currently weighs around 130MB, so it's not tiny, but not huge either.
You can build the Docker image yourself with:
git pull https://github.com/eras/TeslaBot
cd TeslaBot
docker build -t teslabot .
and then replace the ghcr.. in the docker run command with teslabot.
You can also use docker-compose up to build and start in one go. Review the very basic yaml file first.
# optional:
python3 -m venv teslabot
. teslabot/bin/activate
pip3 install wheel
sudo apt install -y libolm-dev libffi-dev
git clone https://github.com/eras/TeslaBot
pip3 install ./TeslaBot[matrix,slack]
curl https://raw.githubusercontent.com/eras/TeslaBot/master/config.ini.example > config.ini
emacs config.ini # edit for your needs
# Run and do the API authentication
python3 -m teslabot --config config.ini
You can use e.g. screen, tmux or systemd to arrange this process to run on the background.
Note that by default you need to prefix commands with !.
| command | description |
|---|---|
| help | Show the list of commands supported. |
| authorize | Start the authorization flow. Works only in admin room (though you could only have one and same for control and admin). |
| authorize url | Last phase of the authorization flow. |
| logout | Remove authorization tokens. |
| climate on [name] | Sets climate on. Needs vehicle name if you have more than one Tesla. |
| climate off [name] | Sets climate off. |
| ac on/off [name] | Same as !climate. |
| sauna on/off [name] | Sets max defrost on/off. |
| info [delta] [name] | Show information about the device, such as about location, climate and charging. "delta" shows only differences to the previous info. |
| at 06:00 command | At 06:00 (not before the current time) issue a command. Can be climate or info, maybe more in future. |
| at 600 command | Same |
| at 10m command | Schedule at now + 10 minutes |
| at 1h1m command | Schedule at now + 1 hour 1 minute |
| at tomorrow 02:00 command | Schedule at 02:00 tomorrow |
| at wednesday 02:00 command | Schedule at 02:00 this or next wednesday (not in the past) |
| at 06:00 every 10m command | Schedule at 06:00 and re-do every ten minutes |
| at 06:00 every 10m until 30m command | Schedule at 06:00 and re-do every ten minutes for 30 minutes |
| at 06:00 every 10m until 7:00 command | Schedule at 06:00 and re-do every ten minutes until 30m |
| at 06:00 every 10m until wed 7:00 command | Schedule at 06:00 and re-do every ten minutes until 30m on wednesday |
| atrm 42 | Cancels a timer |
| atrm 42 44 | Cancels two timers |
| atq | Lists timers |
| set location-detail detail | Defines how precisely the location is displayed. See !help. |
| set require-! false | After this commands no longer need the ! prefix to work. |
| location add lat,lon [near 200 m] [address] | Add a new named location. These are for the bot only, not related to Tesla navigation. You can replace "lat,lon" with "current [vehicle name]" |
| location rm location name | Remove a named location. |
| location ls | List location.s |
| charge start/stop | Start or stop charging. |
| charge port open/close | Open or close charging flap. |
| charge amps 10 | Set charging amperage (per phase). |
| charge limit 70 | Set charging limit in percents. |
| charge schedule 04:00 | Schedule charging to start at given time. This uses Tesla's scheduler, not the one in this bot. |
| charge schedule disable | Disable charging schedule. |
| heater seat n off/low/medium/high | Adjust seat heaters. Works only if AC is on. |
| heater steering off/high | Adjust steering wheel heater. Works only if AC is on. |
| command # comment | Run command; ignore # comment |
| # comment | Ignore message |