Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision 		Previous revision
en:how_to_configure_trigger_and_action [2016/08/09 16:26]
127.0.0.1 external edit 		en:how_to_configure_trigger_and_action [2022/12/28 16:47] (current)
phit
Line 1: Line 1:
 {{tag>"​System Configuration"​ "​BioStar 2" "​Trigger and Action"​ Alert Setting}} {{tag>"​System Configuration"​ "​BioStar 2" "​Trigger and Action"​ Alert Setting}}
  
-====== How to configure Trigger and Action on Setting ====== +====== How to configure Trigger and Action on Setting ====== ​
-The trigger & action feature is used when you would like to send a custom output signal from a device or send an email to the administrator based on the occurrence of an alarm event. ​  +
-For instance, you can use this feature to trigger your alarm lamp when a forced door open alarm goes on. The system will simultaneously send an email to the administrator as well. \\ \\ +
-{{:​en:​2xtraining_trigger_action001.png?​nolink&​500|}} +
-\\+
  
-===== Available Triggers =====  +The trigger & action feature ​is used when you would like to send a custom output signal from a device or send an email to the administrator based on the occurrence of an alarm event. \\  ​
-Below is the full list of events that are available for triggers ​on the setting menu.\\ +
-Available events for Device: \\ +
-    *  Supervised Input (Open) +
-  *    Supervised Input (Short) +
-  *    Tamper On +
-  *    RS-485 disconnected +
-  *    Device restarted+
  
-<callout type="​primary"​ icon="​true">​  +For instance, you can use this feature to trigger your alarm lamp to go on simultaneously when a forced door open alarm goes on. The system can also simultaneously send an email to the administrator as well. \\ \\ 
-Supervised Input is used with a DM20. Please refer to [[en:​tc_appnote_dm20_wiring_examples]] for more information.  +
-</​callout>​+
  
