Page Comparison

In this tutorial, you summarize the battery lelve level data of the device and create the Battery_Level_Per_Hour table by annalzing analyzing  the data gathered from all the enrolled devices.

MobX created creates new mobile applications or send updated sends updates to corporate mobile applications. These applications need to be installed on the users devices. To ensure that the applciations applications are installed or updated on all the enrolled devices successfully, all the devices need to have a battery level of 50% or above. Using the steps given below, MobX administartors administrators are able to identify the devices that had less battery power when an application installation request was pushed and confirm with those users if the application was installed successfully.

Let's get started!

...

Configuring WSO2 IoT

...

Server to publish device information

You need to configure WSO2 IoT Server to publish device information as it is disabled by default. Follow the steps given below.

1. Open the <IOTS_HOME>/conf/cdm-config.xml file.

2. Configure the PublishDeviceInfoResponse parameter as true. 

   Code Block
   <OperationAnalyticsConfiguration> <PublishLocationResponse>false</PublishLocationResponse> <PublishDeviceInfoResponse>true</PublishDeviceInfoResponse> <PublishOperationResponse> <Enabled>false</Enabled> <Operations> <Operation>*</Operation> </Operations> </PublishOperationResponse> </OperationAnalyticsConfiguration>

Creating a stream and persisting data

You need to create a stream to gather the device data. Follow the steps given below:

1. Start WSO2 IoT Server:

   1. Start the WSO2 IoT Server broker profile.

      Code Block
      cd <IOTS_HOME>/bin sh broker.sh

   2. Start the WSO2 IoT Server core profile.

      Code Block
      cd <IOTS_HOME>/bin sh iot-server.sh

   3. Next, start the WSO2 IoT Server analytics profile.

      Code Block
      cd <IOTS_HOME>/bin sh analytics.sh

...

You need to create a stream to gather the device data. Follow the steps given below:

1. Access the WSO2 IoT Server's analytics management console.

   1. For access via secured HTTP: https://<IOTS_HTTPS_HOST>:9445/carbon/ 
For example: https://localhost:9445/carbon/

   2. For access via HTTP: http://<IOTS_HTTP_HOST>:9765/carbon/ 

      For example: http://localhost:9765/carbon/

2. On the Main tab click Streams that is under Events.

3. Click + Add Events Streams.

4. Enter the following values:

   Event Stream Name	org.wso2.iot.BatteryStream
   Event Stream Version	1.0.0
   Meta Data Attributes	Add a meta data attribute by entering the name, selecting the type from the drop-down list, and by clicking Add . Attribute name Attribute type deviceId String deviceType String timestamp Long
   Payload Data Attributes	Add a payload data attribute by entering the name, selecting the type from the drop-down list, and by clicking Add . Attribute name Attribute type level Double year Int month Int day Int hour Int minute Int

5. Click Perisist Persist Events. What happens when you do this?
6. Click Add Event Stream.

Creating an execution plan to publish data

Create an execution plan to publish the data received to an output stream. Follow the steps given below:

1. On the Main tab, click Execution Plans.
2. Click Add Execution Plan.

3. Copy the execution plan that is given below and replace the sample content that is in the text box.

   Code Block

   @Plan:name('analze_battery_level') @Import('org.wso2.iot.DeviceInfoStream:1.0.0') define stream inputStream (meta_deviceId string, meta_deviceType string, timeStamp long, imei string, imsi string, deviceModel string, vendor string, osVersion string, osBuildDate string, batteryLevel double, totalInternalMemory double, availableInternalMemory double, totalExternalMemory double, availableExternalMemory double, operator string, connectionType string, mobileSignalStrength double, ssid string, cpuUsage double, totalRAM double, availableRAM double, pluggedIn bool); @Export('org.wso2.iot.BatteryStream:1.0.0') define stream outputStream (meta_deviceId string, meta_deviceType string, meta_timestamp long, level double, year int, month int, day int, hour int, minute int); from inputStream select meta_deviceId, meta_deviceType, timeStamp as meta_timestamp, batteryLevel as level, time:extract(time:timestampInMilliseconds(), 'year') as year, time:extract(time:timestampInMilliseconds(), 'day') as day, time:extract(time:timestampInMilliseconds(), 'hour') as hour, time:extract(time:timestampInMilliseconds(), 'minute') as minute insert into outputStream;

