Closed kristianolofsson closed 2 years ago
The car may just have a bad connection. It is not really something this library can help you with, sorry. Just keep trying.
Sorry to reopen this, but I'm definitely seeing a lot of 408 errors from this library, while if I open the Tesla app on my phone, it can connect just fine. What could be the reason for this? A 408 is a Timeout, so could it be that the library times out before the car responds, while the Tesla app has a bigger timeout window set?
I am actually seeing a lot of 408 errors myself lately. But I am also seeing it in the app. Perhaps Tesla changed or broke something. The library does not timeout, the response code is directly from the Tesla API. There is not really something I can do about it.
Alright, thank you for the reply!
fre. 1. jul. 2022, 14:50 skrev Martin Schimmel @.***>:
I am actually seeing a lot of 408 errors myself lately. But I am also seeing it in the app. Perhaps Tesla changed or broke something. The library does not timeout, the response code is directly from the Tesla API. There is not really something I can do about it.
— Reply to this email directly, view it on GitHub https://github.com/onokje/node-red-contrib-tesla/issues/36#issuecomment-1172312906, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABBYPRMP5GJLBRKMFGB2GT3VR3STFANCNFSM5LIEXUOQ . You are receiving this because you commented.Message ID: @.***>
Im trying this with a Tesla MY but can't get I to work, keep getting 408 and the car will not wakeup. Tried both the wakeup command and during eg. unlock charging port to set the wakeup automatically. The auth seems to work since the car shows up in list of vehicles.