Deactivate Axis radar pairing before clearing its configuration

Bottom line: Plan retirement of a paired radar as an explicit state change, rather than assuming a configuration-clear request will remove an active pairing.

Source fact: documented behavior

The Network Radar Pairing documentation says clearConfiguration fails while the network radar pairing function is active.

It describes setActive as activation of an already configured pairing and says the operation fails if no configuration can be located.

The topic explicitly says the API is not supported by all devices.

What the source does not establish

Use this article only as a review of the documented pairing-state contract. Require the exact camera and radar support information before changing an installation. Do not treat removal of an integration as proof that perimeter coverage remains acceptable. Keep the decision to retire a detection path with the system owner, rather than making it an incidental configuration cleanup.

Applicability questions

• Which camera and radar pairing is being retained, replaced or retired?
• What supported evidence shows the current configuration and active state?
• Who owns the detection or response path that depends on that pairing?
• What verified final state should exist after the approved change?

DSE recommendation: controlled next steps

The following steps are DSE recommendations based on the cited source.

DSE recommends writing the intended pairing-state transition before touching a production radar integration.

1. For a proposed retirement, identify the exact pair and the dependent rules or operator workflow. Ask the system owner to decide whether alternative coverage or a maintenance arrangement is needed. Define what must remain available during the work. Keep the credential and support review restricted to authorized personnel; do not copy passwords into the change worksheet.
2. Rehearse the documented sequence on a supported noncritical pair or other manufacturer-approved test arrangement. Read the current configuration and active state through the supported methods. Follow the approved deactivation step before attempting to clear the configuration. Preserve each returned result, and stop if an operation reports failure rather than treating the request’s transmission as completion.
3. After the approved transition, inspect the supported state again and compare it with the intended result. Separately verify the affected operational workflow with the system owner. If the pair is being replaced, commission that replacement under its own support requirements. Do not infer a working replacement solely because an old pairing no longer appears in a configuration view.

Verification and evidence

Retain the camera and radar identity, software versions, support references, before-and-after state observations and sanitized operation results. Record the decision about dependent detection or response functions and who confirmed the final operational state. Preserve the rollback or restoration procedure appropriate to the approved change.

Include a paper review of the documented active-clear failure in the proposed rehearsal so the team knows how to respond to it. Do not disable necessary protection merely to demonstrate an error. The expected outcomes in this article are proposed acceptance criteria; no pairing was deactivated, cleared or tested during its preparation.

Official references

• Network Radar Pairing — Axis Communications; official VAPIX documentation.

Source review completed October 28, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.