GridMind’s Tesla integration provides the deepest functionality of any integration — real-time battery control, solar monitoring, multi-vehicle management, and Wall Connector data. It uses the official Tesla Fleet API for all communication.

Before connecting to GridMind, you need:
Tesla Fleet API access requires creating a developer application at developer.tesla.com. This is a one-time setup that takes about 15 minutes.
https://app.gridmindpower.com/oauth/tesla/callback, allowed origin https://app.gridmindpower.comGridMind requires a public/private key pair for Tesla’s vehicle command security protocol. Generate keys using OpenSSL:
openssl ecparam -name prime256v1 -genkey -noout -out private_key.pem
openssl ec -in private_key.pem -pubout -out public_key.pem
cat public_key.pemCopy the contents of public_key.pem — you’ll register this with Tesla in the next step.
public_key.pempublic_key.pem) from Step 2| Capability | Available | Notes |
|---|---|---|
| Real-time solar output | ✓ | kW, live |
| Real-time battery SOC | ✓ | %, live |
| Real-time grid import/export | ✓ | kW, live |
| Set backup reserve | ✓ | 0–100% |
| Change operation mode | ✓ | Self-powered / Time-Based |
| Vehicle SOC | ✓ | Doesn’t wake vehicle |
| Vehicle charge start/stop | ✓ | Wakes vehicle |
| Set charge limit | ✓ | 0–100% |
| Wall Connector status | ✓ | No wake needed |
| Charge session history | ✓ | From Wall Connector logs |
Tesla Fleet API has strict rate limits that GridMind manages automatically:
GridMind uses smart polling intervals to stay well within limits:
403 EXCEEDED_LIMIT error: Your Tesla account has been temporarily rate-limited by Tesla. This typically recovers within 24 hours. GridMind implements a 1-hour local cooldown when this occurs to avoid repeated failures.
Vehicle not showing data: The vehicle may be asleep. Use the Wake button on the Vehicle page. GridMind won’t wake vehicles automatically to avoid unnecessary battery drain.
”Site not found” after Discover: Ensure your Tesla account is the primary account on the Powerwall (not a shared user). Gateway firmware may need to be up to date.
This banner means GridMind’s server-side connection to Tesla has been interrupted. Because GridMind monitors your system in the background 24/7 — even when your phone is off — it holds a Tesla OAuth token on your behalf on the server. If Tesla invalidates that token, there’s no way to recover silently: you need to re-authenticate to issue a fresh one.
Common causes:
What to do: Tap the banner and sign in with Tesla again. It takes about 30 seconds and doesn’t affect your settings, history, or automation rules.
This is a Tesla platform limitation, not a GridMind bug. Tesla can revoke third-party tokens at any time without notice. Apps that use the local Powerwall API (on your home network only) don’t have this issue because they don’t use Tesla’s cloud OAuth — but they also can’t monitor your system remotely or run automations while you’re away.