This section gives you a quick understanding of how to connect your device to WSO2 IoT Server and start using it. For this purpose, let's use the virtual fire alarm.
...
- Click Enroll New Device.
- Click Try to try out the Virtual Firealarm.
- Download the device:
- Click Download Agent to download the device agent.
Enter a preferred name for your device (e.g., "FireAlarm"), select the simple or advanced agent option, and click DOWNLOAD NOW.
| Tip |
|---|
Tip: Avoid using spaces or other characters for the device name. |
| Localtabgroup |
|---|
| Localtab |
|---|
| active | true |
|---|
| title | Simple Agent |
|---|
| Follow the steps below to start the Simple Agent. Navigate to the location of the unzipped device agent file on your terminal.
Example: Navigate to the device agent file, which is in the <IOTS_HOME>/device_agents/virtual_firealarm directory. | Code Block |
|---|
cd <IOTS_HOME>/device_agents/virtual_firealarm |
Start the virtual fire alarm. | Code Block |
|---|
sh start-device.sh |
Once you start your virtual fire alarm, the fire alarm emulator will pop up.  Image Modified
Try out the virtual fire alarmOnce you start your virtual fire alarm, you can try out the following actions: |
|
...
...
...
...
for the fire alarm device and start the Advanced Agent. Click the menu icon Image Modified , and click Policy Management. Click Add New Policy
|
|
...
and select the Virtual Fire Alarm platform. Configure a policy using the Siddhi Query Language and click Continue.
The following is an example of a policy you can use for the Fire Alarm device. See Adding a Policy for more information on how to add your own policy. | Code Block |
|---|
define stream fireAlarmEventStream (temp int);
from fireAlarmEventStream#window.time(30 sec)
select max(temp) as maxValue
insert into analyzeStream for expired-events;
from analyzeStream[maxValue < 50]
select maxValue
insert into bulbOnStream;
from fireAlarmEventStream[temp > 50]
select temp
insert into bulbOffStream; |
- Assign the policy to user roles or users and select an action to be triggered upon non-compliance.
For example, you can assign the policy to the admin user role and select Enforce as the action upon non-compliance. For more information, see Adding a Policy.
 Image Modified - Enter a name and description for the policy and click Publish.
 Image Modified
When you start the fire alarm device, this policy will be assigned to the device. Navigate to the location of the unzipped device agent file on your terminal.
Example: Navigate to the device agent file, which is in the <IOTS_HOME>/device_agents/virtual_firealarm directory.
| Code Block |
|---|
cd <IOTS_HOME>/device_agents/virtual_firealarm |
|
|
Start the virtual fire alarm. | Code Block |
|---|
sh start-device.sh |
Once you start your virtual fire alarm, the fire alarm emulator will pop up.  Image Modified
Try out the virtual fire alarmOnce you start your virtual fire alarm, you can try out the following actions: | Action | Description |
|---|
| View device details | Click the menu icon Image Modified, and click Device Management. Select the virtual fire alarm device you created from your devices, and view the device details, carry out operations, and monitor real-time data.  Image Modified
|
|---|
| Ring the fire alarm |
|---|
|
|
...
...
...
...
- emulator, enter a temperature lower than 50°. The buzzer will start ringing.
- Enter a temperature higher than 50° to stop the ringing.
|
|
|
...
Note that the buzzer now works according to the policy you defined above. |
|
|
View real-time and historical data
When you adjust the temperature and humidity values in the virtual fire alarm emulator you can see the data in real-time or view historical data by following the steps given below:
...
