Author: Isaac Penrod

Categories
Knowledge Support Cloudvue Cloudvue Cameras Cloudvue Gateway Support Categories Products

Unable to Add Hikvision Camera to Cloudvue Gateway

Description 

While older Hikvision cameras can be added as model specific newer models do not have individual API integrations and must be added using ONVIF.   Before scanning or adding the camera in Cloudvue or Cloudvue Local the following items must be configured within the camera web interface on each camera. 

Product 

  • Cloudvue Gateway

Solution

RTSP Authentication

  • Configuration > System > Security
  • Set to digest or digest/basic.

ONVIF or Open Network Video Interface

  • Configuration > Network > Advanced Settings > Integration Protocol
  • Must be enabled.

ONVIF User

  • Configuration > Network > Advanced Settings > Integration Protocol
  • An ONVIF user with the following attributes is added.
    • Username: admin
    • Password: same as the current admin user used to access the cameras web interface
    • Level: Administrator

NOTE: Customers have reported that sometimes the settings don’t get applied in the camera.  Please double check by logging out and back into the camera and reviewing.

Categories
Knowledge Support Support exacqVision Server Categories Products

Video distortion in playback during PTZ activity and motion

Description 

Camera footage distorting when set to motion and the camera is PTZ’d. When the camera is set to free run there is no distortion.

Product 

  • exacqVision Server

Solution

Update to Server version 22.12.0
Bug Fix – psfpi – Fixed missing i-frame write when ptz activity is resumed

Categories
Knowledge Support Plugin Exclude from Global Search Log Level Warning Support exacqVision Server Categories Products Logs NotifyPI

Profile Description: %1. Notification attempt return code= 26

Profile Descriptìon: %1. Notification attempt return code= 26

Description

%1 – This is the name of the Email Message Profile %BR% %BR%

Notifications are sent using curl, so the return codes are curl status/error codes. %BR%

Curl error 26 means “Read Error”

Notes

Notifications which include attaching a clip will attempt to create, then read a file locally on the Server. If there was a failure when the clip was created, you’ll see this error. Also, you could see this error due to a permissions limitation. %BR%
Other curl errors can be found here:%BR%
https://curl.se/libcurl/c/libcurl-errors.html

Categories
Plugin Exclude from Global Search Knowledge Support Log Level Warning Support exacqVision Server Categories Products Logs NotifyPI

Profile Description: %1. Notification attempt return code= 67

Profile Descriptìon: %1. Notification attempt return code= 67

Description

%1 – This is the name of the Email Message Profile %BR% %BR%

Notifications are sent using curl, so the return codes are curl status/error codes. %BR%

Curl error 67 means “Login Denied”

Notes

Failed logins to SMTP servers can result due to username/password problems, or no authentication was supplied and the SMTP Server does not support anonymous connections. %BR%
Other curl errors can be found here:%BR%
https://curl.se/libcurl/c/libcurl-errors.html

Categories
Exclude from Global Search Knowledge Support Log Level Warning Support exacqVision Server Categories Products Logs NotifyPI

Profile Description: %1. Notification attempt return code= 7

Profile Descriptìon: %1. Notification attempt return code= 7

Description

%1 – This is the name of the Email Message Profile%BR% %BR%

Notifications are sent using curl, so the return codes are curl status/error codes. %BR%

Curl error 7 means “Couldn’t Connect”

Notes

Connection failures to SMTP servers result when the TCP connection to a given host/port fails. This could mean a firewall is blocking communication.%BR%
Other curl errors can be found here: %BR%
https://curl.se/libcurl/c/libcurl-errors.html

Categories
Exclude from Global Search Knowledge Support Log Level Warning Support exacqVision Server Categories Products Logs NotifyPI

Profile Description: %1. Notification attempt return code= 28

Profile Descriptìon: %1. Notification attempt return code= 28

Description

%1 – This is the name of the Email Message Profile %BR% %BR%

Notifications are sent using curl, so the return codes are curl status/error codes. %BR%

Curl error 28 means “Operation Timeout”

Notes

Timeouts to SMTP servers can result due to routing problems between the exacqVision Server and the SMTP Server, or a configuration problem, such as using the wrong address/port.

Categories
Video Library Demo exacqVision Server Categories Products

2022-09-01 Log File Reference Creation

>
Categories
Exclude from Global Search Uncategorized

Log Reference Template

Actual log example (Title of KB and first line should match)

Description

Describe

Notes

Notes, suggestions, KB’s, examples, etc…

REMOVE THIS SECTION

Categories Selections:
Exclude from Global Search
Categories
__Products
____%product%
Logs
__Plugin
____%plugin% (use ‘GerericCameraPI’ for things that apply to all/many camera plugins
__Log Level
%loglevel%
Tags are optional but we may use the Internal/Level2/Guest in the future to hide some from public

Categories
Plugin Exclude from Global Search Log Level Verbose exacqVision Server Products Logs GenericCameraPI

The processing loop has taken too long *** times. The longest time was ***ms for *** passes.

The processing loop has taken too long *** times. The longest time was ***ms for *** passes.

Description

A calculation is made by each camera plugin to determine if network operations ever took longer than 32ms. Once a minute, this data is logged. If it logs that it has “taken too long” this may indicate that the CPU is not able to keep up with the load.

Notes

A plugin that is not connected to any cameras will log this message once a minute and is not concerning.%BR%
Antivirus software may cause a delay in processing data.
The processing loop may take too long during heavy use, such as lots of reconnects to cameras, or many CGI commands (PTZ) and could be a sign that the system (CPU) is not powerful enough to process the current amount of camera data.

Categories
Plugin Exclude from Global Search Log Level Verbose exacqVision Server Products Logs GenericCameraPI

The processing loop performed *** passes and took ***ms to process the data.

The processing loop performed *** passes and took ***ms to process the data.

Description

A calculation is made by each camera plugin to determine if network operations ever took longer than 32ms. Once a minute, this data is logged. If it logs that it has “taken too long” this may indicate that the CPU is not able to keep up with the load.

Notes

Antivirus software may cause a delay in processing data.
The processing loop may take too long during heavy use, such as lots of reconnects to cameras, or many CGI commands (PTZ) and could be a sign that the system (CPU) is not powerful enough to process the current amount of camera data.