Tesla has changed how they do authentication (referred to now as v3). Every app and site that uses the API has to be updated.
And if you don't want to give apps/sites your Tesla.com credentials (which you shouldn't, no matter how much you trust them, because they can always be hacked with a harvester), then you need to generate a special token the apps/sites can use to talk to the Tesla scripting API.
This is like a 'valet key' for the scripting interface, giving the 3rd party very limited access to just the features they need.
Here's a working PHP script to locally generate your V3 Refresh Token.
**Working** PHP to Generate Refresh Token (Steps 1-4) · Discussion #288 · timdorr/tesla-api
Confirmed to work with TeslaFI.com (which has already been updated to support the new authentication).
And if you don't want to give apps/sites your Tesla.com credentials (which you shouldn't, no matter how much you trust them, because they can always be hacked with a harvester), then you need to generate a special token the apps/sites can use to talk to the Tesla scripting API.
This is like a 'valet key' for the scripting interface, giving the 3rd party very limited access to just the features they need.
Here's a working PHP script to locally generate your V3 Refresh Token.
**Working** PHP to Generate Refresh Token (Steps 1-4) · Discussion #288 · timdorr/tesla-api
Confirmed to work with TeslaFI.com (which has already been updated to support the new authentication).