Phase 2 of documentation restructuring. Creates docs/reference/ with: Services (16): - alloy, argocd, borgmatic, 1password, forgejo, grafana - jellyfin, kiwix, loki, miniflux, navidrome, postgresql - prometheus, teslamate, transmission, zot Infrastructure (3): - hosts - Device inventory - tailscale - ACLs, groups, tags - routing - DNS domains and port mappings Kubernetes (2): - cluster - Minikube specs - apps - ArgoCD application registry Storage (2): - sifaka - Synology NAS configuration - backups - Backup policy All cards use wiki-links for cross-referencing and include YAML frontmatter with title and tags for Quartz. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
| title | tags | ||
|---|---|---|---|
| TeslaMate |
|
TeslaMate
Self-hosted Tesla data logger collecting vehicle telemetry from the Tesla Owner API.
Quick Reference
| Property | Value |
|---|---|
| URL | https://tesla.ops.eblu.me |
| Tailscale URL | https://tesla.tail8d86e.ts.net |
| Namespace | teslamate |
| Image | teslamate/teslamate:2.2.0 |
| Database | postgresql |
Data Collected
- Battery level, state of charge, range estimates
- Charging sessions (location, energy, cost, duration)
- Drives (distance, efficiency, routes)
- Climate/HVAC usage
- Software update history
- Vampire drain analysis
- Vehicle states (asleep, driving, charging, online)
Grafana Dashboards
18 dashboards in the "TeslaMate" folder:
- Overview, Charges, Drives, Efficiency, States
- Battery Health, Vampire Drain, Statistics
- Charge Level, Locations, Trip, Mileage
- Drive Stats, Charging Stats, Projected Range
- Timeline, Updates, Visited
Dashboards use PostgreSQL datasource (not Prometheus).
Authentication
Uses Tesla Owner API via OAuth:
- Access https://tesla.ops.eblu.me
- Click "Sign in with Tesla"
- Tokens encrypted with ENCRYPTION_KEY
Credentials
1Password: TeslaMate item with db_password and api_enc_key
Related
- postgresql - Data storage
- grafana - Dashboards
- borgmatic - Database backup