-Available events for Door: \\ +{{:​en:​2xtraining_trigger_action001.png?​nolink&​500|}}  
-  * Held door open alarmed + 
-  * Forced door open alarmed +\\  
-  * Held door opened + 
-  * Forced door opened+   
 + 
 +===== Available Triggers =====   
 + 
 +Below is the full list of events that are available for triggers on the setting menu. [Available on BioStar 2 Version 2.9.0 ]\\  
 + 
 +Available events for Device: \\  
 + 
 +    *  AC Power Failure  
 + 
 +    *  Supervised Input (Open)  
 + 
 +    *  Supervised Input (Short)  
 + 
 +    *  Tamper on  
 + 
 +    *  RS-485 disconnected  
 + 
 +    *  RTSP disconnected  
 + 
 +    *  RTSP connected  
 + 
 +    *  Device restarted  
 + 
 +    *  Device Disconnection Detected  
 + 
 +    *  1:1 authentication succeeded (ID + PIN)  
 + 
 +    *  1:1 authentication succeeded (ID + Fingerprint)  
 + 
 +    *  1:1 authentication succeeded (ID + Fingerprint + PIN)  
 + 
 +    *  1:1 authentication succeeded (ID + Face)  
 + 
 +    *  1:1 authentication succeeded (ID + Face + PIN)  
 + 
 +    *  1:1 authentication succeeded (Card) ​  
 + 
 +    *  1:1 authentication succeeded (Card + PIN)   
 + 
 +    *  1:1 authentication succeeded (Card + Fingerprint) ​  
 + 
 +    *  1:1 authentication succeeded (Card + Fingerprint + PIN)  
 + 
 +    *  1:1 authentication succeeded (Card + Face)  
 + 
 +    *  1:1 authentication succeeded (Card + Face + PIN)  
 + 
 +    *  1:1 authentication succeeded (Card + Face + Fingerprint) ​  
 + 
 +    *  1:1 authentication succeeded (Card + Fingerprint + Face)   
 + 
 +    *  1:1 authentication succeeded (ID + Face + Fingerprint) ​  
 + 
 +    *  1:1 authentication succeeded (ID + Fingerprint + Face)   
 + 
 +    *  1:1 authentication succeeded (Mobile Card)   
 + 
 +    *  1:1 authentication succeeded (Mobile Card + PIN)  
 + 
 +    *  1:1 authentication succeeded (Mobile Card + Fingerprint) ​  
 + 
 +    *  1:1 authentication succeeded (Mobile Card + Fingerprint + PIN)  
 + 
 +    *  1:1 authentication succeeded (Mobile Card + Face)  
 + 
 +    *  1:1 authentication succeeded (Mobile Card + Face + PIN)  
 + 
 +    *  1:1 authentication succeeded (Mobile Card + Face + Fingerprint)  
 + 
 +    *  1:1 authentication succeeded (Mobile Card + Fingerprint + Face)  
 + 
 +    *  1:1 authentication failed (Mobile Card)   
 + 
 +    *  1:1 duress authentication succeeded (Card + Fingerprint) ​  
 + 
 +    *  1:1 duress authentication succeeded (Card + Fingerprint + PIN)  
 + 
 +    *  1:1 duress authentication succeeded (Card + Face + Fingerprint) ​  
 + 
 +    *  1:1 duress authentication succeeded (Card +Fingerprint + Face)   
 + 
 +    *  1:1 duress authentication succeeded (ID + Face + Fingerprint) ​  
 + 
 +    *  1:1 duress authentication succeeded (ID + Fingerprint + Face)   
 + 
 +    *  1:1 duress authentication succeeded (Mobile Card + Fingerprint)  
 + 
 +    *  1:1 duress authentication succeeded (Mobile Card + Fingerprint + PIN)   
 + 
 +    *  1:1 duress authentication succeeded (Mobile Card + Face + Fingerprint) ​  
 + 
 +    *  1:1 authentication succeeded (Mobile Card + Fingerprint + Face)   
 + 
 +    *  1: N authentication succeeded (Fingerprint)  
 + 
 +    *  1: N authentication succeeded (Fingerprint + PIN)  
 + 
 +    *  1: N authentication succeeded (Face)  
 + 
 +    *  1: N authentication succeeded (Face + PIN)  
 + 
 +    *  1: N authentication succeeded (Face + Fingerprint)  
 + 
 +    *  1: N authentication succeeded (Face + Fingerprint + PIN)  
 + 
 +    *  1: N authentication succeeded (Fingerprint + Face)  
 + 
 +    *  1: N authentication succeeded (Fingerprint + Face +PIN)   
 + 
 +    *  1: N duress authentication succeeded (Fingerprint) ​  
 + 
 +    *  1: N duress authentication succeeded (Fingerprint + PIN)   
 + 
 +    *  1: N duress authentication succeeded (Face + Fingerprint) ​  
 + 
 +    *  1: N duress authentication succeeded (Face + Fingerprint + PIN)  
 + 
 +    *  1: N duress authentication succeeded (Fingerprint + Face)   
 + 
 +    *  1: N duress authentication succeeded (Fingerprint + Face + PIN)  
 + 
 +    *  Dual authentication succeeded  
 + 
 +    * Access denied (Invalid access group)  
 + 
 +    * Access denied (Disabled user)  
 + 
 +    * Access denied (Invalid period)  
 + 
 +    * Access denied (Blacklist)  
 + 
 +    * Fake Fingerprint Detected ​  
 + 
 +    * Access denied (Anti-tailgating)  
 + 
 +    * Access denied (Exceeded threshold temp.)  
 + 
 +    * Access denied (Temp. Not measured correctly)  
 + 
 +    * Access denied (Mask not detected) ​  
 + 
 +    * Access granted (Check only)  
 + 
 +    * Access granted (Soft temp violation on check only)  
 + 
 +    * Access granted (Soft mask violation on check only)  
 + 
 +    * Access granted (Soft temp and mask violation on check only)   
 + 
 +    * Access denied (Exceeded threshold temp. On check only)  
 + 
 +    * Access denied (Temp. Not measured correctly)  
 + 
 +    * Access denied (Mask not detected on check only)   
 + 
 +    * Abnormal temp. detected (Exceeded threshold temp.) ​  
 + 
 +    * Mask not detected  
 + 
 +      
 + 
 +<callout type="​primary"​ icon="​true"> ​  
 + 
 +Supervised Input is used with a DM20. Please refer to [[en:​tc_appnote_dm20_wiring_examples]] for more information. ​  
 + 
 +</​callout>​  
 + 
 +   
 + 
 +Available events for Door: \\  
 + 
 +  * Held door open alarmed: can be used after setting Door>​Alarm>​Held Open  
 + 
 +  * Forced door open alarmed: can be used after setting Door>​Alarm>​Forced Open  
 + 
 +  * Held door opened: can be used after setting Door>​Door Sensor  
 + 
 +  * Forced door opened: can be used after setting Door>​Door Sensor ​
  
