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.