Trigger Unlock
Trigger Unlock is a feature that allows users to define specific conditions under which an action, once locked, can be unlocked and allowed to execute again. This locking mechanism serves as a safeguard against repetitive or unwanted triggers, ensuring that actions only occur when truly necessary. Before reading this article, you should familiarize yourself with Trigger Conditions.
How It Works
By default, when a Trigger Condition is met, the corresponding action typically executes immediately. However, in scenarios where Trigger Unlock conditions are also defined, the action first enters a "locked" state upon meeting the initial Trigger Condition. This lock prevents the action from being triggered again until the specified Unlock conditions are met. This mechanism is particularly useful in scenarios where an action should only occur once under certain circumstances, allowing it to be triggered again after meeting other conditions.
Thus, each time a Trigger Condition is met, the trigger is locked if there is at least one Trigger Unlock condition. If the Trigger Conditions are met but there are no Trigger Unlock conditions, the action won't get locked.
You can check if your action is locked by looking at the Locked switch, as shown in the screenshot above. If the Locked switch is gray, it means your action is unlocked; if it's red, it means your action is locked. The lock button will only appear once you add at least one condition.
You can also set this Locked parameter manually; all you have to do is click it to toggle between Locked or not, and then hit Save.
Triggering the action again upon meeting unlock conditions
Additionally, you can run the action again when an unlock condition is met. For example, if you are triggering an Analysis to set a device in alert mode due to high-temperature readings, you can also switch to safe mode upon meeting an unlock condition.
Enabling a trigger when unlocked can lead to a duplicate triggered action.
Why Does This Exist?
One example of an undesirable situation could occur when you want to receive only one SMS when the temperature crosses above 95°C, but instead, you receive one SMS for each time a new value of temperature above 95°C is sent (95°C, 96°C, 97°C).
You may want to implement a hysteresis using a Trigger Unlock condition. If you define the condition to reset when the temperature is less than 90°C, for example, it would prevent this issue.
Only one SMS would be sent, and the system would remain locked until the temperature goes below 90°C, which seems much more reasonable in this example.
Related Articles
Trigger by Variable
The trigger type, Trigger by Variable allows you to execute your Actions when a variable meets certain conditions. If your device has sent data and the variables are meeting those conditions, this action will be triggered. There are 2 (two) ...Trigger by Usage Alert
The "Trigger by Usage Alert" is a feature that enables you to execute an Action when a specific service or resource meets predefined conditions. Below, you will find a list of Resources and Services that can be used to trigger your action. Resources ...Trigger by MQTT Topic
The trigger type, Trigger by Variable, allows you to execute your Action when data is sent to an MQTT topic. TagoIO has its own MQTT broker that is responsible for pushing data to clients in case something new is published in the specific topics they ...Trigger by Resource
The trigger type Trigger by Resource allows you to execute your Action when a resource meets certain conditions. A resource is one of the following: Access Management Actions Analysis Device RunUser For example, you can trigger an Action when a new ...Trigger by Geofence
The "Trigger by Geofence" feature allows you to execute an Action whenever a variable containing location data meets specific geofence conditions—either inside or outside a predefined area. For instance, you can configure an action to trigger when a ...