You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched both the existing open issues & recently closed issues and did not find a duplicate of this issue.
I have read about the Fleet API and understand I may need to use it
I understand issues relating to read only commands will be auto closed if not using the Fleet API.
Version of the Tesla component
3.24.1
Version of the Tesla car software
2024.26.7 b7e14964b659
Model
Model Y
Current Behavior
I've set up everything regarding the Fleet API Proxy. Had some trouble with that setup, but I believe that side is now working.
However, I can't authenticate with this component, always getting the following:
Some searches suggested this could be due to rate limiting, so I have tried leaving it on pause for a day and try again. the result was the same
Expected Behavior
succesful authentication
Debug logs
Logger: custom_components.tesla_custom
Source: custom_components/tesla_custom/__init__.py:220
integration: Tesla Custom Integration (documentation, issues)
First occurred: 4:36:43 PM (3 occurrences)
Last logged: 4:56:10 PM
Unable to communicate with Tesla API: UNKNOWN_ERROR_412
Anything else?
Debug log of the Tesla HTTP Proxy add-on:
[16:45:35] werkzeug:INFO: 172.30.32.2 - - [16/Sep/2024 16:45:35] "GET / HTTP/1.1" 200 -
[16:45:36] webui:DEBUG: Callback URL: https://tesla.n62.casa/callback?locale=en-US&code=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX&state=abd938523c&issuer=https%3A%2F%2Fauth.tesla.com%2Foauth2%2Fv3
[16:45:36] webui:DEBUG: code: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
[16:45:36] urllib3.connectionpool:DEBUG: Starting new HTTPS connection (1): auth.tesla.com:443
[16:45:37] urllib3.connectionpool:DEBUG: https://auth.tesla.com:443 "POST /oauth2/v3/token HTTP/1.1" 200 2273
[16:45:37] webui:WARNING: Obtained refresh token: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
[16:45:37] werkzeug:INFO: 172.30.32.2 - - [16/Sep/2024 16:45:37] "GET /callback?callback_url=https://tesla.n62.casa/callback?locale%3Den-US%26code%XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX%26state%3Dabd938523c%26issuer%3Dhttps%253A%252F%252Fauth.tesla.com%252Foauth2%252Fv3 HTTP/1.1" 200 -
[16:45:39] werkzeug:INFO: 172.30.32.2 - - [16/Sep/2024 16:45:39] "GET / HTTP/1.1" 200 -
2024-09-16T16:46:25+01:00 [info ] Received GET request for /api/1/products
2024-09-16T16:46:25+01:00 [debug] Forwarding request to https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/products
2024-09-16T16:46:28+01:00 [info ] Received GET request for /api/1/products
2024-09-16T16:46:28+01:00 [debug] Forwarding request to https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/products
2024-09-16T16:46:31+01:00 [info ] Received GET request for /api/1/products
2024-09-16T16:46:31+01:00 [debug] Forwarding request to https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/products
2024-09-16T16:46:36+01:00 [info ] Received GET request for /api/1/products
2024-09-16T16:46:36+01:00 [debug] Forwarding request to https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/products
2024-09-16T16:46:40+01:00 [info ] Received GET request for /api/1/products
2024-09-16T16:46:40+01:00 [debug] Forwarding request to https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/products
The text was updated successfully, but these errors were encountered:
naps62
added
car
For items that relate to Tesla vehicles
triage
New issues raised that need initial attention
labels
Sep 16, 2024
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.26.7 b7e14964b659
Model
Model Y
Current Behavior
I've set up everything regarding the Fleet API Proxy. Had some trouble with that setup, but I believe that side is now working.
However, I can't authenticate with this component, always getting the following:
Some searches suggested this could be due to rate limiting, so I have tried leaving it on pause for a day and try again. the result was the same
Expected Behavior
succesful authentication
Debug logs
Anything else?
Debug log of the Tesla HTTP Proxy add-on:
The text was updated successfully, but these errors were encountered: