Hi Mark, I’m working on a widget to see my SOC on my Garmin watch and I’d like to request permission to go further and publish on the Garmin store (https://apps.garmin.com/en-US/) with “OVMS" as name. Once in the store, user will be able to enter vehicle_id, username and password/token to access own car information. Application uses a proxy on AWS Lambda to access the REST Api. I have taken the resources from the iOS app and reduced the size a bit. Please note that I also use the OVMS logo on the loading screen. Here is the code: https://github.com/sdarveau/Open-Vehicle-Garmin. Feel free to move it under the openvehicles workspace. I’m planning to improve it but I'll keep it simple. Thanks, Sebastien
Sebastien, Sounds exciting. I have some comments/questions: You are free to publish this wherever you desire. Similarly, the logo and images are ok for you to use. We try to use ‘Open Vehicles’ as the name. It is short, but explains the project goals in a better way than the OVMS abbreviation. Do you handle the selection of server (api / Dexter / whatever) or fixed to just api.openvehicles.com? Why is your AWS Lambda required? If the HTTP API cannot be used directly, is there a workaround we can do (such as extending the server code) to avoid the requirement for yet another server? I ask because this has security and trust implications for the end-user. A note that medium to long term, it will be better to use api token based authentication - but server side support for that is still in progress so you can’t really use that today. Regards, Mark.
On 16 Jul 2020, at 3:35 AM, Sébastien Darveau <sebastien.darveau@synnoetic.com> wrote:
Hi Mark,
I’m working on a widget to see my SOC on my Garmin watch and I’d like to request permission to go further and publish on the Garmin store (https://apps.garmin.com/en-US/ <https://apps.garmin.com/en-US/>) with “OVMS" as name. Once in the store, user will be able to enter vehicle_id, username and password/token to access own car information. Application uses a proxy on AWS Lambda to access the REST Api.
I have taken the resources from the iOS app and reduced the size a bit. Please note that I also use the OVMS logo on the loading screen.
Here is the code: https://github.com/sdarveau/Open-Vehicle-Garmin <https://github.com/sdarveau/Open-Vehicle-Garmin>. Feel free to move it under the openvehicles workspace.
I’m planning to improve it but I'll keep it simple.
Thanks, Sebastien _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Ok. I will change the name. The reason for the proxy (AWS Lambda) is that the watch is very picky and I didn’t want to bother you with that. At first, the certificate was apparently the problem but then you fixed it and I was still receiving error codes. Another advantage is that I will be able to strip the content to optimize loading time on the watch. What do you mean by “you can’t really use that today”? Does it mean I must ask the user for a password and not the token? Thanks, Sebastien On Jul 16, 2020, at 1:17 AM, Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net> > wrote: Sebastien, Sounds exciting. I have some comments/questions: * You are free to publish this wherever you desire. * Similarly, the logo and images are ok for you to use. * We try to use ‘Open Vehicles’ as the name. It is short, but explains the project goals in a better way than the OVMS abbreviation. * Do you handle the selection of server (api / Dexter / whatever) or fixed to just api.openvehicles.com <http://api.openvehicles.com/> ? * Why is your AWS Lambda required? If the HTTP API cannot be used directly, is there a workaround we can do (such as extending the server code) to avoid the requirement for yet another server? I ask because this has security and trust implications for the end-user. * A note that medium to long term, it will be better to use api token based authentication - but server side support for that is still in progress so you can’t really use that today. Regards, Mark. On 16 Jul 2020, at 3:35 AM, Sébastien Darveau <sebastien.darveau@synnoetic.com <mailto:sebastien.darveau@synnoetic.com> > wrote: Hi Mark, I’m working on a widget to see my SOC on my Garmin watch and I’d like to request permission to go further and publish on the Garmin store (https://apps.garmin.com/en-US/) with “OVMS" as name. Once in the store, user will be able to enter vehicle_id, username and password/token to access own car information. Application uses a proxy on AWS Lambda to access the REST Api. I have taken the resources from the iOS app and reduced the size a bit. Please note that I also use the OVMS logo on the loading screen. Here is the code: https://github.com/sdarveau/Open-Vehicle-Garmin. Feel free to move it under the openvehicles workspace. I’m planning to improve it but I'll keep it simple. Thanks, Sebastien _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev> _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
What do you mean by “you can’t really use that today”? Does it mean I must ask the user for a password and not the token?
Yes. For the moment the user+password is really the only way to access the server. Longer-term we will switch to token. Regards, Mark.
On 16 Jul 2020, at 9:17 PM, Sébastien Darveau <sebastien.darveau@synnoetic.com> wrote:
Ok. I will change the name. The reason for the proxy (AWS Lambda) is that the watch is very picky and I didn’t want to bother you with that. At first, the certificate was apparently the problem but then you fixed it and I was still receiving error codes. Another advantage is that I will be able to strip the content to optimize loading time on the watch.
What do you mean by “you can’t really use that today”? Does it mean I must ask the user for a password and not the token?
Thanks, Sebastien
On Jul 16, 2020, at 1:17 AM, Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>> wrote:
Sebastien,
Sounds exciting. I have some comments/questions:
You are free to publish this wherever you desire. Similarly, the logo and images are ok for you to use. We try to use ‘Open Vehicles’ as the name. It is short, but explains the project goals in a better way than the OVMS abbreviation. Do you handle the selection of server (api / Dexter / whatever) or fixed to just api.openvehicles.com <http://api.openvehicles.com/>? Why is your AWS Lambda required? If the HTTP API cannot be used directly, is there a workaround we can do (such as extending the server code) to avoid the requirement for yet another server? I ask because this has security and trust implications for the end-user. A note that medium to long term, it will be better to use api token based authentication - but server side support for that is still in progress so you can’t really use that today.
Regards, Mark.
On 16 Jul 2020, at 3:35 AM, Sébastien Darveau <sebastien.darveau@synnoetic.com <mailto:sebastien.darveau@synnoetic.com>> wrote:
Hi Mark,
I’m working on a widget to see my SOC on my Garmin watch and I’d like to request permission to go further and publish on the Garmin store (https://apps.garmin.com/en-US/ <https://apps.garmin.com/en-US/>) with “OVMS" as name. Once in the store, user will be able to enter vehicle_id, username and password/token to access own car information. Application uses a proxy on AWS Lambda to access the REST Api.
I have taken the resources from the iOS app and reduced the size a bit. Please note that I also use the OVMS logo on the loading screen.
Here is the code: https://github.com/sdarveau/Open-Vehicle-Garmin <https://github.com/sdarveau/Open-Vehicle-Garmin>. Feel free to move it under the openvehicles workspace.
I’m planning to improve it but I'll keep it simple.
Thanks, Sebastien _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Ok! Here is the link. Let me know if you need me to change something. https://apps.garmin.com/en-US/apps/17164a39-bc7b-47dd-b732-37c45a3987d5 Regards, Sebastien On Jul 26, 2020, at 10:55 PM, Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net> > wrote: What do you mean by “you can’t really use that today”? Does it mean I must ask the user for a password and not the token? Yes. For the moment the user+password is really the only way to access the server. Longer-term we will switch to token. Regards, Mark. On 16 Jul 2020, at 9:17 PM, Sébastien Darveau <sebastien.darveau@synnoetic.com <mailto:sebastien.darveau@synnoetic.com> > wrote: Ok. I will change the name. The reason for the proxy (AWS Lambda) is that the watch is very picky and I didn’t want to bother you with that. At first, the certificate was apparently the problem but then you fixed it and I was still receiving error codes. Another advantage is that I will be able to strip the content to optimize loading time on the watch. What do you mean by “you can’t really use that today”? Does it mean I must ask the user for a password and not the token? Thanks, Sebastien On Jul 16, 2020, at 1:17 AM, Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net> > wrote: Sebastien, Sounds exciting. I have some comments/questions: * You are free to publish this wherever you desire. * Similarly, the logo and images are ok for you to use. * We try to use ‘Open Vehicles’ as the name. It is short, but explains the project goals in a better way than the OVMS abbreviation. * Do you handle the selection of server (api / Dexter / whatever) or fixed to just api.openvehicles.com <http://api.openvehicles.com/> ? * Why is your AWS Lambda required? If the HTTP API cannot be used directly, is there a workaround we can do (such as extending the server code) to avoid the requirement for yet another server? I ask because this has security and trust implications for the end-user. * A note that medium to long term, it will be better to use api token based authentication - but server side support for that is still in progress so you can’t really use that today. Regards, Mark. On 16 Jul 2020, at 3:35 AM, Sébastien Darveau <sebastien.darveau@synnoetic.com <mailto:sebastien.darveau@synnoetic.com> > wrote: Hi Mark, I’m working on a widget to see my SOC on my Garmin watch and I’d like to request permission to go further and publish on the Garmin store (https://apps.garmin.com/en-US/) with “OVMS" as name. Once in the store, user will be able to enter vehicle_id, username and password/token to access own car information. Application uses a proxy on AWS Lambda to access the REST Api. I have taken the resources from the iOS app and reduced the size a bit. Please note that I also use the OVMS logo on the loading screen. Here is the code: https://github.com/sdarveau/Open-Vehicle-Garmin. Feel free to move it under the openvehicles workspace. I’m planning to improve it but I'll keep it simple. Thanks, Sebastien _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev> _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev> _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev> _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
participants (2)
-
Mark Webb-Johnson -
Sébastien Darveau