🔌 Companion firmware: IDTelemetry — the ESP32-S3 stick that collects the data and sends it here over MQTT.
Self-hosted telemetry & trip log for non-Tesla EVs. Collects data via IDTelemetry (ESP32/OBD2) over MQTT with AES-256-CBC encryption and via Home Assistant webhooks. Stores everything in InfluxDB + SQLite and ships with a built-in trip log (Triplog) — dashboard, logbook, journeys, charge tracker, geofencing, analysis and user management.
Note: This is a personal hobby project built for the data-obsessed self-hoster. It is not intended for commercial use and comes with no warranties or support guarantees.
Massive props to TeslaMate — I happily ran it for years and it spoiled me. Then an ID.7 joined the family, and reality hit:
- VW telemetry is essentially non-existent — no API, no public data feed, the official app is a black box.
- And how the hell do I track my charging costs automatically so I can hand a clean monthly report to my employer?
- And honestly: while VW is still busy figuring out a halfway-acceptable UI in their cars 🙃, I'd rather build my own.
So I built ID·Mate: same spirit as TeslaMate (visualise vehicle data, track trips, monitor battery health), but starting from CAN/OBD2 via an ESP32 stick instead of a vendor API — plus a Home Assistant webhook for wallbox energy/cost tracking.
ID·Mate is not a fork of TeslaMate and contains no code from it.
Live map with heading arrow, SoC, range, charge status and geofence pins.
Automatic trip detection from InfluxDB. Per-trip purpose, destination, reason, notes — with batch edit and CSV export.
Group multiple trips into journeys with mini-maps and GPX export.
Charts for trips, purposes, battery health and efficiency (temperature/speed correlation).
Wallbox sessions (15-min readings via Home Assistant) and external/DC charges. Tibber vs. flat-rate comparison.
Users, locations (with radius + custom icons), value rename/merge, GPX import, language toggle (DE/EN).
git clone https://github.com/TheInGoF/IDMate-dev.git
cd IDMate-dev
cp .env.example .env
nano .env # fill in your values (see table below)
docker-compose up -dThen open:
- Triplog — http://your-host:3004
- InfluxDB — http://your-host:3001
Important: Set
INFLUX_TOKENbefore the first start. Changing it later requires resetting the InfluxDB volume.
For custom volume paths (e.g. Synology NAS) copy docker-compose.yml to docker-compose.local.yml and adjust the volumes:
docker-compose -f docker-compose.local.yml up -d
Source: docs/diagrams/architecture.puml — re-render with plantuml -tsvg docs/diagrams/*.puml.
Source: docs/diagrams/infrastructure.puml
Source: docs/diagrams/charge-flow.puml
The MID meter (calibrated energy meter at the wallbox) is integrated into Home Assistant via Modbus/TCP. Home Assistant calculates 15-minute intervals and posts the readings to the Triplog Charge Tracker via REST webhook.
- Stacks > Add Stack > Web editor
- Name:
idmate - Paste the contents of docker-compose.yml into the editor.
- Optional: For custom volume paths (e.g. Synology NAS), replace named volumes with bind mounts (e.g.
influxdb-data:/var/lib/influxdb2→/volume1/docker/idmate/influxdb/data:/var/lib/influxdb2). - Environment variables > Advanced mode — paste the block below and adjust the values:
INFLUX_PORT=3001
INFLUX_USER=admin
INFLUX_PASS=change-me
INFLUX_ORG=home
INFLUX_BUCKET=can-scan
INFLUX_TOKEN=change-me-to-a-long-random-token
INFLUX_DEVICE=id7
TRIPLOG_PORT=3004
SECRET_KEY=
LANGUAGE=DE
MQTT_PORT=3005
MQTT_DATA_TOPIC=tele/+/data
MQTT_DOMAIN=localhost
MQTT_TLS=0
# generate with: openssl rand -hex 32 (must match ESP firmware)
MQTT_AES_KEY=
CHARGE_WEBHOOK_TOKEN=First start: Triplog has no users on first launch — open
http://your-host:3004/setupand the wizard will create the admin account (username, password, optional 2FA). No default credentials are shipped.
Use a cryptographically secure random number generator. Never ask an LLM (ChatGPT, Claude, Copilot, …) to "give me a random 32-byte key" — LLM output is probability-distributed, not random. The same prompt produces a small, predictable distribution of values that an attacker can enumerate offline. The convenience is not worth the silent loss of entropy.
Use these instead:
openssl rand -hex 32 # AES-256 key, SECRET_KEY
openssl rand -base64 32 # API/webhook tokens
python3 -c "import secrets; print(secrets.token_hex(32))"This applies to INFLUX_TOKEN, SECRET_KEY, MQTT_AES_KEY and CHARGE_WEBHOOK_TOKEN.
- For private image repos: add a ghcr.io registry under Registries with a GitHub PAT (
read:packages). - Deploy the stack.
All images are built via GitHub Actions and pushed to ghcr.io — no local
docker buildneeded, no bind mounts required, works with the Portainer web editor.
| Variable | Description | Default |
|---|---|---|
INFLUX_PORT |
InfluxDB external port | 3001 |
INFLUX_USER |
InfluxDB admin user | — |
INFLUX_PASS |
InfluxDB admin password | — |
INFLUX_ORG |
InfluxDB organisation | home |
INFLUX_BUCKET |
InfluxDB bucket | can-scan |
INFLUX_TOKEN |
InfluxDB API token | — |
INFLUX_DEVICE |
Device tag in InfluxDB | id7 |
TRIPLOG_PORT |
Triplog external port | 3004 |
SECRET_KEY |
Flask session secret (auto-generated + persisted if empty) | — |
LANGUAGE |
UI language (DE or EN) |
DE |
ENABLE_DEBUG |
Expose /debug, /scan-debug, /influx-delete routes |
1 |
CHARGE_WEBHOOK_TOKEN |
Charge tracker webhook token (optional) | (empty = no auth) |
MQTT_PORT |
Mosquitto external port | 3005 |
MQTT_DATA_TOPIC |
MQTT topic pattern for telemetry | tele/+/data |
MQTT_AES_KEY |
Hex-encoded 32-byte AES-256 key (must match ESP) | — |
MQTT_TLS |
Enable TLS to broker (0 or 1) |
0 |
MQTT_DOMAIN |
Hostname used in Mosquitto cert config | localhost |
Standalone Python service on port 3004 — not an official logbook, but a personal trip log:
- 🔐 Login/Auth — session-based authentication, admin role, user management, optional 2FA
- 🚗 Vehicle Dashboard — current status, SoC, range, map with heading arrow and geofence pins
- 🛣️ Automatic Trip Detection from InfluxDB (every 5 min), including delta decompression
- 📒 Trip Logbook — purposes, destinations, visit reasons, notes, batch assignment
- 🗺️ Journeys — group multiple trips, mini-map, GPX export
- 📊 Analysis — charts for trips, purposes, battery health, efficiency (temperature/speed correlation)
- 📍 Geofencing — saved locations with radius, automatic destination matching, custom icons
- ⚙️ Admin — rename/merge/delete values, edit locations, manage users, map style, GPX import
- 🌍 Reverse Geocoding via Nominatim (start/destination addresses)
- 📤 CSV Export — filterable by year/purpose
- 🗣️ i18n — German and English UI, switchable in settings
Tracks wallbox charges (15-min intervals via Home Assistant) and external charges (DC fast chargers, etc.):
- Webhook Receiver —
POST /api/charge/readingaccepts quarter-hour readings - Session Detection — grouping by vehicle + odometer
- Tibber vs. Flat Rate — comparison of dynamic electricity costs with annual flat rate
- CSV Import — historical data from Google Sheets (German number format)
- External Charges — manual entry of DC/third-party charges with separate session numbers
- Vehicle Management — plate, name, VIN
For automatic charge data collection every 15 minutes:
1. REST Command in configuration.yaml:
rest_command:
idmate_charge_reading:
url: "http://192.168.x.y:3004/api/charge/reading"
method: POST
headers:
Content-Type: application/json
Authorization: "Bearer {{ states('input_text.idmate_token') }}"
payload: >-
{
"timestamp": "{{ now().strftime('%Y-%m-%d %H:%M') }}",
"vehicle": "{{ states('input_select.wallbox_vehicle') }}",
"kwh": {{ states('sensor.wallbox_energy_15m') | float(0) }},
"meter_start": {{ states('sensor.wallbox_meter_start') | float(0) }},
"meter_end": {{ states('sensor.wallbox_meter_end') | float(0) }},
"tibber_price": {{ states('sensor.tibber_price') | float(0) }},
"tibber_grundgebuehr": {{ states('sensor.tibber_grundgebuehr_15m') | float(0) }},
"odometer": {{ states('sensor.vehicle_odometer') | float(0) }}
}2. Automation (every 15 minutes):
automation:
- alias: "ID·Mate send charge data"
trigger:
- platform: time_pattern
minutes: "/15"
condition:
- condition: numeric_state
entity_id: sensor.wallbox_energy_15m
above: 0
action:
- service: rest_command.idmate_charge_readingSensor entity IDs must be adapted to your HA installation. The
CHARGE_WEBHOOK_TOKENis optional — without a token, no auth is required (suitable for internal networks). For external access, set a token in.env:CHARGE_WEBHOOK_TOKEN=my-secret-token.
IDTelemetry (ESP32) publishes a binary v1 telegram to MQTT topic tele/<device>/data roughly every 10 s. The payload is AES-256-CBC encrypted (PKCS7 padding) with a per-message random IV:
[1 byte version=0x01][16 byte IV][AES-256-CBC ciphertext]
Plaintext layout (after decryption):
field_mask(u32, little-endian) — bitnset ⇒ fieldnis present in this telegram- packed field values in fixed order (lat/lon as int * 1e6, speed/power/voltage as scaled u16/i16, booleans encoded purely via
field_mask, …)
Triplog subscribes via paho-mqtt, decrypts each message with MQTT_AES_KEY, decodes the binary fields and writes them into InfluxDB as Line Protocol. Field names are kept short (e.g. s = speed, u = HV voltage, p = power, la/lo = GPS, bt = battery temp). Mapping to readable names happens in the Triplog UI.
The AES key is shared between the ESP firmware and Triplog (
MQTT_AES_KEY, hex-encoded 32 bytes). Messages with wrong keys are silently dropped.
Container images are published to ghcr.io/theingof/idmate with the following tag matrix:
| Tag | When to use | Stability |
|---|---|---|
1.2.3 |
Pin to an exact release | Most stable |
1.2 |
Auto-update patches within 1.2.x |
Stable |
1 |
Auto-update minors within 1.x |
Recommended for most |
latest |
Always newest main | Active development — read release notes before pulling |
Multi-arch: linux/amd64 and linux/arm64 (Synology DS920+, Raspberry Pi 4/5, Apple Silicon, …).
To update:
docker compose pull && docker compose up -dState lives in three named volumes: triplog-data (SQLite + uploads), influxdb-data (time-series), mosquitto-data (MQTT persistence). Back them up while the stack runs (SQLite is read-consistent during a single tar pass, InfluxDB writes are append-only):
mkdir -p backup && cd backup
for v in triplog-data influxdb-data influxdb-config mosquitto-data mosquitto-certs; do
docker run --rm -v idmate_${v}:/src -v "$PWD":/dst alpine \
tar czf /dst/${v}-$(date +%F).tar.gz -C /src .
doneRestore by stopping the stack, recreating empty volumes and untarring back into them:
docker compose down
for v in triplog-data influxdb-data influxdb-config mosquitto-data mosquitto-certs; do
docker volume create idmate_${v}
docker run --rm -v idmate_${v}:/dst -v "$PWD":/src alpine \
tar xzf /src/${v}-YYYY-MM-DD.tar.gz -C /dst
done
docker compose up -dThe volume prefix (
idmate_) is the Compose project name — adapt if your stack runs under a different name (docker volume lsto verify).
IDMate/
├── docker-compose.yml # Stack (named volumes, ghcr.io images)
├── .env.example # Credential template
├── .env # Actual credentials (gitignored)
├── docs/
│ ├── diagrams/ # PlantUML sources
│ └── screenshots/ # README screenshots (drop yours here)
├── mosquitto/ # MQTT broker (TLS)
└── triplog/ # Trip log service (Python/Flask)
├── Dockerfile
├── requirements.txt
├── app.py # Flask web UI + API + auth + CSV export
├── detector.py # Trip detection + delta decompression
├── geocoder.py # Reverse geocoding (Nominatim)
├── config.py # Configuration via environment variables
├── schema.sql # SQLite schema
├── static/ # Logo + assets
└── templates/ # Flask Jinja templates
This project was developed in a human-in-the-loop workflow with AI assistance. Architecture, code and configuration were created in dialogue — all decisions were made by the human.
GNU Affero General Public License v3.0 — see LICENSE
Donations are voluntary and solely support the project. They do not influence the prioritisation of bugs, feature requests or support enquiries.