Automation Rule Scenarios: Common and Advanced Use-Case Examples

With the 5.0 Firmware Version, the array of options to build, filter and suppress CHeKT Automated Rules have been expanded. The purpose of this article is to share some examples of rule combinations that can be used for practical applications in the field.

Need to set up your first automation rule? Stop here first: Automation Rules Setup Guide

Protected Public Area: Increasing warning intensity with time

Have a camera looking at a public pool? Use an Automated Rule to clear out subjects who are in the area past closing without the need to contact the local authorities. 

Ensure there is a camera with a detection area covering the pool. Intrusion and Loitering zones are generally recommended for this. Cover the internal gated area with the analytic rule. 

Create an automated rule with a friendly reminder message:

Source Event: Camera Triggered

 

Action: Talkdown

 

This is a friendly message informing guests that they pool is closing soon, and they need to make their way to the exit.



Operational Condition: Time 







Here we will ensure that the message only plays in the 10 minutes approaching pool closure time:




Don't forget to add labels for ease of service: 

.

Add an additional rule with a less-than-friendly message:

Source: Camera triggered : Same Camera Source

 

This time, we will choose a less friendly Talkdown Message to Broadcast:

 

Our filter will be the entire time the pool is closed:

Label the rule of ease-of-service:
 

All of the details of the newly created rules are visible at a glance in the Automation Rule Menu

This ruleset is now ready to go. Any time a person activates the pool camera during the 10 minutes approaching closing time, the Friendly "pool is closing" message will be played. If that activation takes place during the time the pool is closed, a more aggressive message will play. 

Entry and Exit Sequencing: Ensuring the rules and annunciators activate at the intended times.

The CHeKT System can now integrate the entry, exit and alarm countdowns into the rule programming. This will allow the dealer to ensure an Audio Talkdown message does not activate during the entry sequence, for instance. 

Creating an Automated Audio Talkdown Message that will not play during entry or exit sequencing:

Source Event: Camera Triggered

 

Action: Talkdown

 

Operational Conditions: System Status - While in Alarm:

AI Operator will Filter the Rule based on the results of the CHeKT Cloud AI Filtering Engine. To use, Ensure Cloud AI is enabled and correctly configured. 

1. https://support.chekt.com/portal/en/kb/articles/chekt-ai-filtering-setup-guide-and-best-practices

If the AI Operator Checkbox is checked, the rule will take ~5-10 seconds longer to activate while waiting for the Cloud AI Determination 

Label the Rule:

This rule will now only activate when a camera is triggered while the system is in alarm condition and a valid subject is confirmed by the AI engine.

1. The alarm condition duration is determined by the Bell Timer Setting in the CHeKT Arming Configuration
   
2. If the system user enters the detection area of a camera that is listed as an entry exit zone, no automatic talkdown message will be activated if they disarm the system prior to alarm activation.  

If there is a requirement for the initial alarm activation event (such as the expiration of the entry timer) to generate an automated Talkdown Message as well, this can be accomplished with an additional rule:

Creating an Automated Audio Talkdown Message on Initial Alarm Activation:

Source Event : When System State Changes - When System Alarm Begins

Action: Talkdown

 

Proceed in the same fashion as the previous rule to save and complete.

Since this condition is initiated the moment the system enters alarm, no additional filters are required. 

Any time an alarm condition begins on that site, the talkdown message will be activated. If the defined subject (defined in Cloud AI Settings ) is verified by the AI operator to enter any other camera detection area, since the system is already in alarm, the sequence will initiate an additional talkdown event. This condition will remain until the Bell Timer has expired. 

Using Automation Rules and System Timers to initialize Visual Indicators or Annunciators

One of the most versatile options available in the CHeKT Solution is the ability to leverage our automation rules to initiate local API calls to devices on the same LAN as the CHeKT Bridge. As an example this article outlines a standard setup for initiating a relay state-change in the CHeKT camera. 

The Following Ruleset is an example of a way to use the lights and speakers on a local camera to signify the current system arming or countdown state to the end user. 

Source Event: System Status Changes - When Site Entry Delay Begins

For Actions, we are going to start by selecting an audible message to inform the customer they need to disarm the system:

Users can add up to 5 Actions. 

For this rule, we will . 

For the second action, we will add a visual signifier:

 For this example, we will illuminate the Red LED on the CHeKT Turret Camera. The URL was obtained from this article.

For step 3, we will opt to skip the condition for this example, as we are only activating this rule during the start of the entry sequencing. Users could additionally opt to filter by time, if preferred.

Label the Rule: More complicated rules justify more detailed labels.

Click Next to create the rule.

Now with that rule created, any time the system entry timer is initiated when a subject enters an entry/exit zone during an armed condition, the "please disarm the system" message will play twice, and the Red LED on the Camera will be Illuminated.

We can also add an independent rule/action for when the system enters an Alarm State. For our example today, we will engage the flashing multi-color lights and siren noise from the CHeKT Turret Camera when the countdown ends (or an instant zone is violated during an armed condition).

Source Event: System State Changes - When System Alarm Begins:

For the source event, we will use the same IP as the camera but send the command to initiate the flashing red/blue lights and siren noises:

Label the rule:

Finally, we will add one more rule to ensure that camera will return to a normal, lights-off state when the disarm comes in.

Source Event: System State Changes - When Site is Disarmed

Action will include an HTTP Request with the command to turn off all LEDs:

Label with action information:

Now with the 3 rules listed, the site will behave as follows:

1. When the end-user enters the detection area of any camera listed as an entry exit zone during an armed condition (activating the system entry timer), the System will automatically play the message Please disarm the system. You have 1 minute before the system enters alarm twice, and illuminate the Red LED  on the Turret camera at the specified IP Address. 
   
2. If the 60 second entry timer expires after an entry zone is violated (or an instant zone is violated) while armed, the system will enter an alarm condition, and our second rule will activate the siren noises and police-colored lights on the turret camera. 
   
3. When the system is disarmed, the lights on the camera will be deactivated. 
   

These are just a few examples of the many ways Automation Rules can create an intelligent solution for your users; we hope this helped spark some of your creative site-solutions as well. 

Thanks for reading!

• Related Articles

• Automation Rules

  CHeKT is proud to announce the public release of the Automation Rules. When this function is enabled, the integrator is granted access to a wide range of new site-level functions that can create a unique, custom experience for their client. Need the ...

• List of known and Tested HTTP Commands for Camera Functions

  Dealers can use CHeKT Automation Rules to create web requests on local devices out the the field. The chart below lists HTTP URLs that have been verified to work with the listed model. If you are looking for a CHeKT Camera URL request that is not ...

• Creating an Automated HTTP Request in IP Cameras

  This guide will outline how CHeKT Portal Users can use the "HTTP Request" option in the CHeKT Automation Rule programming menu to activate camera functions such as relays or lights. Automation Rules Require the CHeKT Professional Dealer Plan: ...

• CHeKT 4MP Turret Camera : Advanced Features FAQ

  This article is designed as a compilation of some of our more advanced Dealer Inquires about internal camera functions. Contact support if you are having trouble working with or understanding a feature in the camera; it may get added to this list. If ...

• Analytic Triggers: Using Camera Analytics

  Analytic Events Supported analytic event triggers from a camera mounted to the bridge can generate alarm signals and video events. These events are based on a supported API connection with the camera. The network event message has topic information ...