Comments (22)
I think we're done here! This will very likely mean the end of this project and usage of the API outside of sanctioned projects. I guess we'll stay tuned as they publish more things.
@timdorr I would like to thank you for all the work you have done bringing the unofficial API to the masses, I know I utilise it's befits every day.
I would also like to think that your work here has helped Tesla bring forward a documented and supported API as they have been able to see the befits of a third party eco system.
from tesla-api.
https://developer.tesla.com/
https://developer.tesla.com/docs/fleet-api
I think we're done here! This will very likely mean the end of this project and usage of the API outside of sanctioned projects. I guess we'll stay tuned as they publish more things.
from tesla-api.
It only took 10 years! (e9a161a)
from tesla-api.
What did you use for your OAuth provider?
I have a personal web server that I run a bunch of home/life automations on. I do OAuth through that.
from tesla-api.
Thanks @timdorr and everyone who contributed to the API docs + ruby code over the last decade!!
from tesla-api.
direct quote:
Following the release of Tesla Vehicle Command SDK support for REST API vehicle command endpoints is now reaching end of life. Starting 2024 most vehicles will require sending commands via Tesla Vehicle Command SDK.
The use of Tesla http proxy is recommended for ease of development and to accelerate the transition to Tesla Vehicle Command (via SDK). When applicable, the proxy will transform Rest API HTTP commands into signed commands. Once configured, developers can simply point their application to the proxy without making any code changes to their application.
src: https://developer.tesla.com/docs/fleet-api?shell#fleet-telemetry
from tesla-api.
Will most existing apps get approved?
from tesla-api.
A documented and supported API from Tesla, this is fantastic news!
from tesla-api.
from tesla-api.
I understand that pre-2021 S and X cars will not be compatible with this new API but will still be with current one.
Hi @GaPhi can you point to where you found this info?
from tesla-api.
I think we're done here!
end of an era!
from tesla-api.
I understand that pre-2021 S and X cars will not be compatible with this new API but will still be with current one.
Hi @GaPhi can you point to where you found this info?
It’s a quote from the last section on the github page
https://github.com/teslamotors/vehicle-command
I truly hope it’s a misunderstanding because then there will be two APIs and unless the new one has tantalisingly new functionality, the old/current one will continue to be used to widen the audience
from tesla-api.
I understand that pre-2021 S and X cars will not be compatible with this new API but will still be with current one.
I wonder where an older car with the MCU2 upgrade fits into this. Ie is it the MCU version that determines compatibility or other factors?
from tesla-api.
@kribensa thanks, must've missed it.
I truly hope it’s a misunderstanding because then there will be two APIs and unless the new one has tantalisingly new functionality
Unfortunately, it's prob not. Pre-refresh Model S & X don't support VCSEC (eg: no BLE compatibility) and BLE is integrated into a significant portion of the new vehicle-command protocol.
So this:
I wonder where an older car with the MCU2 upgrade fits into this. Ie is it the MCU version that determines compatibility or other factors?
will prob have no effect :/
the old/current one will continue to be used to widen the audience
This prob won't be so bad with the new tesla-http-proxy, but if you skip the proxy entirely and adopt the new vehicle-commands protocol natively then yeah that will be a huge pain.
Hopefully @teslamotors chooses to reverse this decision and support older Model S & X vehicles in vehicle-command
from tesla-api.
It only took 10 years! (e9a161a)
It can take a long time to become an overnight success.
from tesla-api.
Will most existing apps get approved?
I just applied and was immediately rejected. No reason was given.
from tesla-api.
I just applied and was immediately rejected. No reason was given.
That's interesting. I applied and was immediately approved. I didn't select all of the scopes, and I filled out all of the details as a "company".
from tesla-api.
That's interesting. I applied and was immediately approved. I didn't select all of the scopes, and I filled out all of the details as a "company".
What did you use for your OAuth provider?
from tesla-api.
What did you use for your OAuth provider?
I have a personal web server that I run a bunch of home/life automations on. I do OAuth through that.
Do you know if it's possible to get a list of referrals through their API?
from tesla-api.
Perhaps this repo can become a Ruby client only for new API endpoints; new requirements like /vehicle_data?endpoints=location_data;charge_state
from tesla-api.
Looks like the EV.energy folks have something working already.
https://twitter.com/teslaownersSV/status/1724102225579188453?t=Qd7mDeInbR3poLKTL7zHxw&s=19
ChargeHQ also have a working solution now:
https://www.tesla.com/_ak/tesla.chargehq.net
from tesla-api.
Related Issues (20)
- "data_request" endpoints appear to have been removed by Tesla HOT 5
- Battery capacity and health
- How to call `mobile-app/*` endpoints? HOT 3
- in `login!': undefined method `split' for nil:NilClass (NoMethodError) HOT 2
- display_name is no longer part of vehicle_data response HOT 2
- Charger occupancy
- 403 during token refresh only on docker
- HTTP Error: 403 Client Error: Forbidden for url: https://auth.tesla.com/oauth2/v3/authorize
- 403 status code on http://auth. tesla.com/oauth2/v3/authorize.. after entering email HOT 1
- "/api/1/energy_sites/{site_id}/calendar_history" API does not work when kind=energy
- Should `tesla-api` gem provide a default `retry_options`? HOT 1
- Error when try to login to tesla.com
- Endpoint `/api/1/vehicles` returns only 100 records HOT 1
- Powerwall API changes orphan downstream home assistant projects HOT 3
- Is Apple removing Tesla third party apps? HOT 1
- Charge invoice PDFs HOT 2
- OpenAPI Specification HOT 1
- Tesla Signaling/Hermes Protocol to send vehicle commands
- Climate not possible with low soc HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from tesla-api.