You have a Tesla developer account where you can check your usage.
If you get an alert now, your car is awake a long time during a day and data is requested. Data calls are only done/counted if the car is awake.
To prevent API usage for data readings, you can increase the interval in car device settings (e.g. 15min).
He is red now, next month again. I set it to 5 minutes. At night, it is set to 1 minute. This can also be set to 5 minutes, or does that not make a difference?
The data requests are only counted if the car is awake. So if the car sleeps at night (and is not charging or Sentry active) then it doesn’t matter.
hi @RonnyW, I created a developer account and added the ‘Homey’ app as you’ve described. Then I deleted my previous car within homey and am trying to add a new car. But it get’s stuck after providing the API credentials. Am getting a 403 ‘Forbidden: unauthorized missing scopes’ but I am 100% sure that the scopes were added, as you’ve described. See screenshots. Any idea how to get this fixed?
Did you create a developer account with another eMail?
Then clear browser cookies for tesla.com and then pair your device.
Then you can use the other account to login and pair.
Btw…deleting the car is not needed. Just repair in device settings.
hi @RonnyW should the developer account be created with a different email address than my regular Tesla email address? I used the same address for both. So please let me know.
Same here. I think the European accounts (I created a EU one with euros instead of the ones with dollars) is more expensive. I have 500 requests per euro with a 10 euro range. So I’m also already through the whole budget. Didn’t have this issue last month… 
For now created the following flow, hope that saves some calls when the car is (fast)charging.
There is no difference. Using the same eMail makes is easier to login without deleting cookies every time. And you can directly switch from car view to developer view.
If you registered the app and your Homey to an app id, you are locked in. The app id is bound to your Homey (and it’s URL).
Sorry, can’t read. Data request are more expensive then the other one…
Hi @RonnyW,
For me, the email I used for developer and regular tesla are the same.
I also followed your recommendation and deleted the cookies from my phones browser and tried to re-add the vehicle in Homey. But I am still getting the same error as in my previously uploaded screenshot. Any advice how I can get this fixed?
Your screenshot is from Tesla developer area (app details/scopes)?
Look good so far.
While pairing, did you get the auth popup with login (email/2FA) and scope selection?
If this was cached because the app was already added from a first try to your account, you won’t see scopes selection again.
Please go to your car account. Under “Security”, you can open the “3th party apps” section.
There you can manage the HomeyApp access to your car account. Please check if you set the scopes there (1st login in Homey app with your car account).
If that also doesn’t work, just remove app from your account. Then pair again. You should get again the login popup and scopes selection.
Tesla car account should look like this:
Thanks again for this great app! Together with Google Home I can now talk to my watch like Michael Knight and open the trunk!
Just as idea…
I use the charge state as trigger.
If connected and cable type is IEC (AC charging), then use a higher interval.
If disconnected, use standard interval.
I have to check what cable type is shown for SuC charging. If anyone is at a SuC next time, please share the cable type 
My target is to set a data saving interval while AC charging while at a SuC the standard interval should be used instead.
And if i´ve tried all of that but it doesnt work anyway… Get the “400bad gateway” thing still.
I´ve gotten a dev account, updated 3rd party app and reinstalled the app in homey.
Do you have a screenprint on what data should be put in under the 3rd part?
The 3th party app settings in your car account should look like this:
Also got your log (with 400 error). I can see you set your eMail as client_id. That’s wrong.
Use the client_id and client_secret from your developer account:
First is the client_id. Second is the client_secret (you can copy it after making it visible with the “eye” icon).
I think am getting the url and uri wrong. What should I write there?
Skickat från min iPhone
Silly question perhaps, but is there a difference between the hardware versions and the functionality supported by the app? I have a model S that is almost 8 years old, and while I was able to set everything up, the app shows me the current charge level of the battery, it does not show me any options to open/close the charge port, or to stop/start charging or set the charge level or speeds. In the developer API, I have enabled all car related functions, and only left the two energy product ones unchecked since I don’t have any of those products. I have the old tesla wall connector that doesn’t have wifi, so I’d very much like to just start and stop the charging by communicating with the car, but I’m puzzled slightly why not all options are showing up, and would appreciate any pointers since my searches so far have come up pretty much empty. 
Did you add the battery device?
In addition to the car itself, there are some devices for additional functionality - It’s splitted into several devices to get related data i än different device sensor views and to group flow by device.
The URLs to include in developer app details are shown in pair view (you can copy by clicking on it).
Or follow the instructions:
