Categories
Cloudvue Knowledge Support Cloudvue Gateway Support Categories Products

Cloudvue Gateway – Video File Naming Format

Description 

The Cloudvue Gateway video file storage structure is as follows:

Product 

  • Cloudvue Gateway

Solution

/smartvue/video/MAC/YYYY-MM-DD/EPOCHTIME.mp4

MAC (The MAC address of a connected camera)
YYYY (Year such as 2023)
MM (Month such as 03 for March)
DD (Date such as 30 for the 30th)
Note: The folders Year, Month Date are UTC/GMT not the local time zone of the Cloudvue Gateway.

Within  each directory, video is stored in files. Each video device has its own directory and files.

Example

/smartvue/video/0050F9627E62/2023-03-30/1680140457.mp4

At first glance it would appear the video for the camera with MAC address 0050F9627E62 was recorded on March 30th, 2023. However, there is only one Unix time, and it is created using the UTC/GMT time zone. A check of the epoch time 1680140457 shows the local recording time was Wednesday, March 29, 2023, at 9:40:57 PM.

Use a converter like https://www.epochconverter.com/ to convert the epoch time to show the human readable GMT and local time.

1680140457
GMT: Thursday, March 30, 2023, 1:40:57 AM
Your time zone: Wednesday, March 29, 2023, 9:40:57 PM GMT-04:00 DST

Categories
Knowledge Support Cloudvue Support Cloudvue Access Control Categories

How to Get an ioSmart Reader Serial Number

Description 

In order to properly add an ioSmart reader in Cloudvue you will need the ioSmart Readers Conf Code and Serial Number. These two values are combined and makeup the devices Serial Number in Cloudvue. Here are the current options for obtaining that information.

Product 

  • ioSmart Smart Reader

Solution

  • Use either of the following methods
  • NOTE: If your ioSmart Reader does not have a Conf: code listed you must use Method 2

Method 1 Label on the Reader

  • The Serial and Conf codes are located on the back of the Reader
  • Remove the Readers cover and make note of the SN and Conf Codes
  • See the ioSmart Reader Panelless Enrollment video here for more information

Method 2 Cloudvue Mobile App

  • You must be within Bluetooth range of the reader and perform the following actions.
  • Install the Cloudvue Mobile App on your mobile device. Note: This is in addition to the Cloudvue Access App, see Knowledge Base Article #13379 for instructions
  • Scan for the Mobile Access Device
    • From the Cloudvue Mobile App
    • Click the plus sign in the upper right corner
    • Select Add Mobile Access Device
    • Select Scan in the upper right corner to search for the reader
    • Make Note of the ioSmart Serial number found
    • Click the back arrow to exit the scan
    • See the ioSmart Reader Panelless Enrollment video here for more information

Method 3  Original Packaging

  • Both the SN and Conf codes can be found on the outside of the  ioSmart Smart Card Readers original box
Categories
Knowledge Support Support exacqVision Server Categories Products exacqVision Hardware

Windows 7 Hard Drive Unexpectedly Shows Needs Prep

Description 

We have seen cases on NVRs running Windows 7 where a  drive has been working properly and was not just replaced that the status incorrectly shows Needs Prep

Product 

  • exacqVision Server 22.12.5.0
  • exacqVision Server 23.03.1.0
  • Microsoft Windows 7

Steps to Reproduce 

Within the exacqVision Client navigate to Configuration> YOUR Server > Storage > Hardware Tab

Expected Results 

All drives listed are high-lighted in green and have a status of Healthy

Actual Results 

One or more drives are high-lighted in orange and have a status of Needs Prep

Solution

Validate

Before going ahead with the following workaround, you must first confirm that the Needs Prep status is false

  • Using File Explorer access the contents of the effected drive(s)
  • Confirm that recent video files (those ending in .ps) are present and can be played back
  • If the drive is not accessible then it should be prepped
  • If video is present and can be played then DO NOT RUN PREP, go ahead with the workaround

Workaround

WARNING: This change is not permanent and will be overwritten during an exacqVision Server update! If necessary it can be re-applied

  • Stop the exacqVision Server Service
  • Open Notepad++ or a similar text editor as an Administrator
  • Open the file “C:\Program Files\exacqVision\Server\scripts\sysinfo.ps1”
  • Locate the line containing write-stdout ("drive-needs-prep=1") (typically line 288)
  • Comment out the line by adding a # at the beginning of the line
  • It should now be # write-stdout ("drive-needs-prep=1")
  • Save the file
  • Start the exacqVision Server Service

Branch Build 23.06.3032801 is available and confirm fixes the issue.
September 2023 release should house this fix.

AES-427

Categories
Cloudvue Cloudvue Cameras Documentation Data Sheets Categories Products

Cloudvue Illustra Flex Gen4 Mini-Domes Data Sheet

Cloudvue-Illustra-Flex-Gen4-Mini-Domes-Data-Sheet-R01.pdf
Categories
Cloudvue Cloudvue Cameras Documentation Data Sheets Categories Products

Cloudvue Illustra Essentials Gen4 Cameras Data Sheet

