Model S REST API

wayner · Jun 20, 2016

And according to some posts in the Remote S app thread - Summon is also broken. There is also a report above that VT is broken.

jsgoecke · Jun 20, 2016

Yes, Autopark is summon and indeed is broken.

rog · Jun 20, 2016

What is surprising to me - if Tesla really changed the endpoint, wouldn't they have to update the Android / iOS app too to make it use this new endpoint? The official Tesla app on my Android phone has not been updated for weeks, ~~but still Summon is working on it...~~ I stand corrected: Summon via official Android app doesn't work for me anymore either... Getting "Unable to connect to the car" error message. All other functions in the app still work.

Polyport · Jun 20, 2016

Tesla switched to WebSockets for Summon and HomeLink.

They connect to wss://streaming.vn.teslamotors.com/

On a successful connection, the server responds with
{"autopark":{"autopark_pause_timeout":2000,"autopark_stop_timeout":10000,"heartbeat_frequency":500},"connection_timeout":20000,"msg_type":"control:hello"}
followed by:
{"autopark_state":"ready","msg_type":"autopark:status"}
{"homelink_nearby":true,"msg_type":"homelink:status"}

During auto park/summon, the server will send a heartbeat, like this:
{"msg_type":"autopark:heartbeat_car","timestamp":488163277436.176025}
{"msg_type":"autopark:heartbeat_car","timestamp":488163277936.211975}

When summon forward is requested, the server replies with:
{"cmd_type":"autopark:cmd_forward","msg_type":"autopark:cmd_result","reason":"","result":true}.E{"msg_type":"autopark:heartbeat_car","timestamp":488163276934.765991}

When summon is cancelled, the server sends:
{"cmd_type":"autopark:cmd_abort","msg_type":"autopark:cmd_result","reason":"","result":true}
{"autopark_state":"aborting","msg_type":"autopark:status"}

{"latitude":43.589033,"longitude":-121.858813,"msg_type":"vehicle_data:location"} (altered to not publish my house's location

)
{"autopark_state":"ready","msg_type":"autopark:status"}

Obviously, this is missing what the client sends to the server. That's mostly because it's either compressed or not ASCII and I need to recompile my test code to give me hex bytes instead of ASCII in that situation before I can figure out the commands.

jsgoecke · Jun 20, 2016

Great sleuthing @Polyport! I am anxiously awaiting what you find on what to send from the client -> the server.

Polyport said:
Tesla switched to WebSockets for Summon and HomeLink.

They connect to wss://streaming.vn.teslamotors.com/

On a successful connection, the server responds with
{"autopark":{"autopark_pause_timeout":2000,"autopark_stop_timeout":10000,"heartbeat_frequency":500},"connection_timeout":20000,"msg_type":"control:hello"}
followed by:
{"autopark_state":"ready","msg_type":"autopark:status"}
{"homelink_nearby":true,"msg_type":"homelink:status"}

During auto park/summon, the server will send a heartbeat, like this:
{"msg_type":"autopark:heartbeat_car","timestamp":488163277436.176025}
{"msg_type":"autopark:heartbeat_car","timestamp":488163277936.211975}

When summon forward is requested, the server replies with:
{"cmd_type":"autopark:cmd_forward","msg_type":"autopark:cmd_result","reason":"","result":true}.E{"msg_type":"autopark:heartbeat_car","timestamp":488163276934.765991}

When summon is cancelled, the server sends:
{"cmd_type":"autopark:cmd_abort","msg_type":"autopark:cmd_result","reason":"","result":true}
{"autopark_state":"aborting","msg_type":"autopark:status"}

