Tim Dorr
Tim Dorr
For those really interested, here's the entire state machine they use for autopark related stuff (it's pretty complex): https://gist.github.com/timdorr/61834c6ada93d961e4646ea5fff6d7f7
Correct. The header is in the format `Authorization: Basic %{base64(token)}`. The token comes from the vehicles endpoint in the `tokens` field. Same as the streaming data API.
Ah, yes, you're right. It's `Basic {base64({email}:{token})}`
Look at whatever the `heartbeat_frequency` is in the `control:hello` response.
The HTTP streaming endpoint is completely dead. It 502's for my car, which was still supported as of last year. I've updated the gem to use the new WebSocket endpoint:...
[Mine works.](https://github.com/timdorr/tesla-api/blob/master/lib/tesla_api/stream.rb) It's actively running as I write this, for a project I'm working on right now.
There is a `control:ping` on the Summon API. You might try that.
Yeah, that makes sense with the new SSO system going live (must have been what took MFA so long). I'll get the Ruby gem updated soon.
Yep, I can confirm you need a new connect message. Here's what we generate in Ruby: ```rb def streaming_connect_message { msg_type: 'data:subscribe_oauth', token: client.access_token, value: 'speed,odometer,soc,elevation,est_heading,est_lat,est_lng,power,shift_state,range,est_range,heading', tag: self['vehicle_id'].to_s, } end...
https://tesla-api.timdorr.com/api-basics/authentication