Now we’ll look at triggers based on “A Devices Value is…”. In the screenshot below the dropdown is expanded and gives all of the choices
When you select the Trigger type you will be prompted for a Device
When you select the Device, you will be prompted for a Status or Value to Trigger on
You simply choose the Device's Status on which you want the Trigger to become True.
In addition to a Value or Status, you can trigger on an Invalid or Error State. This is covered in the Virtual Devices Forum here.
This trigger is the first to offer a choice that can lead to a runaway event. You will note that all of the choices except one are based upon the Value of a device being changed or set or at a Value for a specific period of time. These are all a “moment in time” type of trigger and will trigger only once each time the device is set or changed. Below is an example of the one trigger that presents a “gotcha” – "This device has been for at least…"
The problem with using this as a trigger is that it will continually trigger (about once a second) as soon as the First Floor Kitchen Overhead Light has been on for more than 15 minutes. This event will trigger until the light is turned off. If this trigger were to turn the light off it is a very safe trigger, but if you are using it to control another device or to speak something, it will continually do so until the light is turned off. There is an event option that will keep an event from running again for a fixed period of time that will be covered a little later in this thread. As a preventative measure, it is always good practice to set that option on any event that could continually trigger. There are not many triggers allowed that will present this hazard, but we will point them out on all of the core triggers. The lesson to be learned is to think clearly about what will cause a trigger to be true and make sure that it is a “moment in time” or that the event itself makes the trigger false.
The second choice of a Device Value and time is "This device has been/for exactly..." is a much safer option.
This Trigger is only true at the exact period of time. It will only trigger once.
The rest of the Triggers are based upon the Value of the Device being “Set” or Changing. There is in important distinction between the two. A device value is “Set” when it is commanded to be a value, either by local control or by HS control. The value does not have to change. For example if a light switch is On and it is commanded to be On, the value doesn’t change, but it has been “Set”. This is a very important distinction when triggering off of a Central Scene or remote control. On these devices, you may press a button to perform an operation. You may press the same button again hours later. The second press will not result in a change of value, but the value will be Set. When you use the trigger “This Device had its value set to…” it will be true any time the device value is set, but not necessarily changed.
When you select the Trigger type you will be prompted for a Device
When you select the Device, you will be prompted for a Status or Value to Trigger on
You simply choose the Device's Status on which you want the Trigger to become True.
In addition to a Value or Status, you can trigger on an Invalid or Error State. This is covered in the Virtual Devices Forum here.
This trigger is the first to offer a choice that can lead to a runaway event. You will note that all of the choices except one are based upon the Value of a device being changed or set or at a Value for a specific period of time. These are all a “moment in time” type of trigger and will trigger only once each time the device is set or changed. Below is an example of the one trigger that presents a “gotcha” – "This device has been for at least…"
The problem with using this as a trigger is that it will continually trigger (about once a second) as soon as the First Floor Kitchen Overhead Light has been on for more than 15 minutes. This event will trigger until the light is turned off. If this trigger were to turn the light off it is a very safe trigger, but if you are using it to control another device or to speak something, it will continually do so until the light is turned off. There is an event option that will keep an event from running again for a fixed period of time that will be covered a little later in this thread. As a preventative measure, it is always good practice to set that option on any event that could continually trigger. There are not many triggers allowed that will present this hazard, but we will point them out on all of the core triggers. The lesson to be learned is to think clearly about what will cause a trigger to be true and make sure that it is a “moment in time” or that the event itself makes the trigger false.
The second choice of a Device Value and time is "This device has been/for exactly..." is a much safer option.
This Trigger is only true at the exact period of time. It will only trigger once.
The rest of the Triggers are based upon the Value of the Device being “Set” or Changing. There is in important distinction between the two. A device value is “Set” when it is commanded to be a value, either by local control or by HS control. The value does not have to change. For example if a light switch is On and it is commanded to be On, the value doesn’t change, but it has been “Set”. This is a very important distinction when triggering off of a Central Scene or remote control. On these devices, you may press a button to perform an operation. You may press the same button again hours later. The second press will not result in a change of value, but the value will be Set. When you use the trigger “This Device had its value set to…” it will be true any time the device value is set, but not necessarily changed.
Comment