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 Pro is available through auto-renewing monthly, quarterly, and yearly subscriptions, or a lifetime unlock in the App Store. 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.

TeslaMate API Configuration — Mytess iOS App

This guide explains how to configure the Mytess TeslaMate iOS app to connect to your self-hosted TeslaMate API service. Supported authentication methods include AK/SK, Basic Auth, and Cloudflare Service Auth. Remote access is supported via Cloudflare Tunnel, Tailscale, or any HTTPS reverse proxy.

Step 1 — Obtain your API address and AK/SK credentials

After deploying mytesla/teslamateapi using Docker Compose, find your server IP and exposed port. The Mytess deployment guide commonly maps TeslaMateAPI to port 3030. Your API_ACCESS_KEY and API_SECRET_KEY are defined in your docker-compose environment or printed by the installer. They authenticate Mytess requests to TeslaMateAPI and are not Tesla account access or refresh tokens. Example API address: http://192.168.1.100:3030.

Step 2 — Configure the Mytess iOS app

Open the Mytess app on your iPhone or iPad. Navigate to Settings → API Configuration. Enter:

API Address: Your TeslaMateAPI URL (HTTP or HTTPS)
API Access Key and Secret Key: The API_ACCESS_KEY/API_SECRET_KEY pair configured for TeslaMateAPI

Tap Test Connection. A success message confirms the connection is working. Your Tesla data will start loading immediately.

Remote Access via Cloudflare Tunnel

To access TeslaMate outside your local network without port forwarding, use Cloudflare Tunnel. Create a tunnel in the Cloudflare Zero Trust dashboard pointing to your teslamateapi container (port 8080). Enter the public HTTPS tunnel URL in Mytess Settings. For additional security, create a Cloudflare Access Service Token and configure it in the app (CF-Access-Client-Id and CF-Access-Client-Secret).

Remote Access via Tailscale

Install Tailscale on your server and your iPhone. Join the same Tailnet. Use the Tailscale IP address of your server (e.g. http://100.x.x.x:8080) as the API address in Mytess. No port forwarding required. Works securely over any network.

Basic Authentication

If your reverse proxy (Nginx, Caddy, etc.) requires HTTP Basic Auth, enable it in Mytess Settings under Advanced. Enter your username and password. The app appends the Authorization header to all API requests.

Common Issues

Connection refused: Ensure the teslamateapi container is running (docker compose ps) and the port is not blocked by a firewall.
401 Unauthorized: Check that API_ACCESS_KEY and API_SECRET_KEY match what is configured in the app.
Homepage shows no data: Restart TeslaMate services with docker compose restart to trigger MQTT data push.
SSL certificate error: Ensure your reverse proxy uses a valid TLS certificate. Self-signed certs are not supported.

API-Konfiguration

Mytess mit Ihrem TeslaMate API-Dienst verbinden

1API-Adresse konfigurieren

Geben Sie die Adresse Ihres TeslaMate API-Dienstes ein, Format:

Intranethttp://192.168.1.x:3030

Öffentlichhttps://api.example.com

2Authentifizierungsmethode wählen

Keine Authentifizierung

Für Intranet-Umgebungen oder anderweitig geschützte APIs

AK/SK-AuthentifizierungEmpfohlen

Setze API_ACCESS_KEY und API_SECRET_KEY im API-Dienst und trage dasselbe Paar in Mytess ein. Sie authentifizieren Mytess-Anfragen an TeslaMateAPI.

API_ACCESS_KEY=AKxxxxxxxxxxxxxx
API_SECRET_KEY=SKxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Diese Schlüssel sind keine Tesla-Konto-Access/Refresh-Tokens. TeslaMate verwendet diese Tokens zur Fahrzeugautorisierung; Mytess nutzt AK/SK nur für den Zugriff auf TeslaMateAPI.

Basic-Authentifizierung

Benutzername/Passwort über Nginx oder anderen Reverse-Proxy konfigurieren

3Fernzugriff (optional)

Für externen Zugriff auf Ihre TeslaMate API:

Cloudflare Tunnel

Tailscale / WireGuard

frp / ngrok

Nginx + Let's Encrypt

Test Connection

Nach der Konfiguration klicken Sie auf 'Verbindung testen', um zu verifizieren.

Häufige Probleme

Verbindungszeitüberschreitung

Überprüfen Sie API-Adresse, Port und Firewall-Einstellungen

Authentifizierung fehlgeschlagen (401)

Überprüfen Sie Authentifizierungsmethode und Anmeldedaten

Zertifikatsproblem

iOS erfordert ein gültiges HTTPS-Zertifikat, Let's Encrypt empfohlen