Consider Telsa's official third-party access "Sign in with Tesla" scheme
k8stone opened this issue · comments
I have so far avoided getting an access token through any of the various sketchy means I've seen, but it seems like Tesla is finally providing an official path for apps to register for an authentication token which the owner can revoke if desired from their Tesla account. Details are thin on the ground, but at least one such app has appeared as of today:
https://teslanorth.com/2023/08/08/first-sign-in-with-tesla-third-party-app
Official documentation on how to participate with the formal SDK has finally been published.
Wow, that's great!! I'll investigate this and hopefully it will fix the "too many requests" problem.
Any update on the "too many requests" problem?
Hm. I am looking at their website and it's very business-centric. It seems like they are just testing the waters here. They are saying "free for now" and the way they describe everything is for "business fleet management". Also the API rate limits are extreme:
One API request per car per 5 minutes is … unworkable. Anyone have a different read on this?
Oof, that definitely seems unworkable. Are we hitting a rate limit right now with the "too many requests" message?
It appears so, yes. And the worse news is they have officially deprecated the REST API (which this and every other Tesla app in the world uses) and it will stop functioning in early 2024. The only way forward is this new "Tesla Vehicle Control" API and no one knows how much it will cost, or if there will be an open-source free version to use on your own vehicle or what. It's a complete mystery.
Does that mean this plugin officially no longer works now then?
Unfortunately so, there's a note at the top of the Homepage/README explaining the same.
according to its documentation, Telsa doesn't want us to pull vehicle data, instead they want to push it through webhook. but this will not work with homebridge unless someone can host a proxy service to receive these pushes and store them for query, or we need to register a developer account and setup our own server.
ref: https://developer.tesla.com/docs/fleet-api#fleet-telemetry
@nfarina im trying to uninstall your Tesla app and I keep getting half way and it says it’s Unable to uninstall. Any tips?
Will there be an update to get this working? Is it possible at this stage?
Unfortunately Tesla hasn't provided any new information yet. I'm hoping they announce some kind of "personal plan" where you can send unlimited requests to your own vehicle without paying them. Anything else won't be feasible.
Unfortunately Tesla hasn't provided any new information yet. I'm hoping they announce some kind of "personal plan" where you can send unlimited requests to your own vehicle without paying them. Anything else won't be feasible.
Thanks for the information. Good Job btw with this and Homebridge in general 💯
@nfarina I was wondering if it would be feasible to use Teslamate (which still works) to get the job done? My guess is that once could also leverage this other project (https://github.com/tobiasehlert/teslamateapi) to avoid using the official API?
I currently have homebridge and Teslamate both running on the same linux box. This API could be just an extra requirement that seems pretty straightforward to setup.
Also, FWIW, the Tessie API works, and it has most of the endpoints needed I think. There is a $5/month subscription as I recall. Personally I would be willing to subscribe to have the Tesla/Homebridge world back in my life 👍.
FYI I've recently moved to Home Assistant for my home automation, and learnt that it can do everything that HomeBridge does (and more), as I now use it to bridge non-supported accessories into Apple Home instead.
Crucially, it has a working HACS integration for the Tesla API (little bit more work to get setup) and can bridge accessories through to HomeKit just like HomeBridge does.
It may seem intimidating but if you're technically minded enough to mess about setting up HomeBridge on a Raspberry Pi just to integrate devices into HomeKit, you can get HA setup instead and you'll get WAY more out of it.
according to its documentation, Telsa doesn't want us to pull vehicle data, instead they want to push it through webhook. but this will not work with homebridge unless someone can host a proxy service to receive these pushes and store them for query, or we need to register a developer account and setup our own server. ref: https://developer.tesla.com/docs/fleet-api#fleet-telemetry
Can't you use something like zapier or add on some sort of rabbitMQ broker to your PI to capture the requests ?
So does this application have the same problem?
https://github.com/teslamate-org/teslamate
I've forked this repo and plan to make it support Tessie and Teslemetry, which are paid subscription based products that provide access to the new Fleet API. I integrated both of these into Home Assistant already.