Tesla Fleet Api

**Quick judgement** A powerful, feature-rich integration for Tesla’s official Fleet API, suitable for technically competent users or teams who control the vehicles being accessed. It offers broad control and telemetry coverage but requires non-trivial setup (OAuth, config, signing proxy) and carries real-world safety and privacy risks if exposed to untrusted prompts or users. **What it’s good for** - Automating common Tesla tasks: starting/stopping climate, setting temperatures, managing seat heaters/coolers, steering wheel heater, and preconditioning schedules. - Managing charging: starting/stopping charging and setting charge limits for one or multiple vehicles. - Reading detailed vehicle telemetry: battery/charge state, climate, drive state, location, locks, software, configuration, and GUI settings, with both human-readable and JSON output. - Fleet-style scenarios: listing multiple vehicles, refreshing cached vehicle lists, and applying commands per vehicle by name or VIN. - Handling Tesla OAuth and config: login/refresh, client credentials, redirect URIs, regional audience/base URLs, and domain registration for signed commands. **Key risks & limitations** - **Physical-world control & safety**: The skill can lock/unlock vehicles, start climate, adjust charging, and interact with vehicle security features. Misuse or incorrect prompts could have safety, security, or comfort implications. - **Location & privacy**: Access to GPS/location and other sensitive telemetry makes this high-risk if used in agents exposed to untrusted users or arbitrary natural-language instructions. - **Credential & token handling**: Requires careful management of client ID/secret, OAuth tokens, TLS material, and config.json/auth.json files. Compromised credentials could grant control over vehicles. - **Operational complexity**: Setup involves state directory management, OAuth configuration, region-specific endpoints, and a signing proxy for vehicle commands. This is not plug-and-play for non-technical users. - **Dependency on Tesla services**: Availability and behavior depend on Tesla’s Fleet API, auth endpoints, and their policies; breaking changes or downtime are outside the skill’s control. **Recommended scenarios** - Private, owner- or fleet-operator-controlled environments where the same party owns both the Tesla account and the agent using the skill. - Internal tools or assistants for technically savvy users who can correctly configure OAuth, TLS, and the signing proxy. - Workflows where strong safety controls are in place: restricted prompt sources, role-based access, clear guardrails around which commands the agent is allowed to issue, and explicit user confirmations for high-impact actions (e.g., unlock, charge control). - Not recommended for open, user-generated-content-driven agents (like public chatbots) without substantial additional safety, policy, and access-control layers.