4. Click Add Execution Plan.

Creating an analytics script to summarize data

...

1. On the Main tab click Scripts that is under Batch Analytics.
2. Click Click Add New Analytics Scripts.
3. Give the script a name, such as battery_data_analytics.

4. Copy the script given below to the the Spark SQL Queries text  text box.

   Code Block

   CREATE TEMPORARY TABLE BatteryData USING CarbonAnalytics OPTIONS(tableName "ORG_WSO2_IOT_BATTERYSTREAM", incrementalParams "ORG_WSO2_IOT_BATTERYSTREAM, HOUR"); CREATE TEMPORARY TABLE Battery_Level_Per_Hour USING CarbonAnalytics OPTIONS (tableName "Battery_Level_Per_Hour", schema "deviceId STRING, type STRING, level DOUBLE -i, year INT -i, month INT -i, day INT -i, hour INT -i, timestamp LONG", primaryKeys "year, month, day, hour, deviceId, type", mergeSchema "false"); INSERT INTO TABLE Battery_Level_Per_Hour SELECT meta_deviceId as deviceId, meta_deviceType as type, avg(level) as level, year, month, day, hour, getHourStartingTime(year, month, day, hour) as timestamp FROM BatteryData GROUP BY meta_deviceId, meta_deviceType, year, month, day, hour; INCREMENTAL_TABLE_COMMIT ORG_WSO2_IOT_BATTERYSTREAM;

5. Enter 0 0 0/1 1/1 * ? * as  as the value for the the Cron Expression.
   This field is used to determine how often the analytics script needs to be executed. In this sample we have configured the script to run every hour.
6. Click Click Add.

Creating an execution plan to publish data

...

Try it out

The script you wrote above summarizes the batter data of the devices and adds it to the Battery_Level_Per_Hour database table. To check out the data that was summarized and added to the table, follow the steps given below:

1. On the Main tab, click Execution Plans.
2. Click Add Execution Plan.

3. Copy the execution plan that is given below and replace the sample content that is in the text box.

   Code Block

   @Plan:name('analze_battery_level') @Import('org.wso2.iot.DeviceInfoStream:1.0.0') define stream inputStream (meta_deviceId string, meta_deviceType string, timeStamp long, imei string, imsi string, deviceModel string, vendor string, osVersion string, osBuildDate string, batteryLevel double, totalInternalMemory double, availableInternalMemory double, totalExternalMemory double, availableExternalMemory double, operator string, connectionType string, mobileSignalStrength double, ssid string, cpuUsage double, totalRAM double, availableRAM double, pluggedIn bool); @Export('org.wso2.iot.BatteryStream:1.0.0') define stream outputStream (meta_deviceId string, meta_deviceType string, meta_timestamp long, level double, year int, month int, day int, hour int, minute int); from inputStream select meta_deviceId, meta_deviceType, timeStamp as meta_timestamp, batteryLevel as level, time:extract(time:timestampInMilliseconds(), 'year') as year, time:extract(time:timestampInMilliseconds(), 'day') as day, time:extract(time:timestampInMilliseconds(), 'hour') as hour, time:extract(time:timestampInMilliseconds(), 'minute') as minute insert into outputStream;

4. Click Add Execution Plan.

...

1. Access the WSO2 IoT Server's analytics management console.

   1. For access via secured HTTP: https://<IOTS_HTTPS_HOST>:9445/carbon/ 
For example: https://localhost:9445/carbon/

   2. For access via HTTP: http://<IOTS_HTTP_HOST>:9765/carbon/ 

      For example: http://localhost:9765/carbon/
2. On the Main tab click Data Explorer that is under Interactive Analytics.
3. From the Table Name* drop-down list, select BATTERY_LEVEL_PER_HOUR.
4. Click Search.

The data is displayed in the table format.

<Screenshot>

What's next

• Want to know more on the WSO2 IoT Server Siddhi extensions? See WSO2 IoT Server Siddhi Extensions.

• Try out the tutorials listed below and see how the extensions described above are put into use.

  • Sending Operations to Devices Based on Time

  • Applying Policies on Devices Based on Geofencing