I've been looking into the new streaming server endpoint.
Firstly, it looks like some(all?) model 3 with recent software can no longer connect to:
What's interesting however is a model S running the exact same software as me (2018.21.9) also cannot connect to the old streaming endpoint, however I can to my model S on 2018.21.9 perfectly fine!
I have a feeling this is slowly being rolled out.
Looking through the latest Android app binary, we can see they have a new streaming endpoint as mentioned in a post above:
I can connect to the streaming endpoint and get a `hello` response back:
Looking through the Android code, this is expected.
The interesting thing with this endpoint is you get a hello response back regardless of any authentication. Simply opening a web socket to is enough.
I'm starting to hit roadblocks in the app now as it's heavily obfuscated and I can't proxy the web socket.
My initial thought is that we need to send an authentication request once the socket is open, but this is as far as I have got so far.
I know it sends a timestamp as a ping, but I can't figure out the full JSON payload to send.
Has anyone else had a chance to look into this?
Firstly, it looks like some(all?) model 3 with recent software can no longer connect to:
Code:
https://streaming.vn.teslamotors.com/stream/$VEHICLE_ID/?values=speed,odometer,soc,elevation,est_heading,est_lat,est_lng,power,shift_state
What's interesting however is a model S running the exact same software as me (2018.21.9) also cannot connect to the old streaming endpoint, however I can to my model S on 2018.21.9 perfectly fine!
I have a feeling this is slowly being rolled out.
Looking through the latest Android app binary, we can see they have a new streaming endpoint as mentioned in a post above:
Code:
StreamingServerEndpoints={LOCATION_STREAMING:"streaming/",AUTOPARK_SUMMON:"connect/"}
I can connect to the streaming endpoint and get a `hello` response back:
Code:
wsta -v -I wss://streaming.vn.teslamotors.com/streaming/
{"msg_type":"control:hello","connection_timeout":0}
Looking through the Android code, this is expected.
The interesting thing with this endpoint is you get a hello response back regardless of any authentication. Simply opening a web socket to is enough.
I'm starting to hit roadblocks in the app now as it's heavily obfuscated and I can't proxy the web socket.
My initial thought is that we need to send an authentication request once the socket is open, but this is as far as I have got so far.
I know it sends a timestamp as a ping, but I can't figure out the full JSON payload to send.
Has anyone else had a chance to look into this?