search

onokje / node-red-contrib-tesla

Node red nodes to control Tesla vehicles and devices
MIT License
21 stars 11 forks source link

"Error response: 408" #20

Closed moshner closed 3 years ago

moshner commented 3 years ago

My automations all failed today, they are giving me an "Error response: 408" every time they try to connect. I have tried:

  1. Updating my manual api token
  2. opening the Tesla app on my phone: It still connect

No change. Any ideas why this would fail now?

onokje commented 3 years ago

A 408 response usually means that the Tesla API backend cannot contact your device/car in time. It is fairly normal. Just try it again a few times. I don't think it is related to authentication, because you would get another error then (401).

It varies from time to time how stable it is. I get 408 responses in my flow all the time, sometimes dozens a day, sometimes none.

moshner commented 3 years ago

Interesting. I haven't had a non-408 response since 8/31. Every single request is always 408. I wonder if there isn't something else going on. Car has premium connectivity and in the evenings it is connected to my home wifi.

moshner commented 3 years ago

...and of course it suddenly worked again for me as soon as I posted this comment.

bastelbert commented 2 years ago

Does anyone else get the 408 error these days? On Tuesday everything worked fine, today I only get "Error response: 408"