Which Camera Brands Work with CHeKT Edge Analytics
Overview
A common question from dealers and installers is which AI camera brands and models are compatible with CHeKT Edge Analytics.
Rather than maintaining a fixed compatibility list, CHeKT supports edge analytics through the ONVIF Analytics Metadata PullPoint Subscription standard. Compatibility is determined by whether the camera correctly implements this industry-standard ONVIF protocol—not by a proprietary integration or manufacturer partnership.
This article explains how CHeKT receives camera analytics, which brands are known to work, known limitations, and how edge detections become monitored alarm events.
How CHeKT Reads Camera Analytics
The CHeKT Video Control Panel (VCP), formerly known as the Bridge, uses the ONVIF Analytics Metadata PullPoint Subscription API to receive edge analytics directly from supported IP cameras.
Because this is an open ONVIF standard, any camera that correctly implements analytics metadata through PullPoint Subscription can be used with CHeKT. No proprietary integration or custom driver is required.
Once connected, the VCP continuously monitors the camera's analytics metadata and reacts to qualifying detection events.
Camera Brands Known to Work
The following camera manufacturers are known to support the required ONVIF analytics metadata standard and have been successfully used with CHeKT:
- CHeKT Smart Security Cameras
- Dahua
- Hikvision
- Hanwha Vision
- Axis Communications
- Bosch
- Milesight
- Uniview
- Avigilon
- And many other manufacturers that support the ONVIF Analytics Metadata PullPoint Subscription standard
Note: This is not a complete compatibility list. Because CHeKT relies on an industry standard rather than model-specific integrations, many additional camera brands and models are compatible. If a camera properly implements ONVIF Analytics Metadata via PullPoint Subscription, the CHeKT VCP can receive and process its edge analytics.
Known Limitations
While many manufacturers support the ONVIF standard correctly, the following brands have shown inconsistent behavior with analytics metadata:
- TVT
- Digital Watchdog
Camera Stream Requirements
For proper operation, the CHeKT Video Control Panel must be able to access the camera's secondary (sub) stream.
The secondary stream is required because it allows the VCP to:
- Preserve the camera's primary stream at full HD resolution and frame rate for local recording.
- Optimize bandwidth usage between the VCP and the CHeKT Cloud.
- Automatically scale video resolution and frame rate for efficient video uploads.
- Ensure monitoring operators receive video quickly while maintaining high-quality local recordings.
Important: If the camera's secondary stream is disabled or unavailable, the VCP will not be able to connect to the camera or recorder.
How Camera Detections Become Alarm Events
Once a compatible camera has been added to the CHeKT Video Control Panel, alarm processing follows the same workflow as a traditional alarm sensor.
1. Add the Camera to the VCP
Connect the camera to the CHeKT Video Control Panel using the standard onboarding process. Here is an article that can walk you through Adding a Camera to CHeKT VCP.
2. Configure Detection Rules on the Camera
Create analytics such as:
- Person Detection
- Vehicle Detection
- Line Crossing
- Intrusion Detection
- Other supported AI analytics
Important: The CHeKT Video Control Panel (VCP) does not support motion-based analytics because they rely solely on pixel changes to detect activity. Environmental factors such as lighting changes, shadows, rain, insects, or moving vegetation can trigger false detections, resulting in excessive false alarms and reduced detection accuracy.3. The VCP Monitors Camera Analytics
The Video Control Panel continuously listens for ONVIF analytics metadata generated by the camera.
From the VCP's perspective, the camera functions just like an alarm sensor or zone.
4. Armed Detections Generate Alarm Events
When:
- the VCP is armed, and
- the camera reports a qualifying detection,
the VCP:
- captures the associated video clip,
- generates the alarm event, and
- prepares the event for transmission.
5. Alarm Signals Are Sent to the Monitoring Center
The VCP transmits the alarm using Contact ID signaling to the central monitoring station. This article gives an overview of CHeKT's Contact ID Library.
Operators receive:
- the alarm event,
- the associated video clip, and
- the information needed to verify the event.
Why This Matters
Unlike traditional video management systems that simply display camera feeds, CHeKT transforms AI-enabled cameras into monitored alarm sensors.
Each camera behaves like a protected zone within an alarm system. When analytics detect a qualifying event while the site is armed, the VCP processes the detection using the same alarm workflow as conventional intrusion devices, allowing monitoring personnel to receive verified video alarms in real time.
Frequently Asked Questions
Is there a downloadable compatibility list of AI camera brands and models?
- No
Any camera that correctly implements this standard should be compatible.
Do I configure detection rules in CHeKT?
Detection rules—including person detection, vehicle detection, line crossing, intrusion zones, and similar analytics—are configured using the camera manufacturer's software or web interface.
CHeKT simply receives the analytics events generated by the camera.
What if my camera brand isn't listed?
Many compatible brands are not listed in this article.
Check the camera manufacturer's documentation to confirm support for:
- ONVIF Analytics Metadata
- PullPoint Subscription
If you're unsure, perform a bench test or contact CHeKT Support for assistance validating the camera.
Why does the VCP use the secondary stream?
Using the secondary stream allows the camera to continue recording locally at full quality while enabling the VCP to efficiently upload optimized video clips to the CHeKT Portal and monitoring center.
If the secondary stream is unavailable or disabled, the VCP cannot establish a video connection.
Need Help?
If you have questions about camera compatibility or need assistance validating a deployment, CHeKT Support is here to help.
Email: support@chekt.com
Phone: +1 (224) 442-4358
Support Portal: Submit a support ticket through the CHeKT Dealer Portal
Knowledge Base: Visit the CHeKT Online Knowledge Base for additional technical documentation and deployment guides.
Related Articles
CHeKT AI Cameras Analytics Manual
The latest licenced plug-in is a set of analytical tools loaded on our cameras that provides the means to perform advanced analytics, reduce false alerts and customize when events occur. This article will describe how to enable and configure the ...CHeKT E-Series AI Camera Models
The E-Series AI camera boasts a robust construction, ensuring its ability to withstand various environmental conditions. When using the CHeKT Video Bridge, this camera takes advantage of modern IP technology to communicate alarm signals from the ...Analytic Triggers: Using Camera Analytics
Analytic Events Supported analytic event triggers from a camera mounted to the bridge can generate alarm signals and video events. These events are based on a supported API connection with the camera. The network event message has topic information ...Cawamo-CHeKT Integration Guide
The Cawamo AI Server integrated with the CHeKT platform creates video AI event notifcaitons for alarm monitoring centers and customers using the CHeKT Mobile app. This integation allows sites to leverage Cawamo's advances AI as detection zones for ...Supporting Cameras with Analytics
When using cameras with supported edge-based analytics, a wired Digital Input trigger is not needed. The Bridge still requires power, internet service, and in most cases, an arming input from the alarm panel. Using the alarm panel arming state allows ...