On-event scenario is a sequence of actions of particular devices and system processes triggered by an action of other devices or process in Arloid Automation system which is realizable under certain conditions specified by the user.
The main feature of on-event scenarios is that they will be run automatically after a change in the status of a certain device (e.g., as the status of a fire safety sensor changes to “smoke detected” or water leak sensor changes its status with water coming on its contact). Such scenarios can be used for any purpose and involve any devices. We recommend applying on-event scenarios to notify of emergencies.
To create or adjust on event scenarios, go to HouseManager/Scenarios/On-event scenarios/.
Let’s say, we would like to give the following assignment to the system: as a leak detector is actuated, we want the water valve to be closed, Owner group to be notified with an SMS and Email, an alert message to appear in the status bar, and a loud voice alarm to be transmitted around the house.
To have this assignment completed, we need a scenario to be triggered by a leak detector. This means that as water comes on the leak detector, it will transmit a signal to the server. Arloid Automation system will recognize the signal as an event to run the scenario. As the scenario is implemented, the server will send relevant commands to the devices and generate notifications.
For our example let’s assume that the system has at least two devices: a leak detector and a water shutoff valve.
Please take the following steps to create the desired scenario:
7. For the parameter “Start on event” select the value “Leakage”.
Then set the other two main parameters: Time out for the next run (sec) and Start Timer (sec).
8. Time out for the next run is a period of time before the scenario will be run again in the case of repeated detector actuation. While leakage is being eliminated, the detector can be exposed to water again, and the system will resend the same messages. To prevent such resending, you can set time out, say, for 3 hours (10800 sec).
9. Start Timer determines the time period for which the detector condition “Leak detected” should persist so that the scenario will be run. Some detectors have transient triggers, also named “bounce”. The system will ignore such triggers and run scenarios only in the event of a real leakage. E.g., you can indicate 25 seconds here, so that the scenario will be run only if the leak detector continuously identifies leakage during the set period of time.
11. Open “Do” tab
13. For our case, select “Manage devices”
Note: for other variations of actions, see the end of this section
14. In “Devices” tab please select the subsystem and water supply valve on the first floor, as shown on Fig.4. Arloid Automation system normally sorts devices out of the list according to their location (room).
15. Confirm the selection
16. Please select the line with the action you’ve just created and press “Edit” if you would like to have an action other than the default one offered by the system.
17. Now please add another action “SMS”: indicate the text and select a group of recipients (Fig.6.1). In our example we assume that SMS and Email notification groups have been already set up.
To send a message to other groups, press the group selection key again. To clear the list, press the delete key (Fig.6.3).
17. Similarly, add Email, Audio message and Alert (a text that will appear in status bar). As a result, you will have a list looking like the one below.
Note: you can choose more than one word / phrase for an audio message to voice an action.
Now the scenario is ready. If the leak detector is actuated, notification messages will be sent, valves will be closed, and an alert will appear on the status bar of Main User Interface. After elimination of the leakage, Alert will automatically disappear.
Where necessary, create an additional condition so that the scenario will not be run unless this condition is met.
Scenario parameters include the following fields:
1. Run Scenario on event of this devices: this field will be automatically filled with the name of the device you choose from the device list when adding a new scenario. This device will transmit signals to trigger execution of the scenario.
2. Name: user-defined name of the scenario that will be shown in the general list of on even scenarios in HouseManager mode.
3. Start on event: please specify the status to which the main device (indicated in the first field) should switch to have the scenario triggered.
4. Timeout for the next run (sec) is a period of time (seconds) before the scenario will be run again. This function is especially useful for scenarios which include notification messages when one actuation is enough and there is no need to send extra messages after repeated actuation of the same detector.
5. Start Timer (sec): This timer filters "bouncing" of detectors and prevents multiple false activation of the scenario.
Start Timer takes into account the basic condition. Please activate this function so that a.System could start counting time between signals of the main device.
Start Timer takes into account the If condition. We recommend using this function if you use "additional conditions" to adjust the actions implied in the scenario.
Notification actions include Sound messages, SMS messages, Email, Logging and Alert. Normally, the system will perform those actions first (before commands for device actions are executed). Only one notification message of each type can be added to a scenario, but a notification command can include more than one sound and more than one notification group.
Device actions include three items: Manage devices, Manage groups of devices and Time out.
Important: please plan a sequence of actions to be performed in a scenario and arrange the lines in "Do" tab according to the sequence. "Time out" between two actions will provide a pause between those two actions.
Arloid Automation system supports multiple device choice for on event scenarios. Thanks to this function, you can implement very complex scenarios engaging a wide range of different devices, without knowledge of any programming languages.
1. In HouseManager mode select a scenario from the on-event scenario list and press "Edit".
2. Go to "If" tab
3. Press "Add": in a popup window you will see a list of all devices in Smart Home system and a list of system processes.
4. Select a device or system process whose operation or status will be considered for scenario running. For instance, in the event "Broken glass" the main condition is a signal from glass break sensor, and you can add another condition like "if security system is active". With this condition, the house owner will not be disturbed by the system reacting to a sound of accidentally broken dishware.