Yes, I saw traffic over OpenVPN, but such traffic is not visible by anyone (encrypted), so I'm not sure how wk057 could have accessed it. Oh well. Let's just see if Tesla makes it available.
Model S REST API
- Thread starter timdorr
- Start date
-
- Tags
- Model S User Interface
HankLloydRight
No Roads
wk057 (and a few other people) have root access to the car, so they can reverse engineer the calls, as well as make their own calls through the VPN and retrieve and export the data.
Has anyone here figured out the syntax for summon? I'm trying to make my own code to use summon (just for fun) but I'm hitting a brick wall. Can someone give me some pointers on what I need to send to the server using websockets and how to format it?
Thanks.
Thanks.
Had to stop fiddling with this because of work so now just picking this back up. Does anyone know if AWS is still blocked? I messed with my code so much before I found the forum and saw others were having trouble that I'm not sure if my code timing out is my fault or it's just an AWS problem. Thanks!
tliving
Member
AWS is still blocking or blocked (not sure which end). Use a proxy or relocate the code.
GlmnAlyAirCar
Active Member
Obviously you're not using summon correctly!
Have you noticed that the API often reports incorrect heading? It's typically off by either 90 or 180 degrees. I noticed that Tesla app also initially shows the incorrect heading for the car (the same one that the API reports) and then corrects the heading. All 3rd party apps that I have tried are affected by this.
response = {
"gps_as_of" = 14906975;
heading = 191;
latitude = "xx.981397";
longitude = "-xx.238153";
power = 1;
"shift_state" = "<null>";
speed = "<null>";
timestamp = 1490056976311;
};
response = {
"gps_as_of" = 14906975;
heading = 191;
latitude = "xx.981397";
longitude = "-xx.238153";
power = 1;
"shift_state" = "<null>";
speed = "<null>";
timestamp = 1490056976311;
};
HankLloydRight
No Roads
If speed is zero, that's what I'd expect. It needs velocity before it can calculate heading. Even with accurate GPS, you can get an accurate fixed location, but no heading without movement.
AllenWong
Member
I actually tend to find the heading to be correct most of the time. It's usually the heading of the direction, and not where the front of the car is facing. I have a parking spot that I have to back into, and the heading is always correctly pointing towards the back of the car after I park, because that is the last known direction I was heading.
HankLloydRight
No Roads
But I think with subtle GPS drift while the car is parked (or say inside a garage with limited GPS signal), it could get the last correct heading confused if it thinks the car moved a little bit. Most of the time my car is parked in the garage, and that shows in the app. But once in a while it's parked in the back yard.
That's true if the car doesn't have a magnetometer (as most phones do these days).
The fact that Tesla app gets the heading right every time, leads me to believe that Tesla computes the heading using a magnetometer sensor whose output is not available through the API.
It is still strange that the heading reported by the API when the car is stationary, is off by 90 or 180 degrees (when it's reported incorrectly) not by a random offset.
The UK cars and US cars have different names for display settings of range
Dropbox - Monday, Mar 20
Dropbox - Monday, Mar 20
Based on some limited data that I've seen, the following (strange) relationship holds. Has anyone else come across this?
US version EU version
——————— ——————
Rated Typical
Ideal Rated
Dropbox - Monday, Mar 20
Dropbox - Monday, Mar 20
Based on some limited data that I've seen, the following (strange) relationship holds. Has anyone else come across this?
US version EU version
——————— ——————
Rated Typical
Ideal Rated
Looks like Tesla is allowing requests from AWS now. Not getting any failures since yesterday 6pm PDT.
Oh good. I'll try my Alexa skill tonight. BTW, is anyone else seeing this in climate_state:
is_front_defroster_on: 3
is_front_defroster_on: 3
Yep, it was originally some MITM proxy watching. Then I just decompiled the Android APK. In the new React Native version, they actually have a JSON file with all the endpoints listed: Tesla API Endpoints · GitHub
BTW, that shows a new /data endpoint. That gets a combination of all the *_state endpoints so you can get all that info in one call instead of 5
Handy Gist - but it looks to me like /oauth/revoke does not work. Has anyone successfully used it?
Using the Tesla API, how can we tell whether a vehicle is a Model S or a Model X? Will a Model X have an option code like MX01 instead of the Model S's MS01?
HankLloydRight
No Roads
The option code is MDLX for Model X. If it doesn't have MDLX, it's a Model S, as there is no matching MDLS code, but rather several codes MS01, MS02, etc.
I see
"is_front_defroster_on":null
I don't think I've seen
"is_front_defroster_on":3
But I don't think I've tried it with the front defroster on. My car is currently in service, but when I get it back I check with different settings. I'm still hoping for a way to control the rear seat heat from the API. Having to ask the driver to adjust your seat heat is silly.
Last edited:
Thanks! I tried mine today and it's working. Back to being lazy
Similar threads
