Bad request
Opened this issue · 1 comments
ScanxTaz commented
Hey ! Good morning :)
First of all, thanks a lot for your work, really appreciates, really hard to find something that works, especially when you jump in the wonderful world of Tesla with a new TM3 :)
Hey, small prob with the code on my side, each type I'm using the code, I'm getting a "bad request" as a reply... How could I go a bit deeper in the calls to check what's goin'on there ?
Thanks for your help,
/home/*** # teslatoken -u ***.***@***.com -p ******** ERROR: An HTTP error occurred during authorization: 400: Bad Request
fornstedt commented
Hello !
I’ve seen this issue too and I believe it is a result of the new 2-factor authentication feature Tesla has introduced. When introducing that it seems the authentication process has changed and the one implemented in teslatoken needs to be updated. I haven’t looked into it further since I have a token where I can use a refresh-token to renew it (which seems to work still). One thing you can try is to temporary disable 2-factor authentication on your Tesla-account to see if that’s the issue. If so, you might be able to generate a token you can use and refresh further on even when you activate 2-factor authentication again.
Feel free to dig into the code and file a pull request if you find a solution! If I get the time I will try to update it myself, but currently I don’t have the time needed where I can prioritize this.
BR
/ Eric
… 2 okt. 2021 kl. 07:46 skrev ScanxTaz ***@***.***>:
Hey ! Good morning :)
First of all, thanks a lot for your work, really appreciates, really hard to find something that works, especially when you jump in the wonderful world of Tesla with a new TM3 :)
Hey, small prob with the code on my side, each type I'm using the code, I'm getting a "bad request" as a reply... How could I go a bit deeper in the calls to check what's goin'on there ?
Thanks for your help,
/home/*** # teslatoken -u ***.***@***.com -p ******** ERROR: An HTTP error occurred during authorization: 400: Bad Request
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#3>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACC5COYTQZWHRR7F4Y6XLWDUE2MDTANCNFSM5FGAGJRQ>.