Re: iotivity lite bridge - oc_remove_device
toggle quoted messageShow quoted text
Just finished reading and playing with the ocfbridging branch.
So far, it seems to have all I need.
Still, I have some questions. After playing with the dummy bridge example and using Device Spy to read /bridge/vodlist, I have an empty list (even if I try to select 1 in the menu to simulate light 1 or 7 to start the virtual discovery.)
So I must have missed something. What client (if any) are you using for testing the bridge?
I know it is a work in progress, but if I can help, let me know.
Other question: If my Bluetooth device requires a PIN code for pairing, how do I do that with OCF to transfer the pin code request and return the user's pin code? Do I have to do something myself using a dedicated resource?
Le lundi 4 mai 2020 à 15:56:20 UTC+2, Maloor, Kishen <kishen.maloor@...> a écrit :
Please take a look inside the "ocfbridging" branch.
There's some in-progress work over there that should directly address your need. Specifically, it adds infrastructure that allows an application to
dynamically attach and detach virtual OCF Devices based on the presence of related entities in any 3rd party technology. The states of those virtual Devices
are persisted over the duration of their use. Further, this framework incorporates the specified semantics with respect to discoverability (on the OCF side) of
virtual Devices to fulfill some security requirements outlined in the OCF bridging specification.
You should be able to build an application that interacts with Bluetooth devices (your code), and map those to virtual OCF Devices using the said infrastructure.
From: <firstname.lastname@example.org> on behalf of "fariouche via groups.io" <fariouche@...>