Action Required
On the 15th November, Tesla announced the new vehicle_location scope, stating that:
All existing authorization grants that have the vehicle_device_data scope will automatically include the vehicle_location scope (no partner or user action needed).
However this has now changed,
and instead Tesla will be requiring all users to modify their authorized scopes to include the new vehicle_location scope to continue getting location data.
What you need to do
The Teslemetry console has a convenient button to update your scopes, but since you're already here, you just need to click the link below, log in with your Tesla account, and update your scopes.
Synergy with server side polling
One of the first steps to implement the vehicle data caching announced yesterday,
was updating the server side polling service to request vehicle_data from all vehicles with a subscription automatically.
Previously we let you decide which data endpoints the request would include, but this was incompatible with being the new default, and source of the cached data.
Now the server side polling service will pull all data endpoints based on the scopes you have provided.
Right now this simply means those with vehicle_device_data scope get all data endpoints,
but in late December only those with the vehicle_location scope will continue to have location data included.
