-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to setup: could not authenticate #1053
Comments
I want to update that i followed the instructions but same issue. Here is what i did:
Please let me know what else i need to try? |
The error message implies you've not given it the correct refresh token as there is an error message saying |
Feom that tesla add on page I was able to authenticate with tesla http proxy login page and copied the token from. I tried atleast 40 times. It's generating token ok. |
I had exact same issue: Then I noticed that I'm using my local address to create the token. And tried with the duckdns.org address. Things changed to unexpected direction. Tesla Custom Integration still says: "Failed to set up: Check the logs" And the log says: And a bit above that: ...I am located in Finland. Any idea why the car is registered in Turkey? Or rather, how to fix this one? I'm the first owner of the car, 1.5y old MY - or at least that was my belief until today :) |
Googling, it seems like others have Turkey there as well, so that might not be the actual cause. Problem persists:
|
Is there an existing issue for this?
I have read about the Fleet API and understand I may need to use it
Version of the Tesla component
3.24.1
Version of the Tesla car software
2024.32.7
Model
Model y 2021 LR
Current Behavior
I followed the instructions https://github.com/alandtse/tesla/wiki/Proxy-setup-with-DuckDNS-and-NGinx multiple times and have same issue
Expected Behavior
I should be able to see and control the tesla.
Debug logs
Anything else?
No response
The text was updated successfully, but these errors were encountered: