Open andig opened 6 months ago
I think the problem is that the vehicle is asleep. Until a few days ago, Tesla server returned cached data when the vehicle was asleep. Somehow they stopped doing that. I'm not sure if this is a bug or if they change the behavior. I reported it here: #178
Until a few days ago, Tesla server returned cached data when the vehicle was asleep.
This is NOT what this issue is about. This issue is about vehicle asleep for GET requests returning HTTP 200 and for POST requests HTTP 500. The bahaviour is inconsistent.
This is NOT what this issue is about. This issue is about vehicle asleep for GET requests returning HTTP 200 and for POST requests HTTP 500. The bahaviour is inconsistent.
I see. But, I get HTTP 408 when I send a vehicle_data
request. Don't you? I don't send the requests using the proxy. Maybe that's why?
I see. But, I get HTTP 408 when I send a vehicle_data request. Don't you? I don't send the requests using the proxy. Maybe that's why?
Lets not get side-tracked. This issue is about sending commands via proxy.
Note this log for retrieving data vs. sending commands (coming from https://github.com/evcc-io/evcc/issues/12294#issuecomment-1948394229):
Sending commands to proxy results in HTTP 500 (still need to verify behaviour for using fleet api directly). Imho it should return HTTP 200 and indicate the error in the body same as with executing
GET
requests.