Re: iotivity lite bridge - oc_remove_device
My educated guess as to why you did not see the /bridge/vodslist the first time you tried device spy would be because the bridge device was not yet been onboarded.
According to the security specification devices being bridged are not discoverable till the bridge device is onboarded.
The vodslist is only updated once a virtual device is actually onboarded. Till then the list will be empty.
You asked in another email thread how testing was being done. Most of the testing has been done using OCF’s conformance and test tool (CTT) I have also done some minor testing by writing small test programs to test against. Unlike the dummy_bridge these are not checked into the branch since they not good code to reference.
I looked into the “OCF Resource to BLE Mapping Specification” and I did not find anything reguarding pin codes.
You can try to initiate Bluetooth pairing as a result of the ownership transfer method using pin code.
Personally I would split them into two tasks.
If you are able to get them working as two separate steps then you could try pairing the Bluetooth device a part of the PIN OTM process.
The ocfbridging branch is still a work in progress. If you are experiencing any issues or have suggestions please let me know I will try and help you out. If you think you have found a bug feel free to create an issue and assign it to George Nash (that’s me).
From: firstname.lastname@example.org <email@example.com> On Behalf Of Farid BENAMROUCHE via groups.io
Sent: Wednesday, May 6, 2020 11:13 AM
To: firstname.lastname@example.org; Maloor, Kishen <kishen.maloor@...>
Subject: Re: [dev] iotivity lite bridge - oc_remove_device
Never mind, I got the device spy tool working (not sure why the first time it didn't discover the virtual devices)
Now I see that if I add a new virtual device, it must be discovered first, then onboarded (with pin code if needed instead of just work)
Thank you, I have enough material to continue
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.
on behalf of "fariouche via groups.io" <fariouche@...>