Objective

After completing this lab, you will be able to:

• use multiple rules in conjunction with each other to achieve a purpose
• explain how a pico is a first-class Internet citizen
• explain channels and how to manage them
• send events and queries to a pico using a browser, the event console, and the "Testing" tab

Reading and Reference

Read the following:

• Events and Queries Lesson Links to an external site.

You may find the following resources useful:

• KRL Manual 
• Developer Tips for the Pico Engine 
• The Event Intermediaries section from Live_Web_Chap_12.pdf Download Live_Web_Chap_12.pdf
  The Event Intermediary section of Live_Web_Chap_11.pdf Download Live_Web_Chap_11.pdf

Prerequisites

You should have completed:

• Lab 1: Events and Queries
• Lab 2: APIs and Picos

Implementation Notes

• You will be given a Wovyn temperature sensor as part of this lab. Refer to Wovyn Documentation Links to an external site. for more information about its operation. 
• The best way to use the KRL documentation is to search since you may not always appreciate how it's organized (or isn't).
• You can use various methods to send events Links to an external site. to your picos for testing. 
• You'll be modifying the rulesets that you create for this lessons in subsequent lessons. Be sure that the ruleset URLs you turn in for this lesson are unique from the URLs you provide later since this rulesets may not have been graded yet. You could do this by providing links to specific versions. 
• To send events to your pico, you will need the IP address of the machine that the pico engine is running on (along with the port that the pico engine is listening on).  
• To learn more about actions and compound actions, look at this documentation Links to an external site..

Do This

Do the following:

1. Write and register a ruleset named wovyn_base that contains a rule called process_heartbeat that responds to a wovyn:heartbeat event. This rule should return a directive.
2. Using the Pico Engine UI, create a pico that represents a temperature sensor and install your wovyn_base ruleset in it.
3. Using one of the techniques in Raising Events Links to an external site., test your ruleset.  Try it with various values for the sensor data to ensure it's working. 
4. Configure your Wovyn device to post a wovyn:heartbeat event to your temperature sensor pico. You'll need to format the temperature sensor's webhook URL to correspond to the Sky Event API Links to an external site. that your pico engine is expecting. You will need to create a channel for the temperature sensor to communicate with the pico.
5. Modify the process_heartbeat rule so that it will not fire unless there is a "genericThing" attribute present. See the Wovyn documentation for information on the structure of this attribute. Look at the implementation notes above for more info.
6. Modify the process_heartbeat rule to raise an event Links to an external site. with domain wovyn and type new_temperature_reading. The new event should include new attributes  for the temperature reading (called "temperature" and based on the content of the "genericThing" attribute) and a timestamp (called "timestamp"). Hint: event:attrs is a map of all attributes in the current event.
7. In the same ruleset, write a new rule named find_high_temps that selects on the wovyn:new_temperature_reading event. It should read the temperature attribute and, if it contains a value greater than the numeric value of the global variable named temperature_threshold, raises another event with domain wovyn, type threshold_violation, and any attributes passed along. Note, there are multiple ways to accomplish this.  You can pick any positive value for temperature_threshold that you like. The find_high_temps rule should issue a directive stating whether or not there was a temperature violation.
8. In the same ruleset, write another rule called threshold_notification that selects on the wovyn:threshold_violation event. The rule should use the SMS action you created in Lab 2: APIs and Picos to send a notification of the violation to a SMS number stored in a global variable in the ruleset. Note: you will need to install your Twilio module ruleset and your key's module in the temperature sensor pico. 
9. Use ruleset logging and debugging tools to convince yourself that your rules work.

Deliverables

Turn in the following:

1. URLs for your ruleset(s)
2. Short screencast (< 3 min with sound) showing the operation of your rulesets
3. Answers to the following questions:

Questions

1. What parsing method did you choose?
2. Did you accomplish step 5 with an event expression or a rule conditional? What are the advantages and disadvantages of the method you used instead of the other?
3. What was the output of the testing your ruleset before the find_high_temps rule was added? How many directives were returned? How many rules do you think ran?
4. What was the output of the test after the find_high_temps rule was added? How many directives were returned? How many rules do you think ran?
5. How do you account for the difference? Diagram the event flow within the pico (i.e. show the event flow from when the pico receives the first event to the directives being created) using a swimlane diagram Links to an external site..
6. Would you say that your find_high_temps rule is an event intermediary? If so, what kind? Justify your answer.
7. How do your logs show that the find_high_temps rule works? Pick out specific lines and explain them.