GuideInformationVideo Surveillance

Prepare camera addressing and stream profiles before Command Connector adoption

Reserve camera addresses and review connector-created accounts and selected profiles before accepting third-party adoption.

Integrated video surveillance and controlled entry at a modern commercial facility.
DSE visual intelligencePhysical securityGuide · 2 min read
Executive summary

What you need to know

Reserve camera addresses and review connector-created accounts and selected profiles before accepting third-party adoption.

Potentially affected

Applies specifically to the Command Connector adoption workflow and its documented camera compatibility requirements. It does not establish that every ONVIF model is supported or that existing VMS profiles are untouched.

DSE recommendation

DSE recommends reviewing camera configuration ownership before onboarding.

Reserve camera addresses and review connector-created accounts and selected profiles before accepting third-party adoption.

Source facts

Verkada Command Connector communicates with third-party cameras by IP address, so an address change can interrupt streaming. Its guide requires a static address or DHCP reservation and excludes dynamic NAT or Layer 3 translation between connector and camera. Only I- and P-frames are supported, not B-frames. ONVIF adoption creates a camera administrator account. Optimal streaming-profile selection creates high- and standard-quality profiles for each channel; Manufacturer mode instead uses profiles already on the camera.

Source: Verkada Help — Add a non-Verkada camera to a Command Connector.

Applicability

Applies specifically to the Command Connector adoption workflow and its documented camera compatibility requirements. It does not establish that every ONVIF model is supported or that existing VMS profiles are untouched.

DSE recommendation

DSE recommends reviewing camera configuration ownership before onboarding. Reserve addresses, identify existing integrations, and agree who may manage the account and stream profiles. Save the approved pre-change settings and confirm the camera’s encoding and selected profile mode before beginning. Pilot a representative multi-sensor device if the deployment includes them. Treat an IP change as a coordinated connector change and keep the camera inventory synchronized with the connector’s channel records.

Verification

After adoption, inspect the account and created or reused media profiles through the camera’s approved administration interface. Play each expected sensor channel in Command and confirm any pre-existing VMS still works. Record the actual address and frame configuration; discovering a device on the network is not complete integration verification.

Official reference

Verkada Help — Add a non-Verkada camera to a Command Connector. Reviewed October 15, 2026.

Primary reference

Review the official source

Verkada Help — Add a non-Verkada camera to a Command Connector · Verified October 15, 2026

Open official reference ↗
Plan the next step

Need help applying this guidance safely?

DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.

Talk with DSE