Model S REST API

[HankLloydRight]

Nevermind, I got it working now, thanks.

Almost nobody uses the mysql_* functions anymore, they're insecure and deprecated. You should think about updating the code to use mysqli_* functions.

 

[HankLloydRight]

Ok, I've got it working and getting a token.. it tries to get charge state and is failing in queryTeslaAPI

https://owner-api.teslamotors.com/.api/1/vehicles/97/data_request/charge_state
returns:
{"response":null,"error":"not_found","error_description":""}

Any ideas?

 

[Prefect]

Almost nobody uses the mysql_* functions anymore, they're insecure and deprecated. You should think about updating the code to use mysqli_* functions.

That should be your job, that's why I uploaded the code!

is there a dot in the url? "/.api/ ? That would be wrong.

 

[HankLloydRight]

That should be your job, that's why I uploaded the code!

is there a dot in the url? "/.api/ ? That would be wrong.

Thanks, that's probably the problem, not sure how that got in there.

I may re-factor the code and share.

 

[Prefect]

I may re-factor the code and share.

That was the plan Try to get the commands working! That would be awesome!

 

[HankLloydRight]

That was the plan Try to get the commands working! That would be awesome!

Yes, your code is a great start! Just what I was looking for to augment my existing web app LogMySC.com with some automation of grabbing the current mileage and temperature and energy usage instead of the user having to input it manually.

I'll also translate it to English while I'm at it. All the SQL works unchanged, it's just the mysqli_ calls and return values that needed to be changed.

The only problem I had was figuring out the VEHICLE_ID variable. When you list out the vehicle info, there are two IDS: "id" and "vechicle_id". Turns out for the subsequent API calls, you need to specify the "id" value in the URL, and NOT the "vehicle_id" value. Somewhat confusing when the API calls for "vehicle_id".

 

[haunsman]

Does anyone know a good weather widget that can implement easily with this api? Im looking to close the roof when it is supposed to rain,

 

[HankLloydRight]

The weather underground had a pretty good APi with lots of free calls everyday.

I used it for local temps for LogMySc.com, but I'm now switching to the tesla api for local car tenp.

 

[Prefect]

When you list out the vehicle info, there are two IDS: "id" and "vechicle_id". Turns out for the subsequent API calls, you need to specify the "id" value in the URL, and NOT the "vehicle_id" value. Somewhat confusing when the API calls for "vehicle_id".

Interesting find! I already thought that this has to be the error I made for issuing commands to the car. But I already was using the longer "id" instead of the shorter "vehicle_id". Actually the shorter "vehicle_id" also works, at least for all request type calls.

If you get the php or jscript code to issue commands working, let me know! I was not able to get that to return anything other than "404".

 

[haunsman]

The weather underground had a pretty good APi with lots of free calls everyday.

I used it for local temps for LogMySc.com, but I'm now switching to the tesla api for local car tenp.

Thank you!

 

[HankLloydRight]

Two API questions.

1. It seems like about 50% of the time, the climate state returns null for outside and inside temps, while charge_state returns are pretty stable. Is this normal?

2. From the available API values returned in charge_state, how can I estimate how many kWh are left in the battery? I think it currently reports %SOC, but for my app, I want to measure the energy used between two readings. I could take the 85kWh rating of the battery and multiple by the %SOC, but is that accurate? What are other people using? It also looks like there's a constant multiplier of about 2.488 between %SOC and the rated range remaining.

 

[SG57]

Two API questions.

1. It seems like about 50% of the time, the climate state returns null for outside and inside temps, while charge_state returns are pretty stable. Is this normal?

2. From the available API values returned in charge_state, how can I estimate how many kWh are left in the battery? I think it currently reports %SOC, but for my app, I want to measure the energy used between two readings. I could take the 85kWh rating of the battery and multiple by the %SOC, but is that accurate? What are other people using? It also looks like there's a constant multiplier of about 2.488 between %SOC and the rated range remaining.

You want the delta-kWh between two charge state readings? Could you calculate the delta between `battery_level`s , then convert from battery_level % to kWh depending on the battery size? (5% drop in battery level is a lot more on larger battery packs)

 

[HankLloydRight]

You want the delta-kWh between two charge state readings? Could you calculate the delta between `battery_level`s , then convert from battery_level % to kWh depending on the battery size? (5% drop in battery level is a lot more on larger battery packs)

Yes, thats what I want to do and was asking if that's the best way to do it. Is it? How to accurately convert bsttery_level to kWh... Is it just size(85)*%soc?

 

[HankLloydRight]

Oh and I solved the first issue.. In order to get temp readings, the climate control must be turned on, otherwise they return null.

 

[HankLloydRight]

Can anyone else access the Tesla API today? Nothing I do gets a response. Can't even request a new token.

It worked great yesterday, but today, it suddenly stopped working. The Tesla mobile app still works sometimes, but Remote S does not.

 

[markb1]

Can anyone else access the Tesla API today? Nothing I do gets a response. Can't even request a new token.

It worked great yesterday, but today, it suddenly stopped working. The Tesla mobile app still works sometimes, but Remote S does not.

It stopped working for me early this morning. I've been getting "502 Bad Gateway".

The official Tesla app reports no errors, but seems to be displaying stale information. Edit: Actually, the app seems to be working. So maybe I missed some change to the API? Did the server change at some point?

 

[HankLloydRight]

Great, thanks. At least it's not just me. I had one free day to flush out my app changes and now I can't even access the API!

Will have to wait until after Connect.

It just took me four tries to get the climate turned on in my car through the Tesla app (internal temp was 109!).

 

[markb1]

It just took me four tries to get the climate turned on in my car through the Tesla app (internal temp was 109!).

Ok, that lends credence to the the theory that it's all on Tesla's end. Every once in a while, a request goes through, I guess. My script had been working on and off starting at 4:00 AM PDT, but it hasn't been working at all since 8:45 AM. It runs every 5 minutes.

 

[markb1]

It seems to be working again. My script has been succeeding consistently for about the last two hours.

 

[HankLloydRight]

Same here, working pretty well.... except that for most of the afternoon, I had farked one of my scripts with a stupid debug code bug that caused the auth to keep failing. But once I fixed that, all is good now.