You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
I see lots of HTTP 503 error messages with "timeout in request to 172.20.241.22:7654". Only about 10% of my requests complete with HTTP 200 OK. The system seems to be getting gradually worse and worse as more owners come online.
Perhaps the new calendar integration added a lot more traffic on their systems and now everything else is suffering.Agreed. It's in a pretty sad state. I don't think it's just a problem with more owners (though I'm sure that's exacerbating the problem). It seems to have started going downhill with the cutover to the newer api.
I've finished up my Ruby gem and it's at 1.0.0: tesla_api | RubyGems.org | your community gem host
It's got a full test suite for all endpoints. The streaming API is the only thing missing because it's threaded and that's harder to test.
I found some inactive endpoints for "trunk_open" that asks for a "which_trunk", that can be either "front" or "rear". Hopefully, they'll turn that on soon. I can see a use case:
- Watch the car for being awake and then for it's trunk/frunk open state.
- Whenever you're outside of a home geofence and the trunk/frunk opens, assume something was put into the car.
- When you park back at your house, it automatically opens the trunk/frunk for you.
Getting to the settings screen to open the car can be somewhat cumbersome, so that would be a neat script to build out.
@nlc - They probably disabled access to portal.vn. you now have to use owner-API.
Yes, I had to set the "json_bigint_as_string" parameter in order to retrieve the vehicle ID.
The 18 digit "id" field in the new API is a pain in the JSON. It's sent as a number, not a string, and Javascript integers are only significant to 15 digits. Took a while to figure out why my REST calls were not working. Unfortunately you can't just JSON.parse() the response to https://owner-api.teslamotors.com/api/1/vehicles and expect to use "id". The shorter "vehicle_id" is fine but only because its currently fewer than 15 digits long. Now I have to pick apart the response the old fashioned way with regular expressions.
The old login is still working for me. I do notice that a lot of the requests fail/timeout so you may just need to retry.
No, I doesn't work at all here
Maybe your cookies file already have a valid credential and you don't need to get one ?
Can you try to rename your cookies file to save it and test again to see if you get the same error than me ?
That's incredible !!!!
Can you post here the exact curl command you used ?
With the new owner API, it doesn't work too :
curl -H "Content-Type: application/json" -d '{ "grant_type" : "password", "client_id" : "", "client_secret" : "", "email" : "[email protected]", "password" : "xxx" }' https://owner-api.teslamotors.com/oauth/token
gives me the error 500 something goes wrong.
Same problem with Visible Tesla 0.28.
But with Android and official application, no problem. My login/password are good, I can't understand what happens