-Available events for Zone: \\ 
-  * Scheduled lock zone alarm detected 
-  * Fire alarm zone alarm detected 
-  * Anti-passback zone alarm detected 
        
-===== Setting Up a Custom Signal Output =====  
-In the scenario below, we will send a custom signal from our A2 when there is a forced open event. \\ 
-1. Click **Setting > TRIGGER & ACTION**. ​ \\ 
-{{:​en:​2xtraining_trigger_action003.png?​nolink&​350|}} \\ \\ 
-2. Click **ADD TRIGGER & ACTION**. \\ 
-{{:​en:​2xtraining_trigger_action005.png?​nolink&​300|}} \\ \\ 
-3. Enter a name for this trigger on the **Name** textbox. ​ \\ 
-4. Click on the schedule drop box. Click **+ Add Schedule**. If you have a preconfigured schedule, you can use that one by selecting it. \\ 
-{{:​en:​2xtraining_trigger_action006.png?​nolink&​700|}} \\ \\ 
-5. Configure the schedule as necessary and click **Ok**. In this case, I would like the trigger to be on all day except for Sunday. ​ \\ 
-{{:​en:​2xtraining_trigger_action008.png?​nolink&​700|}} \\ \\  
-6. Now select the newly created schedule on the **Schedule** drop box. \\ 
-7. Select the **Door** radio button. \\ 
-8. Select the door this will affect. The A2 is installed on Door 3 in this example. \\ 
-9. Check **Forced door opened**. \\ 
-10. Select your device (A2).  \\ 
-11. Relay 0 is already used for the door lock so relay 1 will be used for the output. ​ \\ 
-{{:​en:​2xtraining_trigger_action010.png?​nolink|}} ​   \\ \\  
-12. Click on the **Signal** drop down box. \\ 
-13. Click **Add Signal**. \\ 
-14. Fill in the details as desired and click **Apply**. \\ 
-{{:​en:​2xtraining_trigger_action012.png?​nolink&​500|}} \\ \\  
-15.Click on the **Signal** drop box and select the signal you just created and click **Apply**. ​  \\ 
-16. Now when there is a forced door open event, the custom signal is sent to relay 1.  \\ 
-{{:​en:​2xtraining_trigger_action014.png?​nolink&​|}} \\ \\  
  
