If you're a fan of the very excellent TeslaMate and use it with Home Assistant, then this project is for you!

The TeslaMate + Home Assistant integration documentation shows a very long, manual configuration of each of the entities that TeslaMate sends messages for. While this works quite well (I used it for years) it has some shortcomings, the biggest of which is that they aren't all collected under a single Home Assistant Device. Unfortunately, devices cannot be created using purely manual end-user configuration, they can only be added with MQTT Discovery or a dedicated integration.

This application replaces most, if not all, of the documented TeslaMate + Home Assistant integration. In a single command, it synthesizes and publishes the MQTT Discovery configuration for commonly used entities converted to desired units and a device_tracker with precise coordinates that can also determine if the car is home (any geofence with "Home" in it).

The application assumes that you have a healthy TeslaMate installation sending messages to a Mosquitto MQTT broker and that Home Assistant can see those messages. The only other requirement is to have an account that can read messages from the /teslamate/# topic tree and send messages to the /homeassistant/# topic tree. This is often done by configuring /share/mosquitto/accesscontrollist as in the following example:

user homeassistant
topic readwrite homeassistant/#
topic read teslamate/#
user teslamate
topic write teslamate/#
user teslamate-discovery
topic write homeassistant/#
topic read teslamate/#

A multi-architecture container image for Linux amd64 and arm64 is published to the GitHub Container Registry:

ghcr.io/nebhale/teslamate-discovery

Use a version tag for repeatable deployments:

$ docker run --rm ghcr.io/nebhale/teslamate-discovery:2.6.0 \
 --mqtt-scheme tcp \
 --mqtt-host <HOST> \
 --mqtt-port 1883 \
 --mqtt-username <USERNAME> \
 --mqtt-password <PASSWORD> \
 --units-distance metric \
 --units-pressure metric

The application publishes retained MQTT discovery messages, so the container only needs to run again when TeslaMate vehicles or discovery settings change.

For Docker Compose installations, the same settings can be provided with environment variables:

services:
 teslamate-discovery:
 image: ghcr.io/nebhale/teslamate-discovery:2.6.0
 restart: "no"
 environment:
 MQTT_SCHEME: tcp
 MQTT_HOST: <HOST>
 MQTT_PORT: "1883"
 MQTT_USERNAME: <USERNAME>
 MQTT_PASSWORD: <PASSWORD>
 HA_DISCOVERY_PREFIX: homeassistant
 TM_PREFIX: teslamate
 UNITS_DISTANCE: metric
 UNITS_PRESSURE: metric

When using the Home Assistant Mosquitto add-on on a local network, --mqtt-scheme tcp and --mqtt-port 1883 are typically required because the CLI defaults to SSL on port 8883.

To install the application, navigate to the Releases page for the project and download the appropriate Asset for the platform you'll be running on (e.g. teslamate-discovery_2.0.2_Darwin_all.tar.gz for macOS). Unzip the package and within it you'll find the teslamate-discovery binary that you'll run.

Common usage might look like:

$ teslamate-discovery \
 --mqtt-host <HOST> \
 --mqtt-username <USERNAME> \
 --mqtt-password <PASSWORD>

Usage:
 teslamate-discovery [flags]
Flags:
 --ha-discovery-prefix string home assistant discovery message prefix (default "homeassistant")
 --help help for teslamate-discovery
 -h, --mqtt-host string mqtt broker host (default "127.0.0.1")
 -P, --mqtt-password string mqtt broker password
 -p, --mqtt-port int mqtt broker port (default 8883)
 -s, --mqtt-scheme string mqtt broker scheme (default "ssl")
 -u, --mqtt-username string mqtt broker username
 --range-type string range type ["estimated", "ideal", "rated"] (default "rated")
 --tm-prefix string teslamate message prefix (default "teslamate")
 --units-distance string distance units ["imperial", "metric"] (default "imperial")
 --units-pressure string pressure units ["imperial", "metric"] (default "imperial")
 -v, --version version for teslamate-discovery

Apache License v2.0: see LICENSE for details.