| "Hello, my name is Enkior. I will be your assistant to guide you in using your device within a scenario. I will explain the different possibilities available to you. Please note, the scenarios presented are only examples: they do not cover all existing possibilities." |
Article content:
-
Introduction.
-
Execute one or more actions with my device.
-
Schedule an action with my device.
-
Execute one or more actions with my device following an event.
Be notified during an event with my device.
-
Allow my scenario to execute one or more actions under certain conditions.
Things to know about scenarios.
Introduction:
How to create a scenario:
| "In this section, I will explain how to access the creation of your scenario so you can script your device. Please follow the explanations below." |
| Android: | iOS: |
| |
|
"Do you have questions? I am here to answer them. What happens when there are no scenarios in the "Scenarios" menu of the Enki app?
|
|
| Android: | iOS: |
What are the characteristics of a scenario:
|
"In this section, I will present the features and possibilities offered by your scenario. Indeed, a scenario allows you to perform a wide range of actions and customize its operation according to your needs." |
|
When creating your scenario, it is important to be able to identify it easily. For this, consider customizing the following option:
| |
| Scenario name |
|
|
You then access the scenario construction phase, which consists of the following three sections:
| ||
| When : | Trigger: |
|
| And only if: | Condition: |
|
| Then: | Action: |
|
|
When creating your scenario, you also have access to the following option:
| |
| Pin to home: |
|
|
"Once your scenario is pinned on the home screen, it will appear in your "Home" menu, as shown in the images below. By pressing the " Also, by long-pressing the scenario tile, you will access handy shortcuts." |
|
| Android: | iOS: |
|
|
Execute one or more actions with my device:
| "In this section, I will explain how to create a simple scenario with your device, to manually execute one or more actions simultaneously." |
|
"This type of scenario is called a manual scenario. But what is a manual scenario? A scenario is called manual when it requires a voluntary action to be launched, that is, it must be activated by yourself via the app, a button, a remote control, or a switch you have configured for this purpose." |
Action on one or more devices:
| "Here, I will show you how to create a simple manual scenario involving an action on a single device." |
Add an action to your scenario. | |
| Android: | iOS: |
|
|
|
Integrate the action of your device. |
||||
For this example, we will choose a desired temperature of 19°C. |
|
"How to integrate a new device or a new action into my scenario? Simply repeat the steps explained in the section "Add an action to your scenario", then in "Integrate the action of your device"." |
Save your scenario. |
|
||||
|
|
Test your scenario. |
||||
|
"In the example above, if your connected radiator is set to a desired temperature of 19°C as action #1, then when the scenario is executed, the device should react immediately in this way." |
Actions on the device with a delay:
| "In this section, I will show you how to create a manual scenario with a waiting delay. For example, you can put the device in one state, wait for a certain time, then switch it to another state." |
Add the first action to your scenario. | |
| Android: | iOS: |
|
|
|
Integrate the first action of your device. |
||||
|
|
"Now that the action of your device has been added to the scenario, we will add a waiting delay. This is particularly useful for "scheduled" actions to which you do not want to associate a precise time." |
Add the second action to your scenario. | |
| Android: | iOS: |
|
|
|
"What does the waiting delay correspond to? The waiting delay is the time that elapses between two actions in a scenario. |
| "For this example, we will set a delay of 03:00:00. Thus, after the execution of the first action, a three-hour delay will elapse before the second action triggers." |
Add the third action to your scenario. | |
| Android: | iOS: |
|
|
|
Integrate the second action of your device. |
||||
|
Save your scenario. |
|
||||
|
|
Test your scenario. |
||||
|
|
|||||
|
"Can we modify a scenario while it is running? No. Modification options are disabled while the scenario is running, as indicated by the message displayed on the screen. To modify it, you must first stop it, either by clicking the " |
|
|
|
"In the example above, you defined:
Thus, when the scenario is executed:
|
Programming an action with my device:
| "In this section, I will explain how to create a scheduled scenario to run at a specific time or during a defined period, in order to apply one or more actions simultaneously to your device." |
|
"This type of scenario is called a scheduled scenario. But what is a scheduled scenario? A scenario is called scheduled when it triggers automatically at a precise time or during a defined period, thanks to a time trigger. The actions planned in the scenario then execute without manual intervention." |
Scheduling at a specific time:
| "In this section, I will explain how to build a scenario that will run at a specific time." |
Add a trigger in your scenario. | |
| Android: | iOS: |
|
|
|
"The time you set to trigger the actions of your scenario is not linked to your phone's time nor your current location. The time taken into account is the one entered in your home's settings, including the country and the postal address provided." |
|
"Can multiple time triggers be set in the same scenario? Yes! Each time you add as a trigger in your scenario will trigger all the actions you have configured. |
Add your action in your scenario. | |
| Android: | iOS: |
|
|
|
Integrate your device's action. |
||||
For this example, we will choose a desired temperature of 19°C. |
|
"How to integrate a new device or a new action into my scenario? Simply repeat the steps explained in the section "Add your action in your scenario", then in "Integrate your device's action"." |
Save your scenario. |
|
||||
|
|
Test your scenario. |
||||
|
| "In the example above, the scenario is scheduled to trigger at 8:30 AM, Monday through Friday. At this time and on these days, your connected radiator will perform the action of setting to 19°C as action #1." |
|
"Warning, if you want your device to switch at another time to an opposite or different state, you must create a second scenario following the same construction method. Otherwise, you can also use the method of separating actions by one or more delays within a single scenario. For this, I invite you to consult the section "Actions on the device with a delay".." |
Scheduling at sunrise or sunset:
| "In this section, I will explain how to create a scenario that runs at sunrise or sunset." |
Add a trigger in your scenario. | |
| Android: | iOS: |
|
|
"The dawn or dusk period used to trigger actions in your scenario is not linked to your phone's time nor your current location. |
Add your action in your scenario. | |
| Android: | iOS: |
|
|
|
Integrate your device's action. |
||||
For this example, we will choose a desired temperature of 19°C. |
|
"How to integrate a new device or a new action into my scenario? Simply repeat the steps explained in the section "Add your action in your scenario", then in "Integrate your device's action"." |
Save your scenario. |
|
||||
|
|
Test your scenario. |
||||
|
| "In the example above, we defined a specific state, the temperature reading is below 15°C, for our connected radiator to trigger the scenario. Thus, when our connected radiator is in this state, the action to close, applied to the roller shutter, will be triggered." |
My device is triggered by a trigger:
| "In this section, I will explain how your device can be activated through another device. In other words, the execution of your device's actions will depend on the state of another device." |
Add one of your devices as a trigger in your scenario. | |
|
|
"In the list of devices, only those that can be used as triggers will appear. |
|
"Is it possible to integrate multiple states of one or more devices to trigger a scenario? Yes, absolutely. You can add multiple states, whether from the same device or different devices. |
| "In this example, we will use a door/window opening detector device, configured in the open state, to trigger the scenario." |
Add your device's action in your scenario. | |
| Android: | iOS: |
|
|
|
Integrate your device's action. |
||||
For this example, we will choose a desired temperature of 9°C. |
|
"How to integrate a new device or a new action into my scenario? Simply repeat the steps explained in the section "Add your device's action in your scenario", then in "Integrate your device's action"." |
Save your scenario. |
|
||||
|
|
Test your scenario. |
||||
|
|
"In the example above, we defined a specific state for one of your devices — a door/window opening detector — to trigger the scenario, namely the open state. Thus, when this device enters the defined state, the action of setting to 9°C configured in the scenario will be automatically executed on your device." |
Be notified during an event with my device:
| "In this section, I will explain how to receive a notification on your phone or tablet when an event occurs with your device." |
Add your device as a trigger in your scenario. | |
| Android: | iOS: |
|
|
|
Integrate the status of your device. |
||||
For this example, we will choose the heating state: yes. |
|
"Is it possible to integrate multiple states of my device to trigger a scenario? Yes, it is absolutely possible. You can add multiple states for your device or for other devices. |
Add the notification to receive in your scenario. | |
| Android: | iOS: |
|
|
|
"How many characters can I use in the notification message? The message must contain between 1 and 160 characters. It is not possible to have fewer or more. |
Save your scenario. |
|
||||
|
|
Test your scenario. |
||||
|
"In the scenario we created above, we configured the trigger as the heating being in the heating state: yes. |
|
"If you encounter difficulties with receiving notifications — such as delays or complete absence — I invite you to consult the following article, which may be helpful: |
Allow my scenario to execute one or more actions under certain conditions:
| "In this last part, I will explain how to create a scenario subject to execution conditions. In other words, a specific event triggers the scenario, but if this event occurs outside the defined conditions, the actions will not be executed." |
My scenario is conditioned by a time period:
| "In this section, I will explain how your device can be triggered by another device, based on a trigger and a time condition. In other words, your device's action depends both on the state of a trigger and a time slot during which this action is allowed." |
Add one of your devices as a trigger in your scenario. | |
|
|
"In the list of devices, only those that can be used as triggers will appear. |
|
"Is it possible to integrate multiple states from one or more devices to trigger a scenario? Yes, absolutely. You can add multiple states, whether from the same device or different devices. |
| "In this example, we will use a motion detector device, configured in the detected motion state, to trigger the scenario." |
Add the action of your device in your scenario. | |
| Android: | iOS: |
|
|
|
Integrate the action of your device. |
||||
For this example, we will choose a desired temperature of 21°C. |
|
"How to integrate a new device or a new action into my scenario? Simply repeat the steps explained in the section "Add the action of your device in your scenario", then in "Integrate the action of your device"." |
Add a time period condition in your scenario. | |
| Android: | iOS: |
|
|
|
"How to integrate a new condition in my scenario? Simply repeat the steps you performed in the section "Add a time period condition in your scenario"." |
| "In this example, the condition is that actions can only be executed from 08:30 to 12:45, Monday to Friday. Outside this time slot and these days, actions will not be triggered, even if the trigger state is reached." |
Save your scenario. |
|
||||
|
|
Test your scenario. |
||||
|
|
"In the example above, we defined a specific state on one of your devices, a motion detector, which triggers the scenario when it is in the detected motion state. A time condition must also be respected: the scenario will only run between 08:30 and 12:45, Monday to Friday. Thus, when the motion detector is in the defined state and only during this time slot and these days, the action to set your device to 21°C will be triggered. If the state occurs outside this time condition, the actions will not be executed." |
My scenario is conditioned by an event:
|
"In this section, I will explain how your device can be triggered by another event, conditional on a specific state of a device. In other words, your device's action depends both on the state of a trigger and a particular event during which this action is allowed. For the example, we will take a specific time as the trigger." |
Add a trigger in your scenario. | |
| Android: | iOS: |
|
|
|
"The time you set to trigger your scenario's actions is not linked to your phone's time nor your current location. The time considered is the one set in your home's settings, including the country and postal address entered." |
|
"Can multiple time triggers be defined in the same scenario? Yes! Each time you add as a trigger in your scenario will trigger all the actions you have configured. |
Add your action in your scenario. | |
| Android: | iOS: |
|
|
|
Integrate the action of your device. |
||||
For this example, we will choose a desired temperature of 21°C. |
|
"How to integrate a new device or a new action into my scenario? Simply repeat the steps explained in the section "Add your action in your scenario", then in "Integrate the action of your device"." |
Add an event-related condition in your scenario. | |
| Android: | iOS: |
|
|
|
"How to integrate a new condition in my scenario? Simply repeat the steps you performed in the section "Add an event-related condition in your scenario"." |
| "In this example, the condition will be that the door or window open/close detector is in the "closed" position, meaning the window is properly closed." |
Save your scenario. |
|
||||
|
|
Test your scenario. |
||||
|
"In the example above, the scenario is programmed to trigger at 08:30, Monday to Friday. |
|
"Attention, I want to warn you: if you want your device to switch to another state, or to the opposite state, at a different time, you will need to create a second scenario following the same construction method. However, it is also possible to separate actions by one or more delays within the same scenario you just created. |
|
"Congratulations, you now have the basics to create your scenarios with your device. Of course, the scenarios presented here are only examples, and many other possibilities exist." |
Things to know about scenarios:
What are the limits regarding the maximum number of triggers?
You can include up to fifty triggers in a scenario.
What are the limits regarding the maximum number of conditions?
You can include up to fifty conditions in a scenario.
What are the limits regarding the maximum number of actions?
You can include up to fifty actions in a scenario.
-
What is the minimum delay accepted for a timer?
The timer must be at least five seconds.
Android: iOS: How many wait delays can I include in my scenario?
It is possible to include up to five maximum delays in a scenario.
What is the maximum time that can be applied for a wait delay?
On Android, the interface allows entering a complete delay up to 23 hours, 59 minutes, and 59 seconds. On iOS, the selection is done by scrolling, with seconds in intervals of five, so the maximum is 23 hours, 59 minutes, and 55 seconds.
-
How do actions proceed?
Actions execute in the order you defined, from top to bottom in the list.
You can change this order by clicking on "Move" next to the "Then" section.
Android: iOS: My device does not appear in the list of device states in triggers, why?
Not all devices are eligible to trigger a scenario. If your device does not appear in the list, it is not eligible. You can check this in the product features table in Enki, on Noirot: Noirot Radiator - Product sheet.
My device does not appear in the list of device states in conditions, why?
Not all devices are eligible to be used as a condition limiting the triggering of a scenario. If your device does not appear in the list, it is not eligible. You can check this in the product features table in Enki, on Noirot: Noirot Radiator - Product sheet.
My device does not appear in the list of device states in actions, why?
Not all devices are eligible to perform an action in a scenario. If your device does not appear in the list, it is not eligible. You can check this in the product features table in Enki, on Noirot: Noirot Radiator - Product sheet.
I use a value to trigger my scenario, but sometimes it does not execute even though the value matches, why?
The trigger works like a threshold. The scenario executes only when the value crosses this threshold. If the value is already within the defined range, the scenario will not trigger again. Example: Suppose three values: A, B, and C. The scenario must execute when the value is greater than B, so at C. If the value is already C, the scenario will not execute. But if the value goes from A to B, then exceeds B to reach C, the scenario will execute because the threshold is crossed.
|
"If you have questions about your scenarios despite our detailed tutorial, do not hesitate to contact our technical support service. To speed up the processing of your request, please provide the following information:
Do not hesitate to provide as many details as possible so that our technicians can offer you effective support." |