Tesla Owner API Tutorial (All you need is your browser)

[Byshop303]

Wait ... I spoke too soon ... my car version is 2017.42 so you still might be right ... I guess I would know in the next update :|

I was just about to ask that. It appears to be as of "46" and up. The schema changes were significant enough to break the Dashboard for Tesla application. The developer updated it today to accommodate the newer firmwares.

 

[Byshop303]

Here's a comparison of the output between 42 and 46.8.

 

[Akrion]

Here's a comparison of the output between 42 and 46.8.

Great info! Thanks. So not nice for Tesla to remove those flags ... if anything we need more info on these cars via their APIs than less!

 

[ccdisce]

Great info! Thanks. So not nice for Tesla to remove those flags ... if anything we need more info on these cars via their APIs than less!

Maybe we should now be looking at ''PT_BMS_ISENSORPROTOCOLNUMBER' has to be greater than 3"
as mentioned in thread #215

Any news on 100D uncorking?

 

[Akrion]

Maybe we should now be looking at ''PT_BMS_ISENSORPROTOCOLNUMBER' has to be greater than 3"
as mentioned in thread #215

Any news on 100D uncorking?

OK where is that value coming from? Which API is returning it?

On the slightly different topic ... can anyone provide API responses for Model X? Do we have documentation similar to the one Tim did for Model X? I would imagine it would have some different API points etc?

Asking since I am trying to experiment with an app and would like to know how generic it could be ... having "only" Model S is a limitation ... Any help is appreciated!

 

[appleguru]

OK where is that value coming from? Which API is returning it?

On the slightly different topic ... can anyone provide API responses for Model X? Do we have documentation similar to the one Tim did for Model X? I would imagine it would have some different API points etc?

Asking since I am trying to experiment with an app and would like to know how generic it could be ... having "only" Model S is a limitation ... Any help is appreciated!

It’s not exposed on the owner API. Is a CAN signal.

 

[Jonas_man]

OK where is that value coming from? Which API is returning it?

On the slightly different topic ... can anyone provide API responses for Model X? Do we have documentation similar to the one Tim did for Model X? I would imagine it would have some different API points etc?

Asking since I am trying to experiment with an app and would like to know how generic it could be ... having "only" Model S is a limitation ... Any help is appreciated!

should be the same.

But model 3 must have some new commands as the app can now open and close the trunk

 

[Akrion]

should be the same.

But model 3 must have some new commands as the app can now open and close the trunk

Are you sure? One variable I wonder if it would be the same is the actual `vechicleId` ... in model S it is `id_s` ... you sure it would be the same with Model X?

 

[Jonas_man]

Are you sure? One variable I wonder if it would be the same is the actual `vechicleId` ... in model S it is `id_s` ... you sure it would be the same with Model X?

im not sure. But it *should*
id_s in my guessing means: id_string

 

[ccdisce]

It’s not exposed on the owner API. Is a CAN signal.

Do you know the CAN message that is required to get this information and which CAN bus to use?

 

[appleguru]

Alright, so did a little bit of CAN logging to see if I could find the PT_BMS_iSensorProtocolNumber signal on the powertrain bus.

Looks like it is message ID 532, and the values are static:

Byte Number:
0: PT_BMS_iSensorMajorVersion
1: PT_BMS_iSensorMinorVersion
2: PT_BMS_iSensorProtocolNumber
3: PT_BMS_iSensorReleaseVersion
4-6: PT_BMS_iSensorSerialNumber

Should be possible to read this value from your car using TMSpy or similar CAN logging app and appropriate cable/dongle.

If the above referenced support emails are to be believed, this is the magical component that makes some 75D cars eligible/not eligible for uncorking (a PT_BMS_iSensorProtocolNumber greater than 3 is required for uncorking).

Does anyone know what part this actually is on the car? Perhaps a current sensor somewhere?

Do you know the CAN message that is required to get this information and which CAN bus to use?

75 and 75D variants increased performance from July 1st - software and hardware improvements?

 

[ccdisce]

75 and 75D variants increased performance from July 1st - software and hardware improvements?

Thanks for the link to your post on the "75and 75D....." thread.
Time to go look around on the powertrain CANbus.

 

[ccdisce]

applguru,

Logged this from the CAN3 bus yesterday for ID 532

Byte Number:
0: PT_BMS_iSensorMajorVersion 0x01
1: PT_BMS_iSensorMinorVersion 0x03
2: PT_BMS_iSensorProtocolNumber 0x05
3: PT_BMS_iSensorReleaseVersion 0x00
4-6: PT_BMS_iSensorSerialNumber 0xe9 0xd7 0x24 0x00

car fw is .42....the answer to everything

 

[Akrion]

42....the answer to everything

Priceless

 

[Yoonoo]

Poking around the REST API, I was able to find the new location for perf_config for cars running version 2017.46 and above. It can be found under "data_request/vehicle_config" instead of "data_request/vehicle_state" for previous versions.

 

[jjanov79]

Poking around the REST API, I was able to find the new location for perf_config for cars running version 2017.46 and above. It can be found under "data_request/vehicle_config" instead of "data_request/vehicle_state" for previous versions.

How do you execute this command from apiary.io since there's no button for that in the Console?

 

[Yoonoo]

How do you execute this command from apiary.io since there's no button for that in the Console?

I'm not very familiar with Apiary, but I would imagine that whoever published the API on Apiary has to add the vehicle_config resource.

Another option would be to use Apiary to generate the cURL command line for vehicle_state then manually replace vehicle_state with vehicle_config and run it locally on your computer.

 

[jjanov79]

I searched through the threads here but all I was able to find was a little bit too technical IMO for the average user and the step by step how to was not really there. I love the fact that Tim did the Apiary.io documentation and wanted with just the browser to walk through an example of how to get your Tesla's vehicle state etc.

I ended up actually doing this step by step for myself and that is how I found out that my "uncorking" was not done although my car was 2 months ago with Tesla of West Palm Beach for that exact purpose. So I have a real life example how this helped me.

Obviously, you can go like 10 different ways to get to the API and work with it but what I really liked with the Apiary.io was that all you need is just the browser so anyone can quickly do it without any other tools like Postman etc.

In any case, hope this is useful to the community and my apologies if it was done already. I did not find much on YT on the subject.

PS. There are few issues in the video like the Content-Type header param etc but overall it should suffice for the average user to follow and get data for their vehicle out IMO.

Because "vehicle_state" no longer displays performance info how do we go about getting "vehicle_config" from Apiary.io? That being said this would need to be for those of us who aren't programmers but can follow directions like in the video.

 

[BTCTM3]

Poking around the REST API, I was able to find the new location for perf_config for cars running version 2017.46 and above. It can be found under "data_request/vehicle_config" instead of "data_request/vehicle_state" for previous versions.

Well would you look at that - calling this on a model 3 shows:

"plg": null,
"rear_seat_heaters": 1,
"rear_seat_type": null,
"rhd": false,

Among some other data...

 

[oddarneroll]

Confirmed that this is removed from the latest firmwares. I took my car in for uncorking and literally watched it happen. I kept a PowerShell script queued up on my phone via RDP to query the status of my car as they were working on it. They uncorked it first, which my script confirmed, and then they updated me from 42 to 46.8 at which point my script stopped working. I don't suppose anyone found a new location in the API response for this same info?