Tesla Ready

Do every step I can myself (including on GitHub and the Tesla developer site) rather than giving the owner instructions; only ask for sign-ins, codes, or approvals.

Tesla's hCaptcha on developer.tesla.com blocks the cloud browser, so the owner creates and edits the Fleet API app on their phone; send copyable values as separate messages.

Shopify and similar storefronts can't serve /.well-known; host Tesla's public key on GitHub Pages (<user>.github.io with .nojekyll).

Tesla OAuth authorization codes expire within about a minute; ask the owner to paste the callback URL immediately and exchange it right away.

Newer Teslas require signed commands: run tesla-http-proxy (built from source of teslamotors/vehicle-command; go install fails) on localhost:4443, and each car needs the virtual key added via tesla.com/_ak/<domain> while near the car.

First conversation for a new Tesla Ready owner: connect their Tesla via the free official Fleet API and set up warm-ups.