-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Getting daily production from Tesla Gateway API
- Thread starter S3anB
- Start date
I read the article. It was not "hacked third party appS" it was " Found people who had used Teslamate, which is a SELF HOSTED tool, who had set it up incorrectly (likely not changing default passwords)".
I dont use any third party apps to access my car, but these were not the issue, this was a "self own" from people using a self hosted tool and not setting it up correctly, but of course the story is "Teen hacks teslas!"
I patched the data holes by downloading from the app for those days which was tedious and the resolution is in 100 watt increments so I'm likely to be off a few percent for those days unless they are leveling between the 5 minute increments with carryover and carryunder NOT to cross one hour boundaries.
Make sure you're using UTC with the dates:
Python 2.7:
url = ('https://owner-api.teslamotors.com/api/1/energy_sites/'
+ SITE_ID
+ '/calendar_history'
+ '?kind=time_of_use_energy'
+ '&period=' + period
+ '&start_date='
+ datetime.strftime(
s_date.astimezone(pytz.utc),
'%Y-%m-%dT%H:%M:%SZ')
+ '&end_date='
+ datetime.strftime(
e_date.astimezone(pytz.utc),
'%Y-%m-%dT%H:%M:%SZ')
)
Can you turn that into sample URL minus your token so that I can curl it. I'm using UTC times with Z on the end of the date/time string. Same as I'm using for end_date with kind=power.
So this is using a start_date in local (Pacific) date/time Jan 12, 2022 00:00:00 and an end_date in local (Pacific) date/time Jan 12, 2022 23:59:59 then converting it to UTC into the URL below:
https://owner-api.teslamotors.com/api/1/energy_sites/<SITE_ID>/calendar_history?kind=time_of_use_energy&period=day&start_date=2022-01-12T08:00:00Z&end_date=2022-01-13T07:59:59Z
Bummer... not that the tokens are longer, but they only last for 8 hours. Can you still use refresh tokens to generate new access tokens? That's easy enough to script. But the full reauthentication to generate new tokens is a pain due to the Captcha.
Yep. That lousy 100W resolution is what motivated me to learn the Tesla API and write my own scripts to get the data at full precision. Also to have the ability to retrieve any day's data at whim, rather than manually scrolling through days in the App and clicking "Download my data".
It's not 8 hours. Someone thought it was because they renewed and then 8 hours later it was expired but that's because tesla expired them due to an "event".
Oh yeah, that's a daily summary. For the 5 minute increments I use: /powerhistory but that only gets the previous day. There must be an endpoint that you can query for a particular day because it's available in the app.
Yes though it's a bit different than before:
Python:
url = 'https://auth.tesla.com/oauth2/v3/token'
payload = {
'grant_type': 'refresh_token',
'client_id': 'ownerapi',
'refresh_token': REFRESH_TOKEN,
'scope': 'openid email offline_access'
}The response is a bit different too.
Though I don't use calendar_history, kind=power, I played around with it and I was able to get data for period=day in 5 minute increments. Oddly enough nothing came up for Dec 9 but Dec 10 had values. Here's what I used:
local = pytz.timezone(TIME_ZONE)
date = local.localize(datetime(
date.year,
date.month,
date.day,
23,
59,
59,
0
), is_dst=None)
url = ('https://owner-api.teslamotors.com/api/1/energy_sites/'
+ SITE_ID
+ '/calendar_history'
+ '?kind=power'
+ '&end_date='
+ datetime.strftime(date.astimezone(pytz.utc), '%Y-%m-%dT%H:%M:%SZ')
+ '&period=' + period)
Tomorrow afternoon, Dec 10th will also vanish. But everything from November and before still appears. It's some sort of december only data hole.
Hmm… I have data for both those days downloaded via the API, but 28 Nov has no data for me.
If you scroll back in the App is it there?
If this is something that really annoys you, you could write a script to poll the site status and record whatever data you want, and run it every 5 minutes via a cron job. I do that to record battery capacity and charge state (%), since the App &/or calendar_history endpoint only provides battery charge level every 15 minutes not 5, and does not return battery capacity at all.
You do, however, get missing data with that method too, since Tesla occasionally takes the backend offline presumably for maintenance updates for 10-20 minutes in the middle of the night USA time (which is afternoon for us) and no data is returned during those periods.
But during those periods the Gateway will still record data and upload it to the servers once it comes back online. So it is possible to stitch together a pretty complete set of data using both methods.
I'm having trouble generating a new access token from the full 4 step login process outlined on this page:
Authentication | Tesla JSON API (Unofficial)
The authentication process for the Tesla API
tesla-api.timdorr.com
Has Tesla changed this as well? It fails at Step 2. I do the login and get the Captcha at Step 1, but Step 2 to obtain an authorisation code returns
Access Denied
You don't have permission to access "http://auth.tesla.com/oauth2/v3/authorize?" on this server.Yeah this changed a few months ago and I stopped trying to keep up with all the changes, relying on the refresh token. There's a long list of discussions on Tim Dorr's Github with varying solutions.I'm having trouble generating a new access token from the full 4 step login process outlined on this page:
Authentication | Tesla JSON API (Unofficial)
The authentication process for the Tesla API
Has Tesla changed this as well? It fails at Step 2. I do the login and get the Captcha at Step 1, but Step 2 to obtain an authorisation code returns
Access Denied
You don't have permission to access "http://auth.tesla.com/oauth2/v3/authorize?" on this server.
Similar threads