{"latitude":43.589033,"longitude":-121.858813,"msg_type":"vehicle_data:location"} (altered to not publish my house's location )
{"autopark_state":"ready","msg_type":"autopark:status"}

Obviously, this is missing what the client sends to the server. That's mostly because it's either compressed or not ASCII and I need to recompile my test code to give me hex bytes instead of ASCII in that situation before I can figure out the commands.

faraz · Jun 20, 2016

@rog, it was not working for me either however, I rebooted my car computer and force shut down the app. When loading again it successfully connected and summon started working. My guess is Tesla kind of sends the connection data to the app and it updates the endpoints behind the seen! I couldn't decipher the client request either so hopefully @Polyport can figure it out

jsgoecke · Jun 20, 2016

Also @Polyport, any code examples you could provide would be greatly appreciated.

timdorr · Jun 20, 2016

@Polyport You were close. They're using some interesting choices of JSON serialization for their message objects in the Android client. Not sure of the equivalent over on the iOS side, but I haven't looked into that version in a while. (Perhaps they're binding to Java now?)

Anyways, I'll list out some initial findings over on the Github repo: GitHub - timdorr/model-s-api: A Ruby gem and unofficial documentation of the Tesla JSON API

Polyport · Jun 20, 2016

timdorr said:
@Polyport You were close. They're using some interesting choices of JSON serialization for their message objects in the Android client. Not sure of the equivalent over on the iOS side, but I haven't looked into that version in a while. (Perhaps they're binding to Java now?)

Anyways, I'll list out some initial findings over on the Github repo: GitHub - timdorr/model-s-api: A Ruby gem and unofficial documentation of the Tesla JSON API

Damn. You beat me to it

Just got finished decoding all the commands. All my stuff done is with iOS, what I'm seeing matches what you put on Github. I think you missed the autopark:heartbeat_app -> timestamp in your list

timdorr · Jun 20, 2016

Polyport said:
I think you missed the autopark:heartbeat_app -> timestamp in your list

Nope, it's in there. There's a heartbeat_car server response and heartbeat_app client command. You should issue those at the rate that the control:hello asks you to.

Polyport · Jun 20, 2016

timdorr said:
Nope, it's in there. There's a heartbeat_car server response and heartbeat_app client command. You should issue those at the rate that the control:hello asks you to.

I wrote that before you added the second part about what the app can send to the car

rog · Jun 21, 2016

faraz said:
@rog, it was not working for me either however, I rebooted my car computer and force shut down the app. When loading again it successfully connected and summon started working. My guess is Tesla kind of sends the connection data to the app and it updates the endpoints behind the seen!

Thanks, re-setting the app seems to have done the trick.

timdorr · Jun 21, 2016

I've added some very basic support to the tesla_api Ruby gem: Autopark support in gem by timdorr · Pull Request #31 · timdorr/model-s-api · GitHub

I don't have a recent MS to test against, so I can't do anything other than connect and confirm the heartbeat stuff all works. If anyone can help, that would be appreciated!

L-P-G · Jun 22, 2016

timdorr said:
I've added some very basic support to the tesla_api Ruby gem: Autopark support in gem by timdorr · Pull Request #31 · timdorr/model-s-api · GitHub

I don't have a recent MS to test against, so I can't do anything other than connect and confirm the heartbeat stuff all works. If anyone can help, that would be appreciated!

Shoot me a PM, I can test this on my MS

jayman · Jun 24, 2016

I'm wondering if I will be throttled or have my account disabled if I am using the streaming protocol on my model S and model X at the same time? They are both under the same account.

ACDriveMotor · Jun 29, 2016

Since you could validly do this via the mobile apps I am guessing they would account for this scenario.

jayman · Jun 29, 2016

ACDriveMotor said:
Since you could validly do this via the mobile apps I am guessing they would account for this scenario.

Yup, works well. Glad to see I can track two cars at once under one account.

blueguse · Jul 1, 2016

Is there a way(api) to unlock the charge port so the charger can be pulled out without pressing the button on the charger?

Prefect · Jul 9, 2016

So since commands in PHP always return 404, I tried javascript:

Code:

<script>

var request = new XMLHttpRequest();

request.open('POST', 'https://owner-api.teslamotors.com/api/1/vehicles/<?=$VEHICLE_ID?>/wake_up');

request.setRequestHeader('Authorization', 'Bearer <?=$token?>');

request.onreadystatechange = function () {
  if (this.readyState === 4) {
    console.log('Status:', this.status);
    console.log('Headers:', this.getAllResponseHeaders());
    console.log('Body:', this.responseText);
    alert ("response: "+this.status + " -- " + this.responseText);
  }
};

request.send();

</script>

And this is the result:

Code:

XMLHttpRequest cannot load https://owner-api.teslamotors.com/api/1/vehicles/71923157...0506/wake_up. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://iteconomy.ch' is therefore not allowed access. The response had HTTP status code 404.

Am I blocked or something??

fact200 · Jul 9, 2016

Prefect said:

So since commands in PHP always return 404, I tried javascript:
<snip>

Code:

XMLHttpRequest cannot load https://owner-api.teslamotors.com/api/1/vehicles/71923157...0506/wake_up. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://iteconomy.ch' is therefore not allowed access. The response had HTTP status code 404.

Am I blocked or something??

404 usually means that the vehicle id you're using is incorrect. What happens when you list vehicles? If that works, the proper vehicle id you should use is the "id" field from that response; not the "vehicle_id" field. Does querying for vehicle charge state work?

That javascript error you're getting is just because you can't do cross domain calls in a browser without the proper CORS headers.

Model S REST API

Active Member

Member

Member

Member

Member

New Member

Member

Model S P90D w/AP3.0

Member

Model S P90D w/AP3.0

Member

Member

Model S P90D w/AP3.0

Member

Member

Member

Member

Member

Member

Member

Similar threads