TeslaMate iOS App Setup Guide — Mytess Documentation
Get started with Mytess, the best TeslaMate iOS app, in three simple steps. This guide walks you through deploying the API service, connecting the app, and viewing your Tesla data.
Step 1 — Deploy TeslaMateAPI
Deploy the mytesla/teslamateapi service alongside your TeslaMate instance using Docker Compose. If you are starting from scratch, use our one-line install script: curl -fsSL https://mytess.net/scripts/mytess-install.sh | bash. This automatically sets up TeslaMate, the API service, PostgreSQL, Grafana, and Mosquitto MQTT broker. If you already have TeslaMate running, add the teslamateapi service to your existing docker-compose.yml and run docker compose up -d.
Step 2 — Configure the Mytess iOS App
Download Mytess from the App Store. Open the app and go to Settings. Enter your TeslaMateAPI address (e.g. http://your-server-ip:8080) and API token. Tap Test Connection to verify. If your server is behind a Cloudflare Tunnel or reverse proxy, enter the public HTTPS URL. You can also enable Basic Auth or use Cloudflare Service Auth (CF-Access-Client-Id / CF-Access-Client-Secret headers) for extra security.
Step 3 — View Your Tesla Data
Once connected, Mytess displays your Tesla's real-time status, battery health, trip history, charging costs, and statistics. Enable push notifications in Settings to receive alerts for charge complete, parking overtime, and more. A one-time PRO upgrade ($9.9) unlocks all premium features including battery degradation tracking, drive insights, advanced statistics, and Live Activity on the Dynamic Island.
Need Help?
Visit the FAQ page for common issues, or join our Telegram group for community support. You can also email us at hi@mytesla.cc.
TeslaMate FAQ - Common Questions & Troubleshooting
How can I get help?
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.
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. This triggers TeslaMate to re-push the latest data to MQTT.
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.
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. Source code: https://github.com/yekk-me/teslamate/
FAQ
Questions fréquentes sur la maintenance et le dépannage de TeslaMate