One other note: the “remove” functionality is purely in the sample
provisioningclient application, and while I do believe it’s broken currently
(last I checked it didn’t work for me, either), it has no effect or interaction
with the actual OCF stack implemented in IoTivity… it’s just removing the
Server entry from the provisioningclient’s internal proprietary db of Servers.
From: Heldt-Sheller, Nathan
Sent: Thursday, February 15, 2018 12:36 PM
To: 'Walber de Macedo Rodrigues' <w...@cin.ufpe.br>;
iotivity-dev@lists.iotivity.org
Subject: RE: [dev] Provisioning example
Hello Walber,
The provisioningclient application has many menu options which are not
routinely tested (in fact, IoTivity’s current automated tests do not run this
application at all as far as I know). We are working with our QA vendors to
improve this and include some of these functions as part of a weekly regression
test.
In the meantime, there are only a few functions which several of the developers
(myself included) verify regularly. A nominal smoke test to verify you have
everything working correctly:
1. $ cd <out>/resource/csdk/security/provisioning/sample
2. $ ./sampleserver_justworks (optionally,
“$./sampleserver_justworks |& tee ss-jw.log” to capture output for later study)
3. <open a second console in same dir>
4. $ ./provisioningclient (using | tee not suggested as it
tends to make menu unusable, but once the process is memorized, you can then
use | tee to capture client-side logs)
5. at provisioningclient app menu, choose "10" <enter>
6. after discovery completes, one device should appear in
"un-owned" list and the menu is re-displayed
7. at provisioningclient app menu, choose "20" <enter>
8. after doing JustWorks OTM completes and the menu is
re-displayed
9. at provisioningclient app menu, choose "10" <enter>
10. after discovery, same deviceuuid as step 6. should appear
but now in "owned" device list
This will work one time, after which the server will be owned and onboarded.
To revert the server to unowned, and run these steps again, you can replace the
server’s .dat file with the original using the json2cbor tool (in this example
the out directory containing json2cbor is in the PATH):
$ json2cbor oic_svr_db_server_justworks.json
oic_svr_db_server_justworks.dat
Finally, you should know that there is a GUI provisioning tool that will
replace this provisioningclient sample app in the next release (slated for
May), so there isn’t a lot of effort going into fixing/improving this command
line sample tool.
Hope this helps,
Thanks,
Nathan
From:
iotivity-dev-boun...@lists.iotivity.org<mailto:iotivity-dev-boun...@lists.iotivity.org>
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Walber de Macedo
Rodrigues
Sent: Thursday, February 15, 2018 9:56 AM
To: iotivity-dev@lists.iotivity.org<mailto:iotivity-dev@lists.iotivity.org>
Subject: [dev] Provisioning example
Hello everybody,
I tried to run the provisioning example shown in this wiki page:
https://wiki.iotivity.org/provisioning .
But the application shows errors when I try to run the following commands:
1. [Command 50] Remove the Selected Device
* ERROR: provisioningclient: OCRemoveDevice API error: 26
* ERROR: provisioningclient: _50_REMOVE_SELEC_DEV_: error
1. [Command 51] Remove Device with UUID:
* ERROR: provisioningclient: OCRemoveDeviceWithUuid API error: 26
* ERROR: provisioningclient: _51_REMOVE_DEV_WITH_UUID_: error
1. [Command 52] Reset the Selected Device
* ERROR: provisioningclient: OCResetDevice API error: 26
* ERROR: provisioningclient: _52_RESET_SELEC_DEV_: error
I tested on both 1.3.0 and 1.3.1 versions using C, giving the same error, and a
friend is having similar issues in Java.
Is that a not yet implemented feature or some problem with the example?
Best regards,
Walber
_______________________________________________
iotivity-dev mailing list
iotivity-dev@lists.iotivity.org
https://lists.iotivity.org/mailman/listinfo/iotivity-dev
