Methodology
How CameraCompat verifies compatibility
Exact products. Separate feature checks. Visible evidence.
1. Exact products matter
Hardware revisions, firmware and integration paths can change compatibility. We keep those scopes explicit.
2. ONVIF is not enough
ONVIF support alone never means full compatibility. Matching specifications and working video do not establish that every required function works.
3. Features are checked separately
Video can work while two-way audio does not. Supported, partially supported, unsupported, unknown and not applicable are separate states.
4. Unknown stays unknown
Missing evidence is not proof of support or incompatibility. We do not turn an unknown result into a prediction.
5. Evidence is visible
Published findings link to reviewed evidence and original sources. CameraCompat's derived assessment is clearly separated from what each source says.
6. Sources can disagree
Conflicting evidence is retained for review. An unresolved conflict cannot become a verified public verdict.
7. Results can change
Firmware, software and documentation evolve. Verification dates and immutable source captures preserve what was reviewed.
Compatibility statuses
All required core features have reviewed support, with an explicit source conclusion and no applicable limitation.
There is reviewed functional support, with a source conclusion or an evidenced restriction supporting CameraCompat's assessment.
Reviewed evidence establishes incompatibility within the stated scope.
There is not enough reliable evidence for an overall conclusion.