I wanted to track it across the factory floor! I can understand why they wouldn't do it, because there's a risk you could start sending commands to the car prior to taking delivery. Of course, they could separate the issuance of a token from the actual VIN association step. Would allow someone to develop an application without having to have possession of a car.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Model S REST API
- Thread starter timdorr
- Start date
-
- Tags
- Model S User Interface
I'm aware that some API endpoints are no longer functional, and they're obviously endpoints that aren't exposed through the current version of the app. For example, the endpoint to open a trunk. Does anyone know if the trigger_homelink endpoint still works? I don't have a garage door to try it out with.
SG57
Former Vendor
@Dr. McKay , yes the trigger homelink over the summon API works as of 3 hours ago when I opened my garage from my phone. I do not know of a trigger homelink endpoint that exists outside the summon API, is there one?
I can't find a way to edit my previous post, my apologies.
I don't know where the library in question (TeslaJS) got that endpoint from, but it seems to me like it might be gone as it only responds with 400 (the same response as openTrunk, which also appears to be gone). I was able to get it working with the WebSocket streaming server, so thanks for that tip.
I don't know where the library in question (TeslaJS) got that endpoint from, but it seems to me like it might be gone as it only responds with 400 (the same response as openTrunk, which also appears to be gone). I was able to get it working with the WebSocket streaming server, so thanks for that tip.
SG57
Former Vendor
Anyone here with an updated 8.1 firmware on their vehicle notice a change in the 'car_type' property for the vehicle state data?
I'll report back on the change once I acquire more detail on the change. For what I have seen, the expected car type values to this day are: "x", "s", "s2", or "3". Perhaps they've added or changed one.
I'll report back on the change once I acquire more detail on the change. For what I have seen, the expected car type values to this day are: "x", "s", "s2", or "3". Perhaps they've added or changed one.
SG57
Former Vendor
I can now confirm after collecting more data from 8.1 firmware vehicles (example firmware: 2017.40.0) that there are new values being returned for the car_type field.
The new values I have seen are:
- models
- models2
Strange, my app that I built for myself has been working for well over a year and today I get the "
private, must-revalidate"
I signed in again, got a new token and still the same issue.
I should add that I am able to retrieve vehicles fine but any other API call such as get data fails with the above error ?
Thoughts?
private, must-revalidate"
I signed in again, got a new token and still the same issue.
I should add that I am able to retrieve vehicles fine but any other API call such as get data fails with the above error ?
Thoughts?
{ Status Code: 200, Headers {
"Cache-Control" = (
"max-age=0, private, must-revalidate"
);
My app gets a new token every 2months to avoid the expiry. I am just thinking the OWNERAPI_CLIENT_ID and SECRET may have changed. Weird that it just stopped working this afternoon around 1pm EST.
Ok, wasn't that. I am using the ones issued in Feb2017.
I am at a loss at whats causing it to think it needs to revalidate for api/1/vehicles/VEHID/data API call ?
Yep official app works.
My code has been code stable for over a year, well apart from an update for iOS11 earlier in the summer but its been working fine and was working on my drive to work fine and then just stopped around 1pm when nothing else had been touched. Its weird I can log in and get a token via the REST API's, retrieve a list of vehicles, just that one API fails
Tried and that did nothing. Also I suspect the Tesla app uses the same API call and thats working
Similar threads
