tesla-api

And thank you for addressing it, Samuel! I converted the streaming and Autopark clients in the Tesla API gem from EM to Async and has been great: https://github.com/timdorr/tesla-api/blob/master/lib/tesla_a... No more globals, which makes it much safer to use inside of threaded job runners like Sidekiq.

There is a huge API to telsa cars: mostly through https://owner-api.teslamotors.com/ for example: POST /api/1/vehicles/{id}/command/door_unlock "Unlocks the doors to the car. Extends the handles on the S and X." response: { "reason": "", "result": true } details of the api people have discovered have been collected here: https://github.com/timdorr/tesla-api Now, I personnaly wouldn't give credentials of my car out to folks, but you have to admit there is some interesting data that has come out of it. for example, folks have discovered the details of how various tesla batteries charge: https://forum.abetterrouteplanner.com/blogs/entry/29-faster-...

If you've ever been to a tesla service center, it's kind of interesting. Cars glide in silently and when they sit there for a bit the words "Service Mode" come up in maybe 5" high letters on the dashboard. There are lots of technicians on their computers. The car info comes up on the specific car and shows lots of history, where and when it was last serviced and so forth. Each car seems to have it's own personal list of options and features, that shows up on the website when searching for cars, or when signing into you car portal. folks have taken the time to document them: https://github.com/timdorr/tesla-api https://github.com/fredrikfjeld/tesla-options-decoder I think all cars are like this, but telsa is less rigid / concerned about model years and just consults the database for the specific car's info at every step.

As long as the carmaker is open about things, the increasing complexity doesn't have to be bad news for tinkerers. It's not officially released yet, but https://github.com/timdorr/model-s-api shows the promise of Tesla's commitment to openness. It won't allow the "how does my car work?" type of tinkering, but it allows the "how can I use my car in interesting ways?" tinkering. It's much the same as computers. The original Apples were understandable devices. The lack of miniaturization meant that hackers could figure out how everything was working and play with it. That activity would be ridiculous with modern-day CPUs/components as the complexity has increased by orders of magnitude and the miniaturization has reached levels where specialized equipment is needed to look at what's going on that costs well beyond what can fit in a hobbyist'

Apiary is great! I used them for documenting the Tesla Model S API: http://docs.timdorr.apiary.io/ All I had to do was create a github repo and that was it: https://github.com/timdorr/model-s-api It's great for public projects because there are both comments, which allows for inline discussion, and a mock API server, which doesn't help me so much (Tesla's API implementation isn't true REST) but allows others to throw things at an endpoint without worrying about consequences. One of the devs was even willing to get involved and issued a pull request for the repo! https://github.com/timdorr/model-s-api/commit/b0669d Awesome guys!

The Model S has a basic, REST-ish API: https://github.com/timdorr/model-s-api

Of course the beauty of it is (if you have a Model S) you can help with the mapping by fork/pull-requesting changes on GitHub: https://github.com/timdorr/model-s-api