{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/prepare-camera-addressing-and-stream-profiles-before-command-connector-adoption/", "item": { "id": "https://update.dsesecurity.com/updates/prepare-camera-addressing-and-stream-profiles-before-command-connector-adoption/", "slug": "prepare-camera-addressing-and-stream-profiles-before-command-connector-adoption", "url": "https://update.dsesecurity.com/updates/prepare-camera-addressing-and-stream-profiles-before-command-connector-adoption/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/prepare-camera-addressing-and-stream-profiles-before-command-connector-adoption.md", "json": "https://update.dsesecurity.com/api/v1/posts/prepare-camera-addressing-and-stream-profiles-before-command-connector-adoption/" }, "title": "Prepare camera addressing and stream profiles before Command Connector adoption", "summary": "Reserve camera addresses and review connector-created accounts and selected profiles before accepting third-party adoption.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "physical-security", "label": "Physical security", "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.", "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "video-surveillance", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-15T13:31:46+00:00", "modified_at": "2026-10-15T13:36:14+00:00", "reviewed_on": "2026-10-15", "reading_minutes": 2, "word_count": 269, "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.", "primary_source": { "name": "Verkada Help — Add a non-Verkada camera to a Command Connector", "url": "https://help.verkada.com/command-connector/configuration/add-a-non-verkada-camera-to-a-command-connector", "published_on": null, "authority": "help.verkada.com" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

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

\n

Source facts

\n

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.

\n

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

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official reference

\n

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

", "content_text": "Reserve camera addresses and review connector-created accounts and selected profiles before accepting third-party adoption.\nSource facts\nVerkada 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.\nSource: Verkada Help — Add a non-Verkada camera to a Command Connector.\nApplicability\nApplies 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.\nDSE recommendation\nDSE 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.\nVerification\nAfter 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.\nOfficial reference\nVerkada Help — Add a non-Verkada camera to a Command Connector. Reviewed October 15, 2026.", "content_markdown": "Reserve camera addresses and review connector-created accounts and selected profiles before accepting third-party adoption.\n\n## Source facts\n\nVerkada 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.\n\nSource: [Verkada Help — Add a non-Verkada camera to a Command Connector](https://help.verkada.com/command-connector/configuration/add-a-non-verkada-camera-to-a-command-connector).\n\n## Applicability\n\nApplies 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.\n\n## DSE recommendation\n\nDSE 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.\n\n## Verification\n\nAfter 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.\n\n## Official reference\n\n[Verkada Help — Add a non-Verkada camera to a Command Connector](https://help.verkada.com/command-connector/configuration/add-a-non-verkada-camera-to-a-command-connector). Reviewed October 15, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/prepare-camera-addressing-and-stream-profiles-before-command-connector-adoption/", "url": "https://update.dsesecurity.com/updates/prepare-camera-addressing-and-stream-profiles-before-command-connector-adoption/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-15" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/prepare-camera-addressing-and-stream-profiles-before-command-connector-adoption/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Prepare camera addressing and stream profiles before Command Connector adoption", "item": "https://update.dsesecurity.com/updates/prepare-camera-addressing-and-stream-profiles-before-command-connector-adoption/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/prepare-camera-addressing-and-stream-profiles-before-command-connector-adoption/#article", "identifier": "https://update.dsesecurity.com/updates/prepare-camera-addressing-and-stream-profiles-before-command-connector-adoption/", "url": "https://update.dsesecurity.com/updates/prepare-camera-addressing-and-stream-profiles-before-command-connector-adoption/", "headline": "Prepare camera addressing and stream profiles before Command Connector adoption", "description": "Reserve camera addresses and review connector-created accounts and selected profiles before accepting third-party adoption.", "abstract": "Reserve camera addresses and review connector-created accounts and selected profiles before accepting third-party adoption.", "articleBody": "Reserve camera addresses and review connector-created accounts and selected profiles before accepting third-party adoption.\nSource facts\nVerkada 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.\nSource: Verkada Help — Add a non-Verkada camera to a Command Connector.\nApplicability\nApplies 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.\nDSE recommendation\nDSE 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.\nVerification\nAfter 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.\nOfficial reference\nVerkada Help — Add a non-Verkada camera to a Command Connector. Reviewed October 15, 2026.", "datePublished": "2026-10-15T13:31:46+00:00", "dateModified": "2026-10-15T13:36:14+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/prepare-camera-addressing-and-stream-profiles-before-command-connector-adoption/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/prepare-camera-addressing-and-stream-profiles-before-command-connector-adoption/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Prepare camera addressing and stream profiles before Command Connector adoption" }, "articleSection": [ "Video Surveillance" ], "keywords": [ "Video Surveillance", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "wordCount": 269, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Verkada Help — Add a non-Verkada camera to a Command Connector", "url": "https://help.verkada.com/command-connector/configuration/add-a-non-verkada-camera-to-a-command-connector" } } ] } }