Mine died on June 5 and within 5 minutes of upgrading to 2.4.239.
I had a 'cookie' logger running for 3 different cars, all different firmwares.
They all 'died' at the same time.
hmmmm
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.
Mine died on June 5 and within 5 minutes of upgrading to 2.4.239.
Good news, everyone!
I finally updated the API docs for the new oAuth API and some of the new endpoints: Tesla Model S JSON API · Apiary
If anyone has any ideas about the upcoming_calendar_entries, notification_preferences, and vehicle_subscriptions endpoints (or any that I've missed), I can get those added too.
I don't think I see the Logout command documented.
Hmm. Well that is a problem if you are caching the token locally. Or if you worry about someone stealing your token somehow. If I were creating the API surface area I would want a way to force expire the auth token.
Good news, everyone!
I finally updated the API docs for the new oAuth API and some of the new endpoints: Tesla Model S JSON API · Apiary
If anyone has any ideas about the upcoming_calendar_entries, notification_preferences, and vehicle_subscriptions endpoints (or any that I've missed), I can get those added too.
I'd be interested in hearing if anyone is having any luck with the new API locations....I can get a vehicle list, but any kind of data request, such as:
curl -H "Authorization: Bearer [my bearer token]" -H "Content-Type: application/json" -i https://owner-api.teslamotors.com/api/1/vehicles/[my vehicle id]/data_request/charge_state
Just results in a 404....
Yeah, that vehicle ID drove me nuts too. In php you have to set a special "BIGINT" parameter in order to retrieve it properly.
Yeah, that vehicle ID drove me nuts too. In php you have to set a special "BIGINT" parameter in order to retrieve it properly.
var matches = /"id":(\d*)/.exec(json);
// matches = [""id":6959443970443583529", "6959443970443583529"]
var id = matches[1];
// id = "6959443970443583529"
{ inside_temp: 47,
outside_temp: 26,
driver_temp_setting: 19.8,
passenger_temp_setting: 19.8,
is_auto_conditioning_on: true,
is_front_defroster_on: 0,
is_rear_defroster_on: false,
fan_status: 10,
seat_heater_left: 0,
seat_heater_right: 0,
seat_heater_rear_left: 0,
seat_heater_rear_right: 0,
seat_heater_rear_center: 0,
seat_heater_rear_right_back: 0,
seat_heater_rear_left_back: 0,
smart_preconditioning: false }
Sorry, as this is probably a really dumb question, but where do I get a client_id and a client_secret? I don't remember setting anything like that up before - just my email and password.Everything seems to work for me... Beware totally lazy Python below.
#!/usr/bin/python
import requests
oauthit = {"grant_type" : "password",
"client_id" : "YOURCLIENTIDHERE",
"client_secret" : "YOURCLIENTSECRETHERE",
"email" : "YOUREMAILHERE",
"password" : "YOURPASSWORDHERE" }
print oauthit
Sorry, as this is probably a really dumb question, but where do I get a client_id and a client_secret? I don't remember setting anything like that up before - just my email and password.
Update: my cookie logger died on 7/16. Time to go dig up the new login process.Interesting. Mine seems fine: