Hello Jith, Sorry for the late reply.
As for ?test environment?, I assume you mean what environment is required to bring up the plugin architecture for the Zigbee plugin and run the sample applications. As for the unit tests, you will just have to use the normal Scons build parameters to initiate the unit tests. (I believe that looks like this: ?scons TESTS=1? at the root of the IoTivity repository/project directory) First and foremost you will need a Telegesis USB Dongle. The model I used during development was a Telegesis USB Dongle ?ETRX357USB-LR?. The firmware on this dongle will need to be upgraded. This firmware will need to be obtained through contacting the sales team at Telegesis? website (we used this link to find a sales representative for our devices: http://www.silabs.com/buysample/pages/contact-sales.aspx?view=map). You will need to ask for a firmware upgrade to version 3.10 (known as R310). The stock firmware version will not work as it only supports a subset of the required full functionality used in our plugin architecture. //From here on out this ?ETRX357USB-LR? module will be referred to as Telegesis Dongle, Telegesis USB Dongle, or USB Dongle. 1. If using Linux you will need to ensure your user is a part of the ?dialout? group. You can do this on Ubuntu by issuing command ?sudo adduser <MY_USER_NAME> dialout? and then restart your computer. 2. Ensure you?re building the sample applications by issuing the following build command at the root of the IoTivity repository/project directory: ?scons plugins? 3. cd <IOTIVITY>/out/linux/<ARCH_TYPE>/<DEBUG_or_RELEASE>/plugins/samples/linux/ 4. Turn on/Reset any of the devices (only required once as the Telegesis Dongle remembers it?s pairings from last time) from the below table. 5. issue following command to start the server: ./iotivityandzigbeeserver 6. Wait >20 seconds to ensure that discovery and pairing has occurred in the server. 7. In different terminal, issue the following command to start the client: ./iotivityandzigbeeclient 8. Wait for client to discover resources types from the following table. You can use the commands in the client application to control ZigBee devices now. Physical Device (You can buy this on the market) ZigBee Cluster IDs Supported OCF Smart Home Resource Types Supported SmartThings Water Leak Sensor 0x0402, 0x0500 oic.r.temperature, oic.r.contact.sensor SmartThings Open/Close Sensor (Multipurpose) 0x0402, 0x0500 oic.r.temperature, oic.r.contact.sensor SmartThings Motion Sensor 0x0402, 0x0500 oic.r.temperature, oic.r.contact.sensor SmartThings Smart Plug 0x0006 oic.r.binary.switch OSRam Lightify Light Bulb 0x0008, 0x0006 oic.r.light.dimming, oic.r.binary.swtich GE Wink Light Bulb 0x0008, 0x0006, 0x0300 oic.r.light.dimming, oic.r.binary.swtich, oic.r.colour.chroma (Invalid Mapping) ZigBee Cluster ID ZigBee Cluster Name OCF Smart Home Resource 0x0402 Temperature Cluster oic.r.temperature 0x0008 Level Control Cluster oic.r.light.dimming 0x0006 On Off Cluster oic.r.binary.switch 0x0500 IAS Zone Cluster (Motion Sensor, Contact Sensor, Water Sensor) oic.r.contact.sensor 0x0300 Color Control Cluster oic.r.colour.chroma (Invalid Mapping) ZigBee Cluster Reference: http://www.zigbee.org/download/standards-zigbee-cluster-library/ OCF Resource Reference: http://www.oneiota.org/ Thanks, Joey Morrow From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Jith Cr Sent: Friday, May 13, 2016 5:03 AM To: iotivity-dev at lists.iotivity.org Subject: [dev] IoTivity Plug-in Samples Test Procedure Hi, I've been trying to test the IoTivity plug-in samples(iotivityandzigbeeserver and iotivityandzigbeeclient) on Linux (Ubuntu 14.04) Can anyone give me directions regarding the test environment(about the zig-bee device,plug-in etc) and test procedure? Thanks, Jith -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160516/207d22b6/attachment.html>
