Trigger Types
This reference documents all trigger types available in Anava profiles and when to use each.
Trigger Overview
| Trigger | Source | Best For |
|---|---|---|
| Motion | Camera VMD | General-purpose |
| Object | AXIS Object Analytics | Pre-filtered detection |
| Perimeter | AOAS perimeter scenarios | Boundary monitoring |
| PerimeterDefender | Advanced perimeter | Complex scenarios |
| DigitalInput | Physical I/O | Sensors, doors |
| Manual | Virtual input | VMS/operator initiated |
| Schedule | Time-based | Continuous monitoring |
| None | (disabled) | Profile inactive |
Motion Trigger
Description
Uses the camera's built-in Video Motion Detection (VMD).
Configuration
Trigger:
Type: Motion
No additional settings required.
When to Use
- Camera doesn't support AOAS
- Need to detect any movement
- Low-traffic areas
- Backup trigger type
Considerations
- Higher false positive rate (shadows, lighting, weather)
- All motion triggers analysis
- Combine with pre-filter in skill
Object Trigger
Description
Uses AXIS Object Analytics (AOAS) for pre-classified detection.
Configuration
Trigger:
Type: Object
Profile: person # AOAS scenario name
Profile Values
| Profile | Detects |
|---|---|
| person | Human presence |
| vehicle | Cars, trucks, etc. |
| face | Face detection |
| any | Any AOAS detection |
When to Use
- Camera supports AOAS
- Need pre-filtered events
- Cost optimization important
- Reducing false positives
Prerequisites
- AOAS enabled on camera
- Matching scenario configured
- Camera firmware supports AOAS
Perimeter Trigger
Description
Uses AOAS perimeter scenarios (line crossing, zone intrusion).
Configuration
Trigger:
Type: Perimeter
Profile: crossline # Scenario type
ID: scenario-1 # Specific scenario ID
Profile Values
| Profile | Description |
|---|---|
| crossline | Line crossing detection |
| intrusion | Zone intrusion |
| loitering | Time in area |
When to Use
- Virtual perimeter monitoring
- Entry/exit detection
- Restricted area monitoring
Prerequisites
- AOAS perimeter scenario configured
- Detection area defined
- Object filter set
PerimeterDefender Trigger
Description
Advanced perimeter detection with AXIS Perimeter Defender.
Configuration
Trigger:
Type: PerimeterDefender
Profile: scenario-name
ID: specific-scenario-id
When to Use
- High-security perimeter
- Long-range detection needed
- Advanced intrusion scenarios
- Integration with radar
Prerequisites
- AXIS Perimeter Defender license
- Scenario configured on camera
- Appropriate camera placement
DigitalInput Trigger
Description
Physical I/O port signal from external sensors.
Configuration
Trigger:
Type: DigitalInput
Port: 1 # I/O port number (1-8)
Port Configuration
| Port | Typical Connection |
|---|---|
| 1 | Door contact |
| 2 | PIR sensor |
| 3 | Alarm panel |
| 4 | Access control |
| 5-8 | Additional sensors |
When to Use
- Door/window sensors
- External PIR detectors
- Alarm panel integration
- Physical button triggers
- Reliable event source
Wiring Notes
- Normally Open (NO) or Normally Closed (NC)
- Configure in camera I/O settings
- Verify signal levels
Manual Trigger
Description
Virtual input triggered by VMS or API.
Configuration
Trigger:
Type: Manual
Port: 6 # Virtual input port (typically 6)
Activating Manual Trigger
Via HTTP (VAPIX):
# Activate (trigger analysis)
GET http://[camera-ip]/axis-cgi/io/virtualinput.cgi?action=6%3A%2F
# Deactivate (reset)
GET http://[camera-ip]/axis-cgi/io/virtualinput.cgi?action=6%3A%5C
When to Use
- Operator-initiated verification
- VMS action rule integration
- API-driven analysis
- On-demand assessment
- Integration with other systems
VMS Integration
Configure VMS to send HTTP request to camera when action needed:
- Create action rule in VMS
- Action type: HTTP request
- URL: Virtual input activation
Schedule Trigger
Description
Time-based polling without external events.
Configuration
Trigger:
Type: Schedule
Active Monitoring:
Enabled: true
IntervalMs: 60000 # Every 60 seconds
MaxDurationSec: 0 # Continuous
When to Use
- Continuous monitoring
- Occupancy tracking
- Queue monitoring
- Regular status checks
- Behavioral analysis
Considerations
- Uses Active Monitoring settings
- Higher resource usage
- Good for temporal analysis
- No external event needed
Trigger Selection Guide
Decision Tree
Comparison Table
| Factor | Motion | Object | Perimeter | DigitalInput | Manual | Schedule |
|---|---|---|---|---|---|---|
| False Positives | High | Low | Low | None | None | N/A |
| Cost Efficiency | Low | High | High | High | High | Medium |
| Setup Complexity | Low | Medium | Medium | Medium | Low | Low |
| Reliability | Good | Good | Good | Excellent | Excellent | Excellent |
| Pre-filtering | No | Yes | Yes | N/A | N/A | N/A |
Multiple Triggers
Same Camera, Different Triggers
Create multiple profiles for different scenarios:
Profile 1:
Trigger: Object (person)
Skill: Intrusion Detection
Schedule: After hours
Profile 2:
Trigger: DigitalInput (port 1)
Skill: Emergency Response
Schedule: 24/7
Profile 3:
Trigger: Schedule
Skill: Occupancy Monitor
Schedule: Business hours
Trigger Priority
When multiple profiles match:
- All matching profiles execute
- ONVIF events from all skills emitted
- TTS uses priority ordering
Related Topics
- Object Analytics - AOAS configuration
- View Areas - Multi-view configuration
- Profiles Reference - Profile configuration