Skip to main content

Device Overrides

While groups provide shared configuration, device overrides allow per-camera customization. This enables handling exceptions without fragmenting your group structure.

Understanding Overrides​

Group vs Device Configuration​

Device Overrides Architecture

When to Use Overrides​

Use CaseOverride Type
Multi-sensor camera needs different view areasView Area
Camera has unique trigger sourceTrigger
Specific camera needs higher resolutionResolution
Camera faces unique scenePrompt addition
Device I/O wiring differsPort mapping

When NOT to Use Overrides​

If many cameras need the same override:

  • Create a new profile instead
  • Consider splitting the group
  • Evaluate if group structure is correct

Override Types​

View Area Override​

For multi-sensor cameras, specify which view area to analyze:

Group Profile: Entrance Security
  Default View Area: 1

Camera Override:
  Camera: AXIS-P3807-001
  View Areas:
    - Profile "Entrance Security" → View Area 2
    - Profile "Parking Watch" → View Area 3

Use for:

  • Panoramic cameras (P3807, Q3819)
  • Multi-head cameras
  • PTZ presets

Trigger Override​

Change the trigger source for specific cameras:

Group Profile: Security Alert
  Default Trigger: Motion

Camera Override:
  Camera: AXIS-P3245-001
  Trigger:
    Type: Object
    Profile: person

Use for:

  • Cameras with AOAS capability in motion-trigger groups
  • Cameras with I/O sensors connected
  • Testing trigger configurations

Resolution Override​

Adjust capture resolution for specific cameras:

Group Profile: Standard Monitoring
  Default Resolution: BALANCED

Camera Override:
  Camera: AXIS-P3255-002
  Resolution: HD_720  # Higher detail needed

Use for:

  • Cameras monitoring fine details (plates, badges)
  • Low-bandwidth locations (reduce resolution)
  • High-value areas (increase resolution)

Profile Exclusion​

Exclude a camera from a specific profile:

Group Profile: After Hours Security
  Applies to: All cameras in group

Camera Override:
  Camera: AXIS-P3245-003
  Exclude from: "After Hours Security"
  Reason: 24/7 reception area

Use for:

  • Cameras in always-occupied areas
  • Cameras with conflicting schedules
  • Temporary exclusions during testing

Confidence Override​

Adjust confidence threshold per camera:

Group Profile: Intrusion Detection
  Default Threshold: 70%

Camera Override:
  Camera: AXIS-M3115-001
  Confidence Threshold: 85%  # Higher due to challenging scene

Use for:

  • Cameras with high false positive rates
  • Cameras in complex environments
  • Fine-tuning specific installations

Configuring Overrides​

Via Web Interface​

  1. Navigate to Devices → Select camera
  2. Click Configuration tab
  3. Find Profile Overrides section
  4. Click Add Override
  5. Select profile and parameter to override
  6. Set override value
  7. Save changes

Override Priority​

When multiple configurations apply:

1. Device Override (highest priority)
2. Profile Configuration
3. Skill Default
4. Group Default
5. System Default (lowest priority)

Viewing Active Overrides​

To see all overrides for a device:

Device View → Configuration → Active Overrides

Shows:

  • Parameter overridden
  • Original value
  • Override value
  • When set
  • Who set it

Common Patterns​

Pattern 1: Multi-Sensor Coverage​

One physical camera, multiple logical profiles:

Camera: AXIS-P3807-001 (4-sensor panoramic)

Overrides:
  - Profile: "Parking Security"
    View Area: 1 (left sensor)

  - Profile: "Entrance Security"
    View Area: 2 (center-left sensor)

  - Profile: "Entrance Security"
    View Area: 3 (center-right sensor)

  - Profile: "Loading Dock"
    View Area: 4 (right sensor)

Pattern 2: I/O Integration​

Camera with connected door sensor:

Camera: AXIS-P3245-002

Group Profile: Door Security
  Default Trigger: Motion

Override:
  Trigger:
    Type: DigitalInput
    Port: 1  # Door contact sensor

Pattern 3: PTZ Preset Analysis​

PTZ camera analyzing specific presets:

Camera: AXIS-Q6155-E

Overrides:
  - Profile: "Gate Watch"
    View Area: 1  # Preset 1: Main gate

  - Profile: "Perimeter Patrol"
    View Area: 2  # Preset 2: Fence line

  - Profile: "Parking Overview"
    View Area: 3  # Preset 3: Lot overview

Pattern 4: Scene-Specific Tuning​

Camera in challenging environment:

Camera: AXIS-M3115-003

Location: Window-facing with reflections

Overrides:
  - Confidence Threshold: 90% (vs 70% default)
  - Resolution: HIGH (for detail through glass)
  - Pre-filter: "Ignore window reflections"

Managing Overrides at Scale​

Documenting Overrides​

Track overrides with:

CameraProfileOverrideValueReason
P3807-001EntranceView Area2Multi-sensor
P3245-002DoorTriggerDI-1Door sensor
M3115-003GeneralThreshold90%Window scene

Auditing Overrides​

Regularly review:

  1. Are overrides still needed?

    • Scene changed?
    • Problem resolved?

  2. Should override become standard?

    • Many cameras with same override?
    • Create profile instead

  3. Are overrides documented?

    • Reason captured?
    • Who configured?

Bulk Override Review​

To find all overrides in a group:

  1. Go to Group → Reports
  2. Select Configuration Report
  3. Filter to Overrides Only
  4. Export for review

Override Inheritance​

Creating Derived Profiles​

Instead of many overrides, consider:

Base Profile: Security Standard
  Trigger: Motion
  Resolution: BALANCED
  Threshold: 70%

Derived Profile: Security High-Detail
  Inherits: Security Standard
  Overrides:
    Resolution: HD_720
    Threshold: 80%

Derived Profile: Security I/O Triggered
  Inherits: Security Standard
  Overrides:
    Trigger: DigitalInput

When to Derive vs Override​

ScenarioApproach
1-3 cameras need changeDevice override
4-10 cameras need changeDerived profile
10+ cameras need changeNew base profile

Troubleshooting​

Override Not Applied​

  1. Check priority

    • Is there a conflicting higher-priority setting?
    • Review active overrides list

  2. Check syntax

    • Override value valid?
    • Compatible with profile?

  3. Check propagation

    • Device online?
    • Configuration pending?

Unexpected Behavior​

  1. Check for hidden overrides

    • Review all active overrides
    • Check inherited settings

  2. Clear and reconfigure

    • Remove all overrides
    • Add back one at a time
    • Identify conflict

Override Conflicts​

When overrides conflict:

# Conflict Example
Profile Override: Resolution → HIGH
Device Override: Resolution → LOW

# Result: Device override wins
Actual Resolution: LOW

Resolution: Remove redundant override or clarify intent.

Best Practices​

Minimize Overrides​

  • Overrides add complexity
  • Document every override
  • Prefer profile changes when possible

Use Descriptive Reasons​

When setting override, document why:

Override Reason: "Camera P3245-001 has door sensor on
  I/O port 1, triggering on door open rather than motion"

Regular Cleanup​

Schedule override reviews:

  • Monthly: Quick scan for obsolete overrides
  • Quarterly: Full audit with documentation
  • After changes: Check for newly-unnecessary overrides

Testing Overrides​

Before applying:

  1. Test on single camera
  2. Verify expected behavior
  3. Roll out to similar cameras
  4. Document results