Community
Blog
Hot
New
Questions
Forums
Tesla
Model S
Model 3
Model X
Model Y
Roadster 2008-2012
Roadster 202X
Cybertruck
SpaceX
Media
New media
Search media
Blog
Hot
New
Forum list
Groups
Public Events
Podcast
Vendors
Log in
Register
Search
Search engine:
Threadloom Search
XenForo Search
Search titles only
By:
Search engine:
Threadloom Search
XenForo Search
Search titles only
By:
More options
Toggle width
Share this page
Share this page
Share
Facebook
Twitter
Reddit
Pinterest
Tumblr
WhatsApp
Email
Share
Link
Blog
Hot
New
Questions
Forums
Tesla
Model S
Model 3
Model X
Model Y
Roadster 2008-2012
Roadster 202X
Cybertruck
SpaceX
Media
New media
Search media
Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register
Menu
Install the app
Install
Community
Tesla Vehicles
Model S
Model S: User Interface
Model S REST API
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="markwj" data-source="post: 267035" data-attributes="member: 7949"><p>I've been interested in the possible use of OVMS Apps to control multiple cars of different types - not necessarily just with OVMS modules. This allows us to extend the manufacturer's offering, and is real nice for those with more than one car in their garage. OVMS has received literally dozens of request for such support.</p><p></p><p>GM/OnStar now have a published API (although are not permitting this to be used against real cars until late 2013).</p><p></p><p>The Leaf carwings API has been reverse engineered.</p><p></p><p>Now, you guys are reverse engineering the Tesla Model S RESTfull API.</p><p></p><p>Perhaps the neatest way of doing this is by gatewaying at the server - no change to Apps necessary. But, I worry that the providers will rate limit requests from a single IP. Doing it at the server allows for all sorts of cool stuff (e.g.; timed pre-heat).</p><p></p><p>We could also do this in the Apps themselves.</p><p></p><p>But, my question is what is the legality of this? I suspect that it would be a contravention of the DMCA? I read that GM/OnStar stopped (or persuaded to stop) the VoltStats guy to stop - and he is now using a very restricted API just for him. What about Nissan? I guess the legalities of doing the reverse engineering vs using fruits of such work are different.</p><p></p><p>Looking at the Model S API, it would be about an evening's work to do a server gateway. Scarily simple. I don't have the car (yet), but if someone (presumably an OVMS roadster owner who also has a Model S) wants to work with me on a proof-of-concept for this, I'm more than willing to give it a go.</p></blockquote><p></p>
[QUOTE="markwj, post: 267035, member: 7949"] I've been interested in the possible use of OVMS Apps to control multiple cars of different types - not necessarily just with OVMS modules. This allows us to extend the manufacturer's offering, and is real nice for those with more than one car in their garage. OVMS has received literally dozens of request for such support. GM/OnStar now have a published API (although are not permitting this to be used against real cars until late 2013). The Leaf carwings API has been reverse engineered. Now, you guys are reverse engineering the Tesla Model S RESTfull API. Perhaps the neatest way of doing this is by gatewaying at the server - no change to Apps necessary. But, I worry that the providers will rate limit requests from a single IP. Doing it at the server allows for all sorts of cool stuff (e.g.; timed pre-heat). We could also do this in the Apps themselves. But, my question is what is the legality of this? I suspect that it would be a contravention of the DMCA? I read that GM/OnStar stopped (or persuaded to stop) the VoltStats guy to stop - and he is now using a very restricted API just for him. What about Nissan? I guess the legalities of doing the reverse engineering vs using fruits of such work are different. Looking at the Model S API, it would be about an evening's work to do a server gateway. Scarily simple. I don't have the car (yet), but if someone (presumably an OVMS roadster owner who also has a Model S) wants to work with me on a proof-of-concept for this, I'm more than willing to give it a go. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
Tesla Vehicles
Model S
Model S: User Interface
Model S REST API
Top
Blog
Hot
New
Forum list
Menu