Tim Dorr

This isn't an API, it's just documentation. We just need to figure out how they are doing it. It's not over the usual API server, so I'm not sure where...

@btamburrino Make sure you're issuing POST requests for the `command` endpoints. They are not GETs.

I mentioned them here: http://www.teslamotorsclub.com/showthread.php/13410-Model-S-REST-API/page49?p=1337610&viewfull=1#post1337610 They both require keyfob presence near the car, so it's hard to test. I haven't dragged my laptop out to the garage yet.

Just found out you can trick it by doing a keyless start and then using the associated APIs. I'll test this over the weekend. But I get the feeling Tesla...

Yes, it's a separate token field. I traced the code back to the Bluetooth device name in the Android app. And yeah, as long as the lat lon is within...

I have a 2012, so I'm probably in the same boat. I'm pretty sure they group this off with Summon. I haven't made any attempts yet, though.

Are you attempting it with the fob within range? I think they make have closed the keyless driving loophole. As far as I know, the API itself hasn't changed.

Looks like you open a standard Websocket connection to `wss://streaming.vn.teslamotors.com/connect/{vehicle_id}`. From there, there is a JSON-based communication protocol with output commands and input results from the server: It has the...

Commands that can be received (`msg_type -> arg1, arg2, ...`) : ``` control:hello -> connection_timeout, autopark: {autopark_pause_timeout, autopark_stop_timeout, heartbeat_frequency} control:goodbye -> reason control:pong -> timestamp autopark:status -> autopark_state autopark:cmd_result ->...

Commands that can be sent (`msg_type -> arg1, arg2, ...`): ``` control:ping -> timestamp autopark:heartbeat_app -> timestamp autopark:cmd_abort -> autopark:cmd_forward -> latitude, longitude autopark:cmd_reverse -> latitude, longitude homelink:cmd_trigger -> latitude,...