Mytess is a TeslaMate iOS app built for Tesla owners who use TeslaMate. It connects to your TeslaMate API and provides a beautiful data visualization interface to view your Tesla's status, trips, charging info, and statistics anywhere. It's the best TeslaMate iOS client available.

What do I need to use Mytess TeslaMate iOS app?

You need: 1) An iPhone or iPad running iOS 18.0 or later; 2) A running TeslaMate instance; 3) The mytesla TeslaMate API service deployed. If you don't have TeslaMate yet, check our deployment guide on the website.

Does Mytess collect my Tesla vehicle data?

No. Mytess does not store any vehicle data on our servers. All Tesla data is fetched directly from your own TeslaMate API server, not through any third-party servers. Your privacy and data security are our top priority.

Is there a TeslaMate app for iPhone?

Yes! Mytess is the best TeslaMate iOS app available for iPhone and iPad. It provides a beautiful native iOS interface to view and analyze your TeslaMate data, including battery health, charging costs, trip history, and real-time notifications.

How can I track my Tesla battery degradation?

With Mytess and TeslaMate, you can track your Tesla's battery health and degradation over time. The app visualizes your battery capacity changes, charging cycles, and provides insights into your battery's condition.

How much does Mytess cost?

Mytess offers a one-time payment of $9.9 USD for lifetime access to all features. The free version includes core features like real-time status, battery health, trip records, and charging history.

What is mytesla/teslamateapi?

mytesla/teslamateapi is the API service that bridges your TeslaMate data with the Mytess app. It is based on tobiasehlert/teslamateapi (thanks to the original author) and is supported by the official myteslamate connect feature. It only reads data from your database and MQTT service, and will never modify any existing TeslaMate data structures. If notifications are enabled, it communicates with Apple APNs without transmitting any unique vehicle identifiers, ensuring your data privacy and security.

How to upgrade mytesla/teslamateapi?

To upgrade TeslaMateAPI to the latest version, run: curl -fsSL https://mytess.net/scripts/mytess-tool.sh | bash -s -- upgrade-api. Or manually: docker compose pull teslamateapi && docker compose up -d teslamateapi. The upgrade only pulls and restarts the teslamateapi service — your TeslaMate, database, and MQTT services will not be affected.

How to backup TeslaMate data?

It is strongly recommended to backup your TeslaMate database regularly. Run: curl -fsSL https://mytess.net/scripts/mytess-tool.sh | bash -s -- backup. Or manually: docker compose exec -T database pg_dump -U teslamate teslamate > teslamate_backup.bck. Store the backup file in a safe location (external drive, cloud storage, etc.).

How to restore TeslaMate data?

To restore from a backup file: 1) Stop TeslaMate to prevent write conflicts, 2) Drop and recreate the database schema with required extensions, 3) Restore data from the backup file, 4) Restart TeslaMate. Run: curl -fsSL https://mytess.net/scripts/mytess-tool.sh | bash -s -- restore your_backup_file.bck. WARNING: This is a destructive operation — all current data will be replaced with the backup data.

Mytess homepage shows no data on first use?

This is normal! Mytess gets data through the flow: TeslaMate → MQTT (Mosquitto) → TeslaMateAPI → Mytess App. If TeslaMate hasn't pushed any data yet (e.g., after a fresh install or restart), the homepage will appear empty. Solution: Restart all TeslaMate services with: docker compose restart.

How to collect diagnostic info for troubleshooting?

Run: curl -fsSL https://mytess.net/scripts/mytess-tool.sh | bash -s -- diagnose. The tool collects service status, resource usage, and TeslaMateAPI logs. No sensitive data (passwords, tokens) will be included in the report.

How can I get help with TeslaMate?

Join our Telegram group for the fastest support! You can also reach us via email at hi@mytesla.cc, our Discord community, or check the documentation at mytess.net/docs/faq.

What if the address names for charging, parking, and trip start/end points are inaccurate?

TeslaMate uses OpenStreetMap for reverse geocoding by default, which may not always provide accurate address names in some regions. Solution: Replace the TeslaMate image with mytess/teslamate, an enhanced version based on TeslaMate with improved reverse geocoding. Apply for a Google Maps API key with Geocoding API permission enabled, then configure the GOOGLE_MAPS_API_KEY environment variable in your docker-compose.yml. See the mytess/teslamate source code at https://github.com/yekk-me/teslamate/ for details.

Deploy TeslaMate & mytesla/teslamateapi - Setup Guide

Fresh Install: Full Docker Compose Stack

Deploy a complete TeslaMate stack from scratch using Docker Compose. Includes TeslaMate, mytesla/teslamateapi, PostgreSQL database, Grafana, and Mosquitto MQTT broker. Secrets (ENCRYPTION_KEY, DATABASE_PASS, API_TOKEN) are generated automatically. Run: docker compose up -d.

Existing TeslaMate: Add TeslaMateAPI (One-click script)

If you already have TeslaMate running, add the mytesla/teslamateapi service with one command: curl -fsSL https://mytess.net/scripts/add-teslamateapi.sh -o add-api.sh && bash add-api.sh. The script reads your existing config, generates an API token, and patches your docker-compose.yml automatically.

Existing TeslaMate: Add TeslaMateAPI (Manual / NAS)

Add a teslamateapi service block to your docker-compose.yml inside the services: section. Use image: mytesla/teslamateapi:latest. Set DATABASE_USER, DATABASE_PASS, DATABASE_NAME, DATABASE_HOST, ENCRYPTION_KEY, MQTT_HOST, and API_TOKEN environment variables to match your existing TeslaMate configuration. Then run: docker compose up -d teslamateapi.

Configure Mytess App

Open Mytess → Settings → Server Config. Enter the API address (http://your-server-ip:3030 or your public domain) and the API_TOKEN value. Tap Test Connection to verify, then select your vehicle.

Important: Use mytesla/teslamateapi image

Mytess requires the mytesla/teslamateapi image, NOT tobiasehlert/teslamateapi. The mytesla build includes custom logic for drive insights, driving analysis, push notifications, and geofence-based time-of-use billing that are not available in the standard image.