Integrating AXIS Strobe Siren with CHeKT Automation Rules

Integrating AXIS Strobe Siren with CHeKT Automation Rules

🎯 Overview

The integration uses HTTP API calls from the CHeKT Automation Rules to trigger predefined profiles in the AXIS D4100-E device. You’ll need:

✅ 4 Profiles on the AXIS device
✅ 4 Automation Rules on the CHeKT platform
✅ HTTP POST commands using Digest Authentication

🏗️ Step 1: Create Profiles on the AXIS D4100-E Device

  1. Log into your AXIS D4100-E device via its IP address.

  2. Navigate to Profiles in the menu.

  3. Create the following 4 profiles:

Profile NameLight OutputSiren Output
AlarmAlternate, Red & BlueSiren: Falling Pitch
ArmedSteady, Red(No Siren)
DisarmedSteady, Green(No Siren)
EntrySteady White + Flash, YellowNotification: Entry

✅ Make sure profile names exactly match what you’ll reference in the HTTP command.

📸 Reference Image




⚙️ Step 2: Configure Automation Rules in CHeKT

  1. Log into your CHeKT Site Portal and go to Site Details → Automation Rules.

  2. Create 4 Automation Rules:

Rule NameSource Event
Armed LightSystem State Change → Site Armed
Disarmed LightSystem State Change → Site Disarmed
Entry Timer LightSystem State Change → Entry Begins
System In Alarm LightSystem State Change → Alarm Begins

For each rule:

✅ Action Type → HTTP Request
✅ Method → POST
✅ URL → http://[Device_IP_or_mDNS]/axis-cgi/siren_and_light.cgi
✅ Authentication → Digest Auth (use the Axis device credentials)

📝 HTTP Request Body

For each rule, send the following JSON body (update the profile parameter to match the desired AXIS profile):

{
  "apiVersion": "1.0",
  "context": "my context",
  "method": "start",
  "params": {
    "profile": "Armed"
  }
}
EventProfile Value
Site ArmedArmed
Site DisarmedDisarmed
Entry BeginsEntry
Alarm BeginsAlarm

👉 Replace "Armed" in "profile": "Armed" with the corresponding Profile Name for each rule.

✅ Don’t forget quotes and commas—this JSON must be formatted correctly!

📸 Reference Image


🔐 Important Notes:

  • You must use Digest Authentication for the HTTP request (required by the Axis device).

  • Test each rule by manually triggering the event (arming/disarming/entry/alarm) to verify the correct light and siren output.

  • Axis profiles are priority level 3 by default; adjust if you need a different override behavior.

🎬 Example Workflow:

✅ Arming the system?
→ CHeKT triggers the HTTP POST
→ AXIS activates Armed profile (steady red light)

✅ CHeKT System goes into Alarm Status
→ CHeKT triggers HTTP POST
→ AXIS activates Alarm profile (red/blue alternating light + siren)



✅ Final Checklist:

✔ 4 profiles created on Axis device
✔ 4 automation rules created on CHeKT site
✔ HTTP POST URL uses correct device IP/mDNS
✔ JSON body references correct profile name
✔ Digest Authentication credentials are valid
✔ Each event triggers corresponding light/siren action