Cloudvue-Illustra-Essentials-Data-Sheet_R01.pdf
Categories
Knowledge Support Cloudvue Cloudvue Gateway Support Categories Products

Cloudvue Gateway and OS Logs

Description 

Directory locations of both the Linux OS and Cloudvue Gateway logs are as follows.

Product

  • Cloudvue Gateway

Solution

Linux logs

Standard Linux logs are located in /var/log

smartvue@TCG4T4:~$ cd /var/log

  • auth.log
  • boot.log
  • bootstrap.log
  • dmesg
  • dpkg.log
  • kern.log
  • mysql.log
  • nginx.log
  • syslog

Here is a full listing

Cloudvue Gateway Logs

smartvue logs are located in /smartvue/logs smartvue

@TCG4T4:~$ cd /smartvue/log/

  • analytics.log
  • diskCleanup.log
  • nginx.log
  • nvr-camera-sync.log
  • nvr-data-api.log
  • smv-record.log
  • snapshot-upload-server.log
  • update.log
  • versionCleanup.log

Here is a full listing

Categories
Knowledge Support Support exacqVision Client Products

Client Machine Suspect Tracking Button Stops Working

Description:
If navigating from one suspect tracking area to another we found that the button for that next camera is not sustaining. You have to click on the button from the associations again in order to select the next camera to navigate to.

Product:
Found on Server Version 22.12 and 23.03

Workaround:

  1. Close the Client
  2. Go into %appdata% and copy the edvrclient.xml file from the directory to the desktop for comparison later on.
  3. Delete the edvrclient.xml from the %appdata% folder.
  4. Relaunch the client and connect to the server.
    Relaunching the client will create a new edvrclient.xml that we will need to compare to the original one however you will need to connect to the server first.
  5. Navigate to %appdata% again and copy the newly created edvrcleint.xml to the desktop for support to compare.

    Note: We have only seen this issue 1 time and it might be related to installing the client on different user accounts for the OS Windows 10 and just a bad configuration.

    We did compare the edvrclient.xml’s and could not find anything that would suggest how this behavior started. If we see further issues based around the client machines having issues we should follow the steps here to gather the edvclient.xml’s and apply the work around to get the Suspect tracking working.
Categories
Sales Materials Presentations Cloudvue Documentation Categories Products

Test Presentation

Categories
Knowledge Support Cloudvue Cloudvue Gateway Support Categories Products

Cloudvue Gateway Camera Already Exists

Description 

When attempting to add a camera to the Cloudvue Gateway an error message appears “Camera Already Exists”. Typically, this happens when the local database is out of sync with the cloud database. Removing the camera from the local database then re-adding triggers a new sync which resolve the issue. Below are instructions for removing the camera from the local Cloudvue database.

Product 

  • Cloudvue Gateway

Solution

Overview

The following steps should be used to remove the duplicate camera from the Cloudvue Gateways database.

  • SSH to the Cloudvue Gateway
  • Launch MariaDB Monitor
  • Display Camera Table Contents
    • Use the MAC address to Identify the Camera
  • Delete the Camera
  • Display Camera Table Contents
    • Check the changes
  • Delete associated Camera Settings
  • Close MariaDB Monitor

SSH to the Cloudvue Gateway

  • sudo ssh -p 7627 smartvue@[IPADDRS]
    • Where [IPADDRS] is the IP address of the Cloudvue Gateway

Launch MariaDB monitor and Access The Smartvue Database

  • mysql -u root smartvuedb

Display Camera Table Contents

  • select * from camera;

Identify The Camera

  • Use the MAC to find the camera which needs to be deleted
    • Make note of the id and deleted_at fields
    • NULL in deleted_at indicates that camera is active

Delete The Camera

  • update camera set deleted_at =  created_at  where id = [id];
    • Where [id] is the cameras id

Check Your Work

  • List the cameras 
    • select * from camera;
  • Verify that the  deleted_at field is no longer NULL but is the same as the created_at field

Delete the Cameras Settings

  • delete from camera_setting where camera_id = [id];
    • Where [id] is the cameras id

Close MariaDB monitor

  • \q

Pro Tip:  To restore a camera change the deleted_at field  to NULL

update camera set deleted_at = NULL where id = [id];

  • Where [id] is the cameras id
Categories
Cloudvue Release Notes Other Categories Products

Cloudvue 22.9.1 Technical Release Notes

Description 

Cloudvue Release 22.9.1 is a defect/fix release

Product 

  • Cloudvue

Deployed

InstanceDate
North America03/08/2023
Australia03/13/2023
EMEA03/13/2023

Enhancements/Fixes

  • “Force Certify” buttoned added the Cloudvue Manager (CVM) user Interface when the device is offline. Devices with certificate problems appear as offline. This fix provides the CVM a method to assign a certificate while the device is offline. 
  • People/Vehicle detection restored to Intelligence. This fix repaired a defect that prevented People and Vehicle Detection events from appearing in Intelligence. 
  • Disabled the “Edit Partner” button for Tyco Cloud Partner role. This fix corrects the root cause of a December 2022 CVM outage 
  • Restored Cloudvue Speed Test. This fix corrected a defect that prevented the display of speed test results.