Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Higher Limits for Open-Source Applications #189

Open
SebastianGode opened this issue Jul 9, 2024 · 3 comments
Open

Higher Limits for Open-Source Applications #189

SebastianGode opened this issue Jul 9, 2024 · 3 comments

Comments

@SebastianGode
Copy link

With the introduction of the new Open-Source category for projects I'm a bit shocked that those projects still have the same limits as the discovery plan and that there's no way to even upgrade them.
https://developer.tesla.com/docs/fleet-api#2024-07-08-open-source-support

Overall I think Tesla benefits from the Open-Source community and many owners just want e.g. some driving stats of their vehicle. They don't want to make money from it.

I would really like if the OpenSource tier can get higher API limits than the DiscoveryPlan. I understand, that the API usage also isn't free to run and that Tesla of course needs to charge big companies for using it, but in my opinion the amount of Open-Source apps like Teslamate really should still be usable with the new Streaming-API. If you don't offer options to pay for the API, please at least increase the limits a bit so that it still is possible to run such loggers.

TLDR: I really would like to have a separate plan for Open-Source applications with higher limits than the default DiscoveryTier for companies.

@Bre77
Copy link

Bre77 commented Jul 10, 2024

Firstly, thank you for raising this issue and making me aware Tesla had added this new open source category.

I have implemented the OAuth flows in Home Assistant and the rate limits are making it rather useless indeed. For some reason even polling every 5 minutes was still being rate limited, and I think I can't even have the whole interaction start up at once because it takes 4 API calls for 1 vehicle and 1 energy site, which also gets me blocked. (Products, vehicle_data, site_info, live_status)

I also don't know how command signing is meant to work but I'll raise that issue separately.

EDIT: This turned out to be an issue with having multiple "applications" under the same developer, and will not be an issue so much when my paid application moves to a paid tier.

@netdata-be
Copy link

I also believe that this will be the end for projects like teslamate :-(
The rate limit on the API is actually OK if the limit of the Telemetry would be higher.
Currently the undocumented web socket API is nearly realtime, the current discovery tier is 10 items / min which is really limited and not enough to achieve the same as we currently have with the owners api in conjunction with the websocket streaming.

Any suggestions from Tesla side on this?

@juergen852
Copy link

juergen852 commented Aug 8, 2024

Main reason for me buying a Tesla is free Software like Teslalogger .

If API remains restricted like this, there are many reasons for buying at VW, Audi, BMW in Germany....
Like much better lane assist, auto parking into garage, autopilot at more than 140 km/h, autopilot adapting speed to recognized speed limits, no phantom breakings, better ventilation distribution, more luxury feeling inside, and so on....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants