And bam, officially documented secure API access. Tesla Fleet API
Temporary free ‘Discovery’ tier limits, with new tiers to come next year.
And on GitHub - GitHub - teslamotors/vehicle-command
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Charge HQ
- Thread starter m4rtin
- Start date
And bam, officially documented secure API access. Tesla Fleet API
Temporary free ‘Discovery’ tier limits, with new tiers to come next year.
And on GitHub - GitHub - teslamotors/vehicle-command
israndy
Supercharger Hunter
I'd say the developer pays, not the user authorising it.
Some limits are definitely per car - but the larger limit is per app I'm assuming, or maybe it's per Tesla developer account - would make sense to pay for tiers per developer account rather than by app (not per 'user' or Tesla account....).
| Commands limits | 50 API requests / car / day And 500k API requests / day |
So you could have 10,000 cars making 50 requests a day with the current Discovery tier
Interesting that it mentions API call limits per car per day, but no mention of API call limits per Powerwall per day (other than the umbrella limits per day). Probably because Powerwalls are not cellular connected.
israndy
Supercharger Hunter
Looks like some cars are already being affected by this,
From the Charge HQ website - How will the new official third party Tesla API impact Charge HQ?
The latest update from Charge HQ is "stay tuned" - though Tesla still haven't announced their future developer API tiers, at least not publicly yet - there's no suggestion of any changes to pricing charged by Charge HQ for it to do it's thing.
As expected, Charge HQ is (finally) kicking the early testers off of their 'free' plan, as Tesla are going to charge for API access.
From Charge HQ - Annual Payment Option Paused for New Users
Last edited:
israndy
Supercharger Hunter
Why is it so expensive? is the ONLY way to control our car's charge speed via this API and TESLA is charging that much for said access? It destroys the savings I get by charging with only solar, which was the point of having the Unofficial API charge the car with solar, to save money. I had my TesSense app that did what Charge HQ did, but when the API broke I was fortunate to have the same functionality for my wife's Mitsubishi iMiev in the app via smart plugs and I just fell back to using it for the Tesla too, at 120 volts. Slow, but still solar only.
Punchbuggy
Member
Yeah, I received that advice too as an early adopter. $5 a month isn't a lot, but I've a Powerwall so I'll continue to run with the Tesla Charge on Solar and see if they improve it in the meantime. I need to override it occasionally as it doesn't have the same smarts as ChargeHQ, so I may yet change my mind.
israndy
Supercharger Hunter
The unofficial API still has some functions that work, but charging control isn't one of them. Most apps have moved to the new Tesla API, but do they really have to pass the $5/mo on to Tesla, that seems CRAZY for accessing our own cars. I don't actually know what it costs to use the API, but I do have 6 apps that I haven't been forced to start paying for that use the new API. Just don't handle solar charging
It’s actually $7/ month! Shows as $5 but that’s in USD.
Oh OK, I haven’t tried to control the charging on my Tesla since CoS became available. Are all charging functions dead (e.g. cannot even start or stop a charge using the Owner API) or only some charging functions (e.g. varying the charge rate)?
My PW2 scripts all still work.
Tesla just needs to provide a toggle on CoS so that you can either prioritise the car charging, or the PW2 charging, then I’d have no need for my own scripts at all. At present, I manually turn CoS on only when my PW2 has filled up.
jgleigh
Member
Tesla hasn't even announced API pricing yet. The developers are jumping the gun a bit.
Similar threads
