Model 3 App and API

[Xtek]

First post in the Model 3 community. I'm looking for an owner of a Model 3 who'd be willing to help me document the Model 3 specific APIs. Once documented developers will be able to add functionality to their apps, voice assistant skills and sites. Right now these APIs are undocumented and are waiting with someone with a Model 3 and the know-how to document them.

Anyone with a Model 3 willing to help?

Here's a GitHub issue by the dev that maintains the current API documentation.
Model 3 APIs · Issue #52 · timdorr/model-s-api · GitHub

Feel free to PM if you'd rather have the conversation there.

 

[Xtek]

Disregard, found a way to fake my way into it.

 

[DS 5/15]

Cool, the land speeder edition Model 3

 

[Xtek]

Cool, the land speeder edition Model 3

Heh, yeah... still had my wheels set as AeroTurbine20. Not sure what the strings are for the Model 3 wheels, yet.

 

[kbecks13]

How'd you get access without a car tied to your account? I just configured a model 3 and keep checking to see if i can get into the app

 

[Xtek]

How'd you get access without a car tied to your account? I just configured a model 3 and keep checking to see if i can get into the app

You won't be able to until final paperwork is done after taking delivery.

 

[kbecks13]

Still need help documenting these API's? Give me a shout as i'd love to help out. Have the car and already can confirm that "charge_port_door_close" works similar to the opening command.

 

[Richk]

I'm willing to help too.

My own experience: I'd written a small logging script using teslajson.py for our prior MSs. When we took delivery of our M3, the new car became the zeroth index vehicle (self.vehicle = connection.vehicles[0]) and the S became vehicles[1]. It surprised me that the vehicle assignment to index had changed. Also, both times we changed vehicles, the API started working only around odometer mile 200.

The logger reads odometer, battery range, est_battery_range, charge_energy_added, outside_temp, and inside_temp. All those parameters are being retrieved for the M3 except est_battery_range, which is coming out as zeros each time. No errors, just zeros.

When/if I get some spare time, I can run the other parameters from Tim Dorr's API page, see which work on the M3.

 

[f8K37Sq31]

Looks like the estimated_range field for model 3 is always populated with 0. Does the car even report an estimated range as model s/x cars do?

 

[Xtek]

Looks like the estimated_range field for model 3 is always populated with 0. Does the car even report an estimated range as model s/x cars do?

It's not surfaced anywhere I'm aware of.

 

[f8K37Sq31]

It's not surfaced anywhere I'm aware of.

The fields are the same but estimated range is set to zero and the Ideal Range and Rated Range are set to the same number.
I wonder if Model 3 can even be configured to display the Estimated Range (vs Rated Range) as Model S/X can be configured.

 

[insaneoctane]

I'm just trying to get my Model 3 logging charging data and so far, so good. But, I tried to wake my car with the API and the "wake_up" command this morning and got 404. Anyone tried this? I can't get the charging data if it's asleep.....

 

[Coeus]

I'm just trying to get my Model 3 logging charging data and so far, so good. But, I tried to wake my car with the API and the "wake_up" command this morning and got 404. Anyone tried this? I can't get the charging data if it's asleep.....

Yup. It works fine for me using the URL

https://owner-api.teslamotors.com/api/1/vehicles/VEHICLE_ID/wake_up

Make sure you are using the correct vehicle ID. It's the "id" field in the vehicle list response *not* the "vehicle_id" field.

 

[AMIYY4YOU]

This is awesome! Tagged

 

[insaneoctane]

Yup. It works fine for me using the URL

https://owner-api.teslamotors.com/api/1/vehicles/VEHICLE_ID/wake_up

Make sure you are using the correct vehicle ID. It's the "id" field in the vehicle list response *not* the "vehicle_id" field.

Yeah, I made that mistake first and already corrected that!

I did find my issue though, I left out the PUT statement I had just copied and pasted my last successful script which was a GET. Simple fix and all is working!

 

[RyanDe]

This brings a whole new level to Tesla ownership!

 

[kablammyman]

i had no idea there was an api available for teslas. what cool things can you do with the api? Is it just monitoring\logging info, or can i rewrite what is the equivalent to air and fuel tables in an ICE's ECU?

 

[israndy]

Check out VisibleTesla for exploring the API

-Randy

 

[Tezlanian]

i had no idea there was an api available for teslas. what cool things can you do with the api? Is it just monitoring\logging info, or can i rewrite what is the equivalent to air and fuel tables in an ICE's ECU?

Remote APIs should be kept to bare minimum of what is required for reasonable remote management. Anything beyond that you should require local access.

 

[gadgetware]

Just got my car yesterday (M3) and I can't seem to get the API access to work. I was able to get a token using either a curl command or python script but when I try any of the other commands (e.g. vehicles) I get an "invalid token" error. Tried resetting my password and generated a new token but still no luck. I get the same error whether I go straight from the Tim Dorr site or via curl or python. Anyone else been able to get results with a new M3?