[Ovmsdev] Open API

[Michael Balzer]

Hi Robert,

you can connect to an OVMS server through the client protocol (TCP) or
via HTTP.

See
-
https://github.com/openvehicles/Open-Vehicle-Monitoring-System/blob/master/docs/OVMS_Protocol.pdf
and the perl clients for details and examples. The protocol supports
telemetry, command execution, push notifications and more.

The HTTP API lacks documentation, it supports telemetry up to now and
it's been described here:
- http://lists.teslaclub.hk/pipermail/ovmsdev/2013-February/000919.html
- http://lists.teslaclub.hk/pipermail/ovmsdev/2013-March/000958.html

...and there's a simple JS client implementation over here:
- http://www.openvehicles.com/simpleclient.htm

To my knowledge there is no cooperation with any car manufacturer.
I would be surprised if car manufacturers actually show interest in
supporting unified or open APIs.

Regards,
Michael


Am 17.01.2016 um 14:20 schrieb Robert Sharpe:
> Hi,
>
> As always, after sending the email found some of what was required
> turned up.
>
> But I am still looking for the OVMS server API specification.
>
> For your information
>
>   * General APIs -
>     https://developer.ibm.com/apimanagement/2014/10/31/whats-driving-apis-automotive
>   * Tesla - http://docs.timdorr.apiary.io
>   * Nissan CarWings - www.npmjs.com/package/carwingsjs
>   * GM - https://developer.gm.com/documentation
>   * BMW i3
>     - https://shkspr.mobi/blog/2015/11/reverse-engineering-the-bmw-i3-api
>
> Because we need to access multiple car types, my vision is to
> find/develop a unified open API.  Is OVMS working with anyone along
> this line?
>
> Look forward to hearing any plans.
>
> Regards,
> Robert Sharpe (Managing Director)
> 07711 252971
>
> <http://www.linkedin.com/in/arsharpe> <http://www.twitter.com/EgcTechnical> <https://www.facebook.com/EvergreenConsultingLtd> <http://www.evergreen-consulting.co.uk/staff/skype/rsharpe.html> <http://www.evergreen-consulting.co.uk/staff/calendars/rsharpe.html?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email>
>
>  
> <http://www.evergreen-consulting.co.uk/?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email>
>
> /Your Plugged-in Partner/
>
> Evergreen Consulting is the trading name of Sharpe Consultants Ltd
>
>
>
> ---- On Sat, 16 Jan 2016 16:25:35 +0000
> *<robert.sharpe at evergreen-consulting.co.uk>* wrote ----
>
>     Hi,
>
>     I am working on an EV route planning and navigation system that
>     will need real time remote access to vehicle data.
>
>     The most powerful approach would be to access all the different
>     supported vehicles through a standard cloud base open api.  My
>     initial Googling has not shown an existing API but I know OVMS has
>     a server.
>
>     Can anyone tell me
>
>       * the location of a OVMS API definition?
>       * any other standard APIs (similar to Open Charge Point Protocol
>         but for cars)
>
>     Thanks in advance.
>
>     Regards,
>     Robert Sharpe (Managing Director)
>     07711 252971
>
>     <http://www.linkedin.com/in/arsharpe> <http://www.twitter.com/EgcTechnical> <https://www.facebook.com/EvergreenConsultingLtd> <http://www.evergreen-consulting.co.uk/staff/skype/rsharpe.html> <http://www.evergreen-consulting.co.uk/staff/calendars/rsharpe.html?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email>
>
>      
>     <http://www.evergreen-consulting.co.uk/?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email>
>
>     /Your Plugged-in Partner/
>
>     Evergreen Consulting is the trading name of Sharpe Consultants Ltd
>
>
>
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20160117/853a2db1/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1452 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20160117/853a2db1/attachment-0020.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1441 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20160117/853a2db1/attachment-0021.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1421 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20160117/853a2db1/attachment-0022.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1457 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20160117/853a2db1/attachment-0023.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1191 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20160117/853a2db1/attachment-0024.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 10590 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20160117/853a2db1/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1452 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20160117/853a2db1/attachment-0025.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1441 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20160117/853a2db1/attachment-0026.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1421 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20160117/853a2db1/attachment-0027.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1457 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20160117/853a2db1/attachment-0028.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1191 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20160117/853a2db1/attachment-0029.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 10590 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20160117/853a2db1/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dexter.vcf
Type: text/x-vcard
Size: 206 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20160117/853a2db1/attachment-0002.vcf>