TeslaFi

Best Self-hosted Alternatives to TeslaFi

A curated collection of the 2 best self hosted alternatives to TeslaFi.

TeslaFi is a SaaS vehicle data logger and analytics platform for Tesla vehicles that connects to a user’s Tesla account/API to collect driving, charging, location, and efficiency data. It provides dashboards, historical reports, alerts, trip logging, and data export tools.

Alternatives List

#1
TeslaMate

TeslaMate

Open-source Tesla telemetry logger that records driving, charging and location data to PostgreSQL and provides Grafana dashboards plus MQTT integration.

TeslaMate screenshot

TeslaMate is an open-source application that records and analyses telemetry from Tesla vehicles. It captures high-precision drive, charge and location data, stores it in a PostgreSQL database and provides dashboards and integrations for further analysis and automation.

Key Features

  • Elixir-based backend with a Phoenix web interface and BEAM runtime for concurrent, fault-tolerant data collection.
  • Stores all vehicle telemetry in PostgreSQL for durable, queryable storage and long-term analysis.
  • Pre-built Grafana dashboards and a custom Grafana image for visualizing drives, charges, battery health and efficiency.
  • Publishes vehicle data to a local MQTT broker for easy integration with Home Assistant, Node-RED and other automation tools.
  • Docker and Docker Compose deployment with additional installation options (NixOS, manual Debian/Ubuntu) and environment-variable configuration.
  • Data import tools for migrating historical data from services like TeslaFi and community scrapers.
  • Features to minimize car wake-ups (reducing vampire drain), geo-fencing/custom locations, multi-vehicle support and charging cost tracking.

Use Cases

  • Personal vehicle analytics: track trips, charging sessions, battery health and energy efficiency over time.
  • Home automation / integrations: feed live telemetry into Home Assistant or Node-RED via MQTT for automations and notifications.
  • Fleet or multi-vehicle monitoring: aggregate and compare driving and charging metrics across multiple vehicles on the same account.

Limitations and Considerations

  • Relies on Tesla's owner/fleet APIs: changes to Tesla's APIs or authentication may break data collection until the project adapts.
  • Some vehicle or MCU configurations require special handling; certain hardware upgrades (e.g., MCU2) have recommended image tags to improve sleep behaviour.
  • Upgrades and major PostgreSQL migrations have produced occasional migration issues for some users; careful backup and testing are recommended before major upgrades.

TeslaMate provides a focused toolset for collecting, analysing and integrating Tesla telemetry with home automation and dashboarding systems. It is designed for reliability and extensibility and is commonly deployed via Docker or native system packages for long-term vehicle analytics.

7.7kstars
904forks
View Details
#2
Fitbit Fetch Script and InfluxDB Grafana Integration

Fitbit Fetch Script and InfluxDB Grafana Integration

Python service that pulls Fitbit health metrics via the Fitbit Web API, stores them in InfluxDB, and provides Grafana dashboards for long-term trend visualization.

A Python-based data collection service that retrieves personal health and activity metrics from the Fitbit Web API, writes them into a local InfluxDB time-series database, and visualizes the results in Grafana. It is designed for ongoing automatic syncing as well as historical backfilling to build long-term health trends.

Key Features

  • Automatic data collection from the Fitbit API with OAuth 2.0 token refresh
  • Stores metrics in InfluxDB for time-series analysis (best supported on InfluxDB 1.11)
  • Grafana dashboard support, including heatmaps and long-term trend panels
  • Collects a broad set of metrics such as heart rate (including intraday), steps, sleep, SpO2, HRV, breathing rate, activity minutes, and device battery
  • Historical backfilling mode designed to respect Fitbit rate limits and handle 429 responses
  • Docker Compose stack for running the fetcher, InfluxDB, and Grafana together

Use Cases

  • Personal health and fitness dashboard with long-term trends and daily summaries
  • Homelab time-series tracking of wearable metrics in InfluxDB with Grafana
  • Historical analysis by backfilling months/years of Fitbit data for reporting

Limitations and Considerations

  • Requires creating a Fitbit developer application and configuring OAuth tokens
  • InfluxDB 2.x support is described as limited and may produce a less detailed dashboard; InfluxDB 1.11 is strongly recommended
  • InfluxDB 3 OSS has query-time limitations that can make long-term visualization harder

It works well for users who want ownership of their Fitbit-derived metrics in their own database and prefer Grafana for visualization. The included schema and dashboards make it practical to deploy as a repeatable, automated pipeline.

828stars
66forks
View Details

Why choose an open source alternative?

  • •Data ownership: Keep your data on your own servers
  • •No vendor lock-in: Freedom to switch or modify at any time
  • •Cost savings: Reduce or eliminate subscription fees
  • •Transparency: Audit the code and know exactly what's running