Elizabeth, As Clark said the client server will not communicate unless they have been onboarded. This can be done using the OTGC tool developed by OCF. Sorry I don’t know the link to the tool. Or you can use the onboarding_tool that is part of iotivity-lite. The onboarding_tool is a used by the development team to test and verify the onboarding and provisioning features. It is not the most user friendly. The README.rst document has a set-by-setp guide for using the onboarding tool to onboard and provision a server and client. (search for the “Simple Step-by-Step guide for onboarding and provisioning” section) The steps in that document is what I use almost every day when testing servers and clients.
George From: [email protected] <[email protected]> On Behalf Of Clarke Stevens Sent: Sunday, February 23, 2020 10:54 PM To: [email protected] Cc: [email protected] Subject: Re: [dev] Iotivity Client Elizabeth, Yes, you will need to onboard the server before the client and server will communicate. You probably know more than I do about the update specification. I haven’t built an example with it yet. Wouter is the expert on the update specification. Kishen is the expert on simpleserver and simpleclient, but I think George has also built those many times. Thanks, -Clarke On Feb 23, 2020, at 10:43 PM, [email protected]<mailto:[email protected]> wrote: Hi George and Clarke, Thanks for the response! Also thanks to Clarke, Yes, I've tried your examples to build an iotivity server as you gave me that before. I've built Iotivity server on my Raspberry Pi with enviro phat as the sensor. Now, I'm looking for a client example for communicate with smart_home_server_with_mock_swupdate, because my research is try to implement OCF firmware update protocol. I've read both smart_home_server_with_mock_swupdate code and OCF FU protocol documentation (OCF 2.0.3 core and security specifications), it needs a client to trigger the firmware update process (according to OCF FU protocol documentation). That's why I want to learn the other client and server example first before I can make the client for trigger the FU process. I've tried the simpleclient and simpleserver, but they didn't communicate. In simpleclient code, the client should do observe then get the light state from simpleserver. But, it stopped after send and received coap messages. Do I need to run onboarding_tool first and onboard the server and client before it can communicate each other (for example: client get the resource from the server)? And for gcc, what version that compatible? -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#10358): https://iotivity.groups.io/g/iotivity-dev/message/10358 Mute This Topic: https://groups.io/mt/69378274/21656 Group Owner: [email protected] Unsubscribe: https://iotivity.groups.io/g/iotivity-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
