Applies to: HealthPro Bridge
Issue Summary
In some instances a device is not detected in ONVIF scan mode in HealthPro Bridge, or it is necessary to confirm whether the device supports ONVIF and is compatible with HealthPro Bridge. This article explains how to verify whether a third‑party device is compatible with HealthPro Bridge using ONVIF.
Resolution
To validate ONVIF compatibility, use the ONVIF compatibility checker tool. To use the ONVIF compatibility checker tool:
-
Download the ONVIF compatibility checker tool and extract the files.
After extraction, the following files appear:onvif_test_bin.exe
onvif_test_bin.json
- Open the onvif_test_bin.json file using a text editor.
- Enter the connection details for the target device:
- IP address
- Port
- Login ID
- Password
- HTTP or HTTPS setting
-
Save the file after making changes.
Example configuration:{
"ip": "192.168.201.217",
"port": 80,
"id": "user1",
"password": "qwer123!",
"isSsl": false
}
NOTE: If the device uses HTTPS, set "isSsl" to true. - Open the Windows Command Prompt.
- Navigate to the folder containing the extracted files.
-
Run the following command:
onvif_test_bin.exe -
Confirm that network settings and firewall rules allow access to the target device.
The test results are displayed. If the test runs successfully and detailed ONVIF information is displayed
between ==test start== and ==test end== without errors, the device is considered compatible with HealthPro Bridge (ONVIF mode).
If there is a compatibility issue, an error message such as ==test error== is displayed.
Example output without errors:Example error output:
==test start== getSystemDateAndTime error: socket hang up dev time: null ==test error== error: The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array-like Object. Received null✅ Successful test → Device is ONVIF-compatible and can be used with HealthPro Bridge.
❌ Error detected → Device may not support required ONVIF features or configuration is incorrect. Please review the device settings or contact the C/S team.
Comments
0 comments
Article is closed for comments.