-===== Setting Up an Email Alert on BioStar =====  +Available events for Zone: \\  
-1. Click **Setting ​> TRIGGER & ACTION**. \\ + 
-2. Click on your desired trigger. ​ \\  +  * Muster zone alarm detected  
-3. On Device / BioStar tab, click **BioStar** and check **BioStar**. \\ + 
-{{:​en:​2xtraining_trigger_action016.png?​nolink&​|}} \\ \\  +  * Occupancy Limit Violation (Count Full)  
-4. Click on the Gear icon on the action tab to setup your email. \\ + 
-{{:​en:​2xtraining_trigger_action018.png?​nolink&​|}} \\ \\  +  * Interlock door open denied alarm (Occupied)  
-5. Set up your SMTP. If you are not sure what the settings are, please ​ask your IT administrator. \\ + 
-{{:en:2xtraining_trigger_action020.png?​nolink&​400|}} \\ \\  +   * Interlock door open denied alarm  
-6. Add a **Recipient** and click **Apply**. \\ + 
-{{:en:2xtraining_trigger_action022.png?nolink&400|}} \\ \\  +  * Intrusion alarm detected  
-7. Now create a forced door open event. ​ \\ + 
-{{:​en:​2xtraining_trigger_action024.png?​nolink&​|}} \\ \\  +  * Occupancy Count Alert 2 Detected ​  
-8. The administrator will receive an alert email. \\ + 
-{{:en:2xtraining_trigger_action026.png?​nolink&​|}} \\ \\ +  * Occupancy Count Alert 1 Detected  
 + 
 +* Exit Occurred While Occupancy Count Zero   
 + 
 +  * Occupancy Availability Recovered ​  
 + 
 +  * Occupancy Full Detected  
 + 
 +* Scheduled lock zone alarm detected  
 + 
 +  * Fire alarm zone alarm detected  
 + 
 +  * Anti-passback zone alarm detected  
 + 
 +===== Setting Up a Custom Signal Output =====   
 + 
 +In the scenario below, we will send a custom signal from BioStation A2 Device when there is a forced opened trigger event. \\  
 + 
 +1. Click **Setting → TRIGGER & ACTION**. ​ \\  
 + 
 +{{:​en:​2xtraining_trigger_action003.png?​nolink&​350|}} \\ \\  
 + 
 +2. Click **ADD TRIGGER & ACTION**. \\  
 + 
 +{{:​en:​2xtraining_trigger_action005.png?​nolink&​300|}} \\ \\  
 + 
 +3. Enter a name for this trigger on the **Name** textbox. ​ \\  
 + 
 +4. Click on the schedule drop box. Click **+ Add Schedule**. If you have a pre-configured schedule, you can use that one by selecting it. \\  
 + 
 +{{:​en:​2xtraining_trigger_action006.png?​nolink&​700|}} \\ \\  
 + 
 +5. Configure the schedule as necessary and click **Ok**. In this case, I would like the trigger to be on all day except for Sunday. ​ \\  
 + 
 +{{:​en:​2xtraining_trigger_action008.png?​nolink&​700|}} \\ \\   
 + 
 +6. Now select the newly created schedule on the **Schedule** drop box. \\  
 + 
 +7. Select the **Door** radio button. \\  
 + 
 +8. Select the door this will affect. The BioStation A2 Device is installed on Door 3 in this example. \\  
 + 
 +9. Check **Forced door opened**. \\  
 + 
 +10. Select your device (BioStation A2).  \\  
 + 
 +11. Relay 0 is already used for the door lock so relay 1 will be used for the output. ​ \\  
 + 
 +{{:​en:​2xtraining_trigger_action010.png?​nolink|}} ​   \\ \\   
 + 
 +12. Click on the **Signal** drop down box. \\  
 + 
 +13. Click **Add Signal**. \\  
 + 
 +14. Fill in the details as desired and click **Apply**. \\  
 + 
 +{{:​en:​2xtraining_trigger_action012.png?​nolink&​500|}} \\ \\   
 + 
 +15.Click on the **Signal** drop box and select the signal you just created and click **Apply**. ​  \\  
 + 
 +16. Now when there is a forced door open event, the custom signal is sent to relay 1.  \\  
 + 
 +{{:​en:​2xtraining_trigger_action014.png?​nolink&​|}} \\ \\   
 + 
 +   
 + 
 +===== Setting Up an Email Alert on BioStar =====   
 + 
 +1. Click **Setting ​→ TRIGGER & ACTION**. \\  
 + 
 +2. Click on your desired trigger. ​ \\   
 + 
 +3. On Device / BioStar tab, click **BioStar** and check **BioStar**. \\  
 + 
 +{{:​en:​2xtraining_trigger_action016.png?​nolink&​|}} \\ \\   
 + 
 +4. Click on the Gear icon on the action tab to setup your email. \\  
 + 
 +{{:​en:​2xtraining_trigger_action018.png?​nolink&​|}} \\ \\   
 + 
 +5. Set up your SMTP. If you are unsure ​what the settings are, please ​follow this article → [[https://​support.supremainc.com/​en/​support/​solutions/​articles/​24000081661--biostar-2-how-to-configure-smtp-and-test-the-recipient-address|How to configure SMTP and Test the recipient address]]. \\  
 +{{:en:how_to_configure_trigger_action_smtp_section.jpg?​nolink&​400|}}\\ \\   
 + 
 +6. Add a **Recipient** and click **Apply**. \\  
 +{{:en:how_to_configure_trigger_action_received_email_section.jpg?noling&400|}} \\ \\   
 + 
 +7. Now create a forced door open event. ​ \\  
 + 
 +{{:​en:​2xtraining_trigger_action024.png?​nolink&​|}} \\ \\   
 + 
 +8. The administrator will receive an alert email. \\  
 + 
 +{{:en:how_to_configure_trigger_action_image.jpg?​nolink&​|}}\\ \\