Jason Goecke

Not sure these are actually implemented, as when I try I get: https://owner-api.teslamotors.com/api/1/vehicles/1234/command/front_defrost_on 400 Bad Request So is this really implemented?

I just gave it a try, indeed the Tesla API is now returning a 400 Bad Request whereas this worked before. I will have to track down what Tesla recently...

Reopening as the other ticket is the fact that Homelink is also not working in addition to AutoPark.

From @Polyport here: https://teslamotorsclub.com/tmc/posts/1591755/ ``` 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"}...

Here is the full API now over websockets for Autopark and Homelink: https://github.com/timdorr/model-s-api/issues/16

https://github.com/timdorr/model-s-api/commit/93b56434558745dd6423a2f803761ea3f4444832

Ok, I have the basics working: ``` go package main import ( "strconv" "github.com/jsgoecke/tesla" "encoding/base64" "log" "net/http" "net/url" "os" "os/signal" "time" "github.com/gorilla/websocket" ) var ( email = "valid_email" server =...

Some of the data output: ``` json 2016/06/22 10:41:02 recv: {"autopark":{"autopark_pause_timeout":2000,"autopark_stop_timeout":10000,"heartbeat_frequency":500},"connection_timeout":20000,"msg_type":"control:hello"} 2016/06/22 10:41:03 recv: {"autopark_state":"ready","msg_type":"autopark:status"} 2016/06/22 10:41:03 recv: {"homelink_nearby":true,"msg_type":"homelink:status"} 2016/06/22 10:41:05 recv: {"autopark_state":"preparing","msg_type":"autopark:status"} 2016/06/22 10:41:08 recv: {"autopark_state":"active_reverse","msg_type":"autopark:status"} 2016/06/22 10:41:13 recv:...

Good question, I'm not sure why I originally used interface{} for many of these. I will have a look and see about changing them to reflect the JSON with int...