| "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. Note, the scenarios presented are only examples: they do not cover all existing possibilities." |
Introduction:
How to create a scenario:
| "In this section, I will explain how to access the creation of your scenario so you can set up your device in a scenario. Please follow the explanations below." |
| Android: | iOS: |
| |
|
"Do you have questions? I am here to answer them. What happens when no scenario is present 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 personalizing the following option:
| |
| Scenario name |
|
|
You then access the scenario construction phase, which consists of the following three sections:
| |
| Trigger: |
|
| Condition: |
|
| 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 tapping the " |
|
| Additionally, 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 deliberate action to be launched, meaning you must activate it 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 your device’s action. |
||||
| |||||
For this example, we will choose "Advanced lighting configuration" and "State: On / Brightness: 50% / White: 2750K". | |||||
|
"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 your device’s action" above." |
Save your scenario. |
|
||||
|
|
Test your scenario. |
||||
|
| "In the example above, if your Inspire connected fan is set to "State: On / Brightness: 50% / White: 2750K" as action #1, then when the scenario runs, the device should immediately respond 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 wait delay. For example, you can set the device to one state, wait some time, then switch it to another state." |
Add the first action to your scenario. | |
| Android: | iOS: |
|
|
|
Integrate the first action of your device. |
||||
| |||||
For this example, we will choose "Turn On / Off" and "State: On / Functionality: Light". | |||||
| "Now that your device’s action has been added to the scenario, we will integrate a wait delay. This delay triggers a new action a certain time after the first. |
|
| This is particularly useful for "scheduled" actions to which you do not want to associate a specific time." | |
Add the second action to your scenario. | |
| Android: | iOS: |
|
|
|
"What is the wait delay? The wait delay is the time elapsed between two actions in a scenario. |
|
| It is a simple way to shift the execution of your scenario’s actions over time." | |
| "For this example, we will set a delay of 03:00:00. Thus, after executing 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. |
||||
| |||||
For this example, we will choose "Turn On / Off" and "State: Off / Functionality: Light". | |||||
Save your scenario. |
|
||||
|
|
Test your scenario. |
||||
|
|
|||||
|
"Can a scenario be modified 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 tapping the " | |||||
|
|
|
"In the example above, you defined:
Thus, when the scenario runs:
|
Schedule 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, 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-based trigger. The actions planned in the scenario then execute without manual intervention." |
Schedule at a precise time:
| "In this section, I will explain how to build a scenario that will execute at a precise time." |
Add a trigger to your scenario. | |
| Android: | iOS: |
|
|
|
"The time you set to trigger your scenario’s actions is not linked to your phone’s time or your current location. The time taken into account is that entered in your home settings, including the country and 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 to your scenario. | |
| Android: | iOS: |
|
|
|
Integrate your device’s action. |
||||
| |||||
For this example, we will choose "Turn On / Off" and "State: On / Functionality: Fan". | |||||
|
"How to integrate a new device or a new action into my scenario? Simply repeat the steps explained in the section "Add your action to 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 Inspire connected fan will perform the action of turning on its fan as action #1." |
|
"Note, if you want your device to switch to a different or opposite state at another time, you must create a second scenario following the same construction method. Alternatively, you can 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"." |
Schedule at sunrise or sunset:
| "In this section, I will explain how to create a scenario that runs at sunrise or sunset." |
Add a trigger to your scenario. | |
| Android: | iOS: |
|
|
"The dawn or dusk period used to trigger actions in your scenario is not linked to your phone’s time or your current location. |
Add your action to your scenario. | |
| Android: | iOS: |
|
|
|
Integrate your device’s action. |
||||
| |||||
For this example, we will choose "Turn On / Off" and "State: On / Functionality: Light". | |||||
|
"How to integrate a new device or a new action into my scenario? Simply repeat the steps explained in the section "Add your action to 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 one hour after dusk, Monday through Friday. At this time and on these days, your Inspire connected fan will perform the action of turning on its light as action #1." |
Execute one or more actions with my device following an event:
| "In this section, I will explain how to create a scenario triggered by an event, whether this event is generated by your device or another element." |
|
"This type of scenario is called an event-driven scenario. But what exactly is an event-driven scenario? A scenario is called event-driven when it automatically triggers due to a change in the state of a device. |
My device triggers the action:
| "In this section, I will explain how your device can trigger a scenario to perform one or more actions on one or more devices." |
Add your device as a trigger in your scenario. | |
| Android: | iOS: |
|
|
|
Set the state of your device. |
||||
For this example, we will select "On" and "Fan". |
|
"Is it possible to include 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 your action in your scenario. | |
| Android: | iOS: |
|
|
|
"How do I add a new device or a new action to my scenario? Simply repeat the steps explained in the section "Add your action in your scenario."" |
| "Only devices eligible to receive an action will appear in the device list. If your device is not visible, it means either it is not eligible to be used in a scenario as an action, or it cannot physically perform an action." |
| "For this example, we will use an air conditioner that will perform the action of turning on." |
Save your scenario. |
|
||||
|
|
Test your scenario. |
||||
|
|
"In the example above, we defined a specific state — the fan turned on — for our Inspire connected fan to trigger the scenario. Thus, when our Inspire connected fan is in this state, the action to turn on the air conditioner will be triggered." |
My device is controlled 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. | |
|
|
"Only devices that can be used as triggers will appear in the device list. |
|
"Is it possible to include multiple states from one or more devices to trigger a scenario? Yes, absolutely. You can add multiple states, whether from the same device or from different devices. |
|
| To do this, simply repeat the steps described in the section "Add one of your devices as a trigger in your scenario". ⚠️ However, be careful not to create a loop that would continuously trigger your scenario, which could cause a malfunction in your setup." | |
| "In this example, we will use a connected thermometer in the state of a recorded temperature above 25°C to trigger the scenario." |
Add your device's action in your scenario. | |
| Android: | iOS: |
|
|
|
Set your device's action. |
||||
| |||||
For this example, we will choose "Turn On / Off" and "State: On / Feature: Fan". | |||||
|
"How do I add a new device or a new action to my scenario? Simply repeat the steps explained in the section "Add your device's action in your scenario", then in "Set 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 connected thermometer — to trigger the scenario, namely the state of a detected temperature above 25°C. Thus, when this device enters the defined state, the action to turn on the fan configured in the scenario will be automatically executed on your device." |
Be notified of 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: |
|
|
|
Set the state of your device. |
||||
For this example, we will select "On" and "Fan". |
|
"Is it possible to include 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. |
|
| However, be careful not to create a loop that would continuously trigger the scenario, which could cause a malfunction in your setup." | |
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 use fewer or more. |
Save your scenario. |
|
||||
|
|
Test your scenario. |
||||
|
| "In the scenario we created above, we configured as a trigger that the Inspire connected fan is in the On state for its fan function. When this state occurs on your device, you will receive the customized push notification you set up." |
|
"If you experience difficulties receiving notifications — such as delays or no notifications at all — 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, depending on a trigger and a time condition. In other words, your device's action depends both on the trigger's state and on a time window during which this action is allowed." |
Add one of your devices as a trigger in your scenario. | |
|
|
"Only devices that can be used as triggers will appear in the device list. |
|
"Is it possible to include multiple states from one or more devices to trigger a scenario? Yes, absolutely. You can add multiple states, whether from the same device or from different devices. |
| "In this example, we will use a connected thermometer configured in the state of a detected temperature above 25°C to trigger the scenario." |
Add your device's action in your scenario. | |
| Android: | iOS: |
|
|
|
Set your device's action. |
||||
| |||||
For this example, we will choose "Advanced lighting configuration" and "State: On / Brightness: 100% / White: 5000K". | |||||
|
"How do I add a new device or a new action to my scenario? Simply repeat the steps explained in the section "Add your action in your scenario", then in "Set your device's action"." |
Add a time condition in your scenario. | |
| Android: | iOS: |
|
|
|
"How do I add a new condition to my scenario? Simply repeat the steps you performed in the section "Add a time condition in your scenario"." |
| "In this example, the condition is that actions can only execute from 8:30 AM to 12:45 PM, Monday through Friday. Outside this time frame and these days, the actions will not be launched, 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, the connected thermometer, which triggers the scenario when it is in the state of a detected temperature above 25°C. A time condition must also be respected: the scenario will only run between 8:30 AM and 12:45 PM, Monday through Friday. Thus, when the connected thermometer enters the defined state and only during this time window and these days, the action to turn on the fan applied to your device will be triggered. If the state occurs outside this time condition, the action 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, subject to a specific state of a device. In other words, your device's action depends both on the state of a trigger and on 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 the actions of your scenario is not linked to your phone's time nor your current location. The time considered is the one entered in your home's settings, including the country and 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: |
|
|
|
Set your device's action. |
||||
| |||||
For this example, we will choose "Advanced lighting configuration" and "State: On / Brightness: 100% / White: 5000K". | |||||
|
"How do I add a new device or a new action to my scenario? Simply repeat the steps explained in the section "Add your action in your scenario", then in "Set your device's action"." |
Add an event-related condition in your scenario. | |
| Android: | iOS: |
|
|
|
"How do I add a new condition to 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 connected receiver for the roller shutter is in the "closed" position, meaning the shutter is fully closed." |
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 Inspire connected fan will perform the action of turning on its light at 100% brightness and on a 5000K white as action #1, provided that the shutter is in the expected state, i.e., closed. If the shutter is open (even 1%), then the action will not be executed." |
|
"Warning, I want to alert 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 just 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 accepted delay for a timer?
The timer must be at least five seconds.
Android: iOS: How many wait delays can I include in my scenario?
You can 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 full delay up to 23 hours, 59 minutes, and 59 seconds. On iOS, selection is done by scrolling, with seconds in five-second intervals, so the maximum is 23 hours, 59 minutes, and 55 seconds.
-
How do actions execute?
Actions execute in the order you defined, from top to bottom in the list.
You can change this order by clicking "↑↓" or "Move" next to the "Action" 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 verify this in the product features table in Enki, on the Inspire fans product sheets.
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 verify this in the product features table in Enki, on the Inspire fans product sheets.
My device does not appear in the list of device states in actions, why?
Not all devices are eligible to execute an action in a scenario. If your device does not appear in the list, it is not eligible. You can verify this in the product features table in Enki, on the Inspire fans product sheets.
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 only executes 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 should execute when the value is greater than B, i.e., at C. If the value is already C, the scenario will not execute. But if the value moves 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 our technicians can offer you effective support." |