Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/tobiasehlert/teslamateapi
TeslaMateApi is a RESTful API to get data collected by self-hosted data logger TeslaMate in JSON
https://github.com/tobiasehlert/teslamateapi
api mqtt restful-api self-hosted tesla teslamate
Last synced: 24 days ago
JSON representation
TeslaMateApi is a RESTful API to get data collected by self-hosted data logger TeslaMate in JSON
- Host: GitHub
- URL: https://github.com/tobiasehlert/teslamateapi
- Owner: tobiasehlert
- License: mit
- Created: 2021-02-09T07:45:54.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2024-09-18T02:26:15.000Z (about 2 months ago)
- Last Synced: 2024-09-29T08:41:01.913Z (about 1 month ago)
- Topics: api, mqtt, restful-api, self-hosted, tesla, teslamate
- Language: Go
- Homepage:
- Size: 443 KB
- Stars: 91
- Watchers: 5
- Forks: 21
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
# TeslaMateApi
[](https://github.com/tobiasehlert/teslamateapi/actions/workflows/build.yml)
[](https://github.com/tobiasehlert/teslamateapi/blob/main/go.mod)
[](https://github.com/tobiasehlert/teslamateapi/releases)
[](https://hub.docker.com/r/tobiasehlert/teslamateapi)
[](https://github.com/tobiasehlert/teslamateapi/blob/main/LICENSE)
[](https://hub.docker.com/r/tobiasehlert/teslamateapi)
TeslaMateApi is a RESTful API to get data collected by self-hosted data logger **[TeslaMate](https://github.com/teslamate-org/teslamate)** in JSON.
- Written in **[Golang](https://golang.org/)**
- Data is collected from TeslaMate **Postgres** database and local **MQTT** Broker
- Endpoints return data in JSON format
- Send commands to your Tesla through the TeslaMateApi
### Table of Contents
- [How to use](#how-to-use)
- [Docker-compose](#docker-compose)
- [Environment variables](#environment-variables)
- [API documentation](#api-documentation)
- [Available endpoints](#available-endpoints)
- [Authentication](#authentication)
- [Commands](#commands)
- [Security information](#security-information)
- [Credits](#credits)
## How to use
You can either use it in a Docker container or go download the code and deploy it yourself on any server.
### Docker-compose
If you run the simple Docker deployment of TeslaMate, then adding this will do the trick. You'll have TeslaMateApi exposed at port 8080 locally then.
```yaml
services:
teslamateapi:
image: tobiasehlert/teslamateapi:latest
restart: always
depends_on:
- database
environment:
- ENCRYPTION_KEY=MySuperSecretEncryptionKey
- DATABASE_USER=teslamate
- DATABASE_PASS=secret
- DATABASE_NAME=teslamate
- DATABASE_HOST=database
- MQTT_HOST=mosquitto
- TZ=Europe/Berlin
ports:
- 8080:8080
```
If you are using TeslaMate Traefik setup in Docker with environment variables file (.env), then you can simply add this section to the `services:` section of the `docker-compose.yml` file:
```yaml
services:
teslamateapi:
image: tobiasehlert/teslamateapi:latest
restart: always
depends_on:
- database
environment:
- ENCRYPTION_KEY=${TM_ENCRYPTION_KEY}
- DATABASE_USER=${TM_DB_USER}
- DATABASE_PASS=${TM_DB_PASS}
- DATABASE_NAME=${TM_DB_NAME}
- DATABASE_HOST=database
- MQTT_HOST=mosquitto
- TZ=${TM_TZ}
labels:
- "traefik.enable=true"
- "traefik.port=8080"
- "traefik.http.middlewares.redirect.redirectscheme.scheme=https"
- "traefik.http.middlewares.teslamateapi-auth.basicauth.realm=teslamateapi"
- "traefik.http.middlewares.teslamateapi-auth.basicauth.usersfile=/auth/.htpasswd"
- "traefik.http.routers.teslamateapi-insecure.rule=Host(`${FQDN_TM}`)"
- "traefik.http.routers.teslamateapi-insecure.middlewares=redirect"
- "traefik.http.routers.teslamateapi.rule=Host(`${FQDN_TM}`) && (Path(`/api`) || PathPrefix(`/api/`))"
- "traefik.http.routers.teslamateapi.entrypoints=websecure"
- "traefik.http.routers.teslamateapi.middlewares=teslamateapi-auth"
- "traefik.http.routers.teslamateapi.tls.certresolver=tmhttpchallenge"
```
In this case, the TeslaMateApi would be accessible at teslamate.example.com/api/
### Environment variables
Basically the same environment variables for the database, mqqt and timezone need to be set for TeslaMateApi as you have for TeslaMate.
**Required** environment variables (even if there are some default values available)
| Variable | Type | Default |
| ------------------ | ------ | --------------- |
| **DATABASE_USER** | string | _teslamate_ |
| **DATABASE_PASS** | string | _secret_ |
| **DATABASE_NAME** | string | _teslamate_ |
| **DATABASE_HOST** | string | _database_ |
| **ENCRYPTION_KEY** | string | |
| **MQTT_HOST** | string | _mosquitto_ |
| **TZ** | string | _Europe/Berlin_ |
**Optional** environment variables
| Variable | Type | Default |
| --------------------- | ------- | ----------------------------- |
| **TESLAMATE_SSL** | boolean | _false_ |
| **TESLAMATE_HOST** | string | _teslamate_ |
| **TESLAMATE_PORT** | string | _4000_ |
| **API_TOKEN** | string | |
| **API_TOKEN_DISABLE** | string | _false_ |
| **DATABASE_PORT** | integer | _5432_ |
| **DATABASE_TIMEOUT** | integer | _60000_ |
| **DATABASE_SSL** | boolean | _true_ |
| **DEBUG_MODE** | boolean | _false_ |
| **DISABLE_MQTT** | boolean | _false_ |
| **MQTT_TLS** | boolean | _false_ |
| **MQTT_PORT** | integer | _1883 (if TLS is true: 8883)_ |
| **MQTT_USERNAME** | string | |
| **MQTT_PASSWORD** | string | |
| **MQTT_NAMESPACE** | string | |
| **MQTT_CLIENTID** | string | _4 char random string_ |
**Commands** environment variables
| Variable | Type | Default |
| --------------------------- | ------- | ----------------- |
| **ENABLE_COMMANDS** | boolean | _false_ |
| **COMMANDS_ALL** | boolean | _false_ |
| **COMMANDS_ALLOWLIST** | string | _allow_list.json_ |
| **COMMANDS_LOGGING** | boolean | _false_ |
| **COMMANDS_WAKE** | boolean | _false_ |
| **COMMANDS_ALERT** | boolean | _false_ |
| **COMMANDS_REMOTESTART** | boolean | _false_ |
| **COMMANDS_HOMELINK** | boolean | _false_ |
| **COMMANDS_SPEEDLIMIT** | boolean | _false_ |
| **COMMANDS_VALET** | boolean | _false_ |
| **COMMANDS_SENTRYMODE** | boolean | _false_ |
| **COMMANDS_DOORS** | boolean | _false_ |
| **COMMANDS_TRUNK** | boolean | _false_ |
| **COMMANDS_WINDOWS** | boolean | _false_ |
| **COMMANDS_SUNROOF** | boolean | _false_ |
| **COMMANDS_CHARGING** | boolean | _false_ |
| **COMMANDS_CLIMATE** | boolean | _false_ |
| **COMMANDS_MEDIA** | boolean | _false_ |
| **COMMANDS_SHARING** | boolean | _false_ |
| **COMMANDS_SOFTWAREUPDATE** | boolean | _false_ |
| **COMMANDS_UNKNOWN** | boolean | _false_ |
## API documentation
More detailed documentation of every endpoint will come..
### Available endpoints
- GET `/api`
- GET `/api/v1`
- GET `/api/v1/cars`
- GET `/api/v1/cars/:CarID`
- GET `/api/v1/cars/:CarID/charges`
- GET `/api/v1/cars/:CarID/charges/:ChargeID`
- GET `/api/v1/cars/:CarID/command`
- POST `/api/v1/cars/:CarID/command/:Command`
- GET `/api/v1/cars/:CarID/drives`
- GET `/api/v1/cars/:CarID/drives/:DriveID`
- PUT `/api/v1/cars/:CarID/logging/:Command`
- GET `/api/v1/cars/:CarID/logging`
- GET `/api/v1/cars/:CarID/status`
- GET `/api/v1/cars/:CarID/updates`
- POST `/api/v1/cars/:CarID/wake_up`
- GET `/api/v1/globalsettings`
- GET `/api/healthz`
- GET `/api/ping`
- GET `/api/readyz`
### Authentication
If you want to use command or logging endpoints such as `/api/v1/cars/:CarID/command/:Command`, `/api/v1/cars/:CarID/wake_up`, or `/api/v1/cars/:CarID/logging/:Command` you need to add authentication to your request.
You need to specify a token yourself (called **API_TOKEN**) in the environment variables file, to set it. The token has the requirement to be a minimum of 32 characters long.
There are two options available for authentication to be done.
1. Adding extra header `Authorization: Bearer ` to your request. (recommended option)
2. Adding URI parameter `?token=` to the endpoint you try to reach. (not a good option)
\* _Note: If you use the second option and your logs get compromised, your token will be leaked._
### Commands
Commands are not enabled by default.
You need to enable them in your environment variables (with `ENABLE_COMMANDS=true`) and you need to specify which commands you want to use as well.
There are 3 ways of using Commands:
1. Specific groups of commands can be enabled for example `COMMANDS_ALERT=true` will enable the [alert](https://tesla-api.timdorr.com/vehicle/commands/alerts) commands group.
2. If you need a granular set of commands enabled `COMMANDS_ALLOWLIST=/path/to/allow_list.json` can be used to specify a [JSON formatted list of commands](./example/allow_list.json) to enable.
3. The most coarse option `COMMANDS_ALL=true` will enable all commands (specific groups and allow_list will be ignored).
\* _Note: if `COMMANDS_ALL` or any specific group of commands has been enabled `COMMANDS_ALLOWLIST` is ignored._
A list of possible commands can be found under [environment variables](#environment-variables).
Regarding what fields you need to provide in the commands, we will referr to the [timdorr/tesla-api](https://tesla-api.timdorr.com/vehicle/commands) documentation.
## Security information
There is **no** possibility to get access to your Tesla account tokens by this API and we'll keep it this way!
The data that is accessible is data like the cars, charges, drives, current status, updates and global settings.
Also, apply some authentication on your webserver in front of the container, so your data is not unprotected and too exposed. In the example above, we use the same .htpasswd file as used by TeslaMate.
If you have applied a level of authentication in front of the container `API_TOKEN_DISABLE=true` will allow commands without requiring the header or uri token value. But even then it's always rekommended to use an apikey.
## Credits
- Authors: Tobias Lindberg – [List of contributors](https://github.com/tobiasehlert/teslamateapi/graphs/contributors)
- Distributed under MIT License