Hi Greg, There are two ways. Either use a BLE stack that has some port of iotivity-lite or devise some proxy to interface with a native BLE device using its own stack that has no OCF support.
For the first case, mynewt is one option and the other is Zephyr. Also for Nordic modules, RIOT with its iotivity-lite port is also possible. Zephyr and mynewt support many other modules beyond Nordic NRF. For the second case, the best that I know of is this project https://01.org/smarthome. It is based on a port of Iotivity to node.js called iotivity-node. I have used some of the example scripts to work with Nordic node that uses Nordic native stack and expose it to the world as OCF device. Currently trying to generalize to multiple BLE devices and profiles as much as can be supported by the number of connections supported by the BLE chipset. Haven't experimented with complex issues such as ownership transfer, provisioning, onboarding in either case. BR, Khaled On Mon, Apr 9, 2018 at 11:09 PM, Gregg Reynolds <d...@mobileink.com> wrote: > > > On Sat, Apr 7, 2018, 5:06 PM Sterling Hughes <sterl...@runtime.io> wrote: > >> Note: you can do that out of the box with Apache Mynewt: >> > > Thanks, looks very interesting. > > But what about security? How does mynewt play with OCF ownership transfer, > provisioning, onboarding, etc? > > Gregg > > _______________________________________________ > iotivity-dev mailing list > firstname.lastname@example.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > >
_______________________________________________ iotivity-dev mailing list email@example.com https://lists.iotivity.org/mailman/listinfo/iotivity-dev