search

alandtse / tesla

Tesla custom integration for Home Assistant. This requires a refresh token be generated by third-party apps to login.
Apache License 2.0
599 stars 99 forks source link

Usage of unsuported APIs #1013

Open TomasCorral opened 4 months ago

TomasCorral commented 4 months ago

Hey

Not really a Feature Request but no other way to create an issue about it.

Does the plugin use any unsupported old API's like Owner's API if we use tesla http proxy?

Usage of old API's is forbidden and we can be banned for using both old and new API's

I tried to find any info about this but without any luck

skipishere commented 4 months ago

Currently the add-on can use either, this is because the fleet API is not available for some older models of cars. If you are using the Tesla proxy then it will be using the fleet API as a drop in replacement.

Not all cars have been forced to use the fleet API as yet (my 2003 model 3 still works with the older one) and given the uncertainty of what the free tier will look like + restrictive API limits I'm in no hurry to use the fleet API until I have to

In terms of banning, I hope they meant they'd return error codes of forbidden on the old API (when you can no longer use it) for now and then at a later date just ignore unsupported cars. Especially given the fleet API isn't yet aimed at general consumers (overly complicated to get working, needing to create a dev account, etc).

TomasCorral commented 4 months ago

So I am currently using Telsa proxy for 2 cars. My integrations is not making any calls via the old API and not breaking FleetAPI EULA right?

I read somewhere, but did not read the EULA myself, that by creating a FleetAPI developer account you can be banned if usage is detected o old API.

I was just making sure what to expect. But I agree, the new API is trash, the limits are very restrictive and it will get worse, to the point of being unusable. I love their cars tho but they have some policies I can't understand.