Wake up endpoint suddenly returning 406 - Not Acceptable. Has anybody else run into this?

[Rockster160]

Hey all! First off- thank you so much for reverse engineering the API and maintaining the documentation. It's amazing!

I set up a cool little system that allowed me to monitor my car. I had it pinging the API roughly every hour to get updates. This whole thing has been working for... A month? Everything has been great. However, suddenly the other day I started getting back a 406 when I try to hit the wake up endpoint.

I believe I'm following all of the recommended times and back offs and retry criteria, but I'm wondering if I got blocked because of the frequent requests? All of the auth / refresh endpoints are working as expected. I can even hit /vehicles to get that data, but trying to hit any endpoints specific to my car (Such as latest_vehicle_data, or any commands) results in an INSTANT 408 Timeout. Hitting the wake_up (which typically is what follows a timeout) endpoint results in the 406 - Not Acceptable.

The regular Tesla app is still working without issue. I've also tried regenerating my subscription code- all successful including auth until hitting an endpoint specific to my car.

Any ideas for how to fix this, and more importantly- how to prevent it from happening in the future?

[rawmean]

Try this and see if you still get the 406 error.

curl --location --request POST 'https://owner-api.teslamotors.com/api/1/vehicles/your_vehicleID/wake_up' \
--header 'Authorization: Bearer your_token'

[themonomers]

@Rockster160 I can confirm the same error and fix by setting content type to "application/json" works in Google Apps Script.

[dvermagithub]

Specific commands, not all, such as vent and close windows and changing charge limit started exhibiting a 406 error a few days ago.

Adding 'Content-type': 'application/json' to my python request command header did not initially work for me. Started getting an http 400 error response.

Solved that by fixing a few things in my code...first the data being passed to the request has to be formatted as proper json which means using " instead of ' and the data has to be dumped into json format in python. kind of annoying but at least it is all working now.
Thanks for this thread.

[rawmean]

I can confirm that setting the payload as proper json is important. For me, adding the 'Content-type': 'application/json' doesn't make a difference. Maybe the request module adds that automatically.
Example in python:

data={'percent': 85}
resp = requests.request('POST', full_url, headers=headers, data=json.dumps(data))


[heumat]

Have a look at #594, I just added a "Accept": "application/json" into the request header dict and it works now.

[dvermagithub]

@rawmean the code data=json.dumps(data) is essentially turning the payload into proper json format, which is what I had to add to my code in addition to 'Content-type': 'application/json'

[heumat]

As written as a short comment on the earlier thread above, the following solved the 406 for me:

response = await session.get(
    url,
    headers={"authorization": f"Bearer {token}", "Accept": "application/json"},
    timeout=6,
)

credits to the guys in #594 !