eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions
blumeops/docs/zk/teslamate.md
Erich Blume a45a78b478 Convert wiki-links to title-based format (#89) 
## Summary
- Add `doc-card-titles` mise task to enumerate all doc cards by title/id and detect duplicates
- Remove redundant aliases from zk cards where alias matched the id
- Rename `reference/storage/postgresql.md` title to "PostgreSQL Storage" to avoid duplicate with `reference/services/postgresql.md`
- Convert all 175 path-based wiki-links `[[reference/path|Title]]` to title-based `[[Title]]` format
- Add pre-commit hook to check for duplicate card titles on doc changes

## Deployment and Testing
- [x] Pre-commit hooks pass
- [x] `mise run doc-card-titles` shows no duplicates
- [ ] Verify wiki-links work correctly in Quartz build

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/89
2026-02-03 15:04:38 -08:00

3.3 KiB
Raw Blame History

id aliases tags
teslamate
tesla
blumeops

TeslaMate

TeslaMate is a self-hosted Tesla data logger running in Kubernetes (minikube on indri), collecting and visualizing vehicle data from the Tesla Owner API.

Service Details

What TeslaMate Collects

  • 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 available in Grafana under the "TeslaMate" folder at https://grafana.tail8d86e.ts.net:

  • 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 the TeslaMate PostgreSQL datasource (not Prometheus).

Useful Commands

# View logs
kubectl --context=minikube-indri -n teslamate logs -f deployment/teslamate

# Check pod status
kubectl --context=minikube-indri -n teslamate get pods

# Restart deployment
kubectl --context=minikube-indri -n teslamate rollout restart deployment/teslamate

# Sync from ArgoCD
argocd app sync teslamate

Credentials

1Password items (blumeops vault):

  • TeslaMate - contains db_password and api_enc_key fields

Kubernetes secrets:

  • teslamate-db (teslamate ns) - DATABASE_PASS for PostgreSQL connection
  • teslamate-encryption (teslamate ns) - ENCRYPTION_KEY for token encryption
  • blumeops-pg-teslamate (databases ns) - CloudNativePG managed role password
  • grafana-teslamate-datasource (monitoring ns) - Grafana datasource password

Backup

TeslaMate data is backed up via borgmatic:

  • PostgreSQL database teslamate included in borgmatic_postgresql_databases
  • Backed up alongside miniflux to sifaka NAS

Tesla API Authentication

TeslaMate uses Tesla's Owner API (not Fleet API) via OAuth:

  1. Access https://tesla.tail8d86e.ts.net
  2. Click "Sign in with Tesla"
  3. Complete OAuth flow in browser
  4. Tokens are encrypted with ENCRYPTION_KEY and stored in database
  5. TeslaMate automatically refreshes tokens as needed

Standalone OAuth tool: If you need to manually obtain tokens, there's a Rust-based helper:

Database Notes

  • TeslaMate requires PostgreSQL 17.3+ or 18.x
  • The teslamate user has superuser privileges (required for extension management during migrations)
  • Extensions used: cube, earthdistance (for geospatial calculations)

Related

Log

Thu Jan 23 2026

  • Initial deployment to Kubernetes
  • 18 Grafana dashboards imported from TeslaMate project
  • Upgraded CloudNativePG 1.25 -> 1.28 for major version upgrade support
  • Upgraded PostgreSQL 17.2 -> 18.1 (required for TeslaMate 2.2.0)
  • Tailscale Ingress at tesla.tail8d86e.ts.net
  • Backup configuration added to borgmatic