Skip to content
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

Always get timeout reply on reading preconditioning_schedule_data #312

Open
jp-embedded opened this issue Sep 19, 2024 · 0 comments
Open

Comments

@jp-embedded
Copy link

I always receive timout replies when requesting preconditioning_schedule_data. All other requests and commands work.

I suspect I have ended up with a ton of schedules in my vehicle. But I cannot delete them wihout being able to get the preconditioning_schedule_data list.

Same result wether I run through the proxy or directly. Setting proxy timeout does not help so I suspect the timeout occurs in the vehicle.

jp@jp-embedded:~$ curl -H "Authorization: Bearer `cat access_token.txt`" -G -v "https://fleet-api.prd.eu.vn.cloud.tesla.com/api/1/vehicles/5YJ-REMOVED-euoi1/vehicle_data" --data-urlencode "endpoints=preconditioning_schedule_data" | jq -r .
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 52.211.84.165:443...
* TCP_NODELAY set
* Connected to fleet-api.prd.eu.vn.cloud.tesla.com (52.211.84.165) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [15 bytes data]
* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [2836 bytes data]
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [80 bytes data]
* TLSv1.3 (IN), TLS handshake, Finished (20):
{ [52 bytes data]
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.3 (OUT), TLS handshake, Finished (20):
} [52 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=US; ST=California; L=Palo Alto; O=Tesla, Inc.; CN=fleet-api.prd.eu.vn.cloud.tesla.com
*  start date: Oct  9 00:00:00 2023 GMT
*  expire date: Oct  8 23:59:59 2024 GMT
*  subjectAltName: host "fleet-api.prd.eu.vn.cloud.tesla.com" matched cert's "fleet-api.prd.eu.vn.cloud.tesla.com"
*  issuer: C=US; O=DigiCert Inc; CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
} [5 bytes data]
* Using Stream ID: 1 (easy handle 0xaaaad87d93c0)
} [5 bytes data]
> GET /api/1/vehicles/5YJ3-REMOVED-381/vehicle_data?endpoints=preconditioning_schedule_data HTTP/2
> Host: fleet-api.prd.eu.vn.cloud.tesla.com
> user-agent: curl/7.68.0
> accept: */*
> authorization: Bearer eyJh....REMOVED......50X3RqVCrt6l0g
> 
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [230 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [230 bytes data]
* old SSL session ID is stale, removing
{ [5 bytes data]
* Connection state changed (MAX_CONCURRENT_STREAMS == 100)!
} [5 bytes data]
  0     0    0     0    0     0      0      0 --:--:--  0:00:09 --:--:--     0< HTTP/2 408 
< x-xss-protection: 1; mode=block
< x-txid: b09133325c4118e30cbfad003c6117c8
< content-type: application/json; charset=utf-8
< vary: Accept,Accept-Encoding
< x-request-id: fdd00e9d-3f01-4e34-806d-8f5acccce87c
< ratelimit-device-data-per-vehicle-limit: 750
< ratelimit-device-data-per-vehicle-remaining: 725
< ratelimit-device-data-per-vehicle-reset: 38896
< content-length: 117
< x-envoy-upstream-service-time: 9116
< x-frame-options: DENY
< x-content-type-options: nosniff
< strict-transport-security: max-age=31536000; includeSubDomains
< cache-control: no-cache, no-store, private, s-max-age=0
< date: Thu, 19 Sep 2024 13:11:52 GMT
< server: envoy
< 
{ [117 bytes data]
100   117  100   117    0     0     12      0  0:00:09  0:00:09 --:--:--    38
* Connection #0 to host fleet-api.prd.eu.vn.cloud.tesla.com left intact
{
  "response": null,
  "error": "{\"error\": \"timeout\"}",
  "error_description": "",
  "txid": "b09133325c4118e30cbfad003c6117c8"
}
jp@jp-embedded:~$ 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant