Never send support a secret
Do not post or message a Teslr token, Tessie token, Tesla credential, account linkage, VIN, plate, PIN, invitation link, exact location, or trip history. Teslr support will never ask for one.
Connect Tesla
- Start the Tesla connection from the Teslr home page.
- Approve the requested Tesla permissions.
- Save the one-time token as
TESLR_FLEET_TOKENonly in your AI assistant's secure environment settings. - On your phone, pair the Teslr virtual key for each vehicle you want to control.
- Refresh the Teslr skill and ask it to list your vehicles.
Disconnect Tesla from Teslr
- Move to a clearly private conversation with your AI assistant.
- Say “Disconnect my Tesla from Teslr.”
- Confirm after the assistant explains that the connection token will stop working immediately.
- Delete
TESLR_FLEET_TOKENfrom the assistant's environment settings. - Optionally remove Teslr from Tesla's third-party app access.
For Tessie compatibility, remove TESSIE_API_TOKEN from the assistant and revoke or rotate the token through Tessie. Teslr does not store Tessie tokens.
If a token may be exposed
Stop sending commands. Revoke the connection using the private steps above if possible, remove the environment variable, and remove Teslr from Tesla's third-party access or rotate the Tessie token. Reconnect only after the old credential is invalid.
Common setup messages
- Virtual key not paired: open the pairing link on the phone with the Tesla app and approve Teslr for that vehicle.
- Scope required: reconnect from teslr.club and approve the requested Tesla permission.
- Command service unavailable: wait and try later; do not repeatedly send a command whose outcome is uncertain.
- Rate limited: wait for the retry window rather than changing providers or repeating the request.
- Fair-use pause: wait for the returned retry window. Do not reconnect, change providers, or repeatedly retry to evade it.
- Command outcome uncertain: check the real vehicle state before any retry.
Contact
Contact @TeslrBot on X with a generic error code and approximate time only. Do not include vehicle identity, location, provider response data, credentials, or account linkage in a public post or direct message.