Unlink SAFIRE from the local P2P cloud

From the attached software interface, select the device and click on the “Unbind” tab at the top of the mask:

Add the device’s credentials and then copy the “CAPTCHA” code and confirm.

Download SADP

Another way to unbind a SAFIRE recorder from the P2P directly from the recorder:

For this it is necessary that the device has a recent version, therefore we must follow the FAQs on how to update the firmware of a Safire recorder.

After the update, we will access the NETWORK / PLATFORM ACCESS options and then check the availability of the UNBIND button and perform the procedure.

How to reset the password of SAFIRE devices

There are two procedures to recover the password of Safire recorders, and each procedure depends on the system of the HTVR, DVR, NVR or camera you want to recover. In both cases the SADP software is used.

1- Install the SADP from the manufacturer’s website:

https://athena-visiotech.s3-eu-west-1.amazonaws.com/d1XvP3EBNOqssiu8J01D/Safire_SADPTool_v3.0.2.50build20200402.zip

2- Run the device finder, which will find the devices by MAC address.

3- Select the device to be recovered and click on the Forgot Password button (bottom right button)

​

If the software indicates to export a file, follow the procedure from step 4 to 7, while if the software indicates to enter a Security Code follow the procedure from step 8 to 12.

Procedure 1:

4- We are asked to export a file (Export File). Click on the Export button, and select the path where the file is to be saved; confirm.

​

5- El fichero se descargará al Pc. A continuación envíe un correo al nuestro servicio técnico para que se lo mandemos al fabricante y genere el fichero de recuperación de contraseña: no apague el grabador en ningún momento desde el momento de generar el fichero hasta que se lo devolvamos.

​

6- After importing in the same tab the recovery file, enter the new password for the recorder and repeat it. The password must be identical in both boxes (New Password and Confirm Password), otherwise, it will not allow you to continue.

7- Confirm the import and wait for the file to load. If you have done the procedure correctly, a window will appear with the following text: Your recorder’s password has now been reset.

Procedure 2:

8- You are asked to enter a Security Code9-

Press the Cancel button, and go back to the SADP, you have to take the Serial number and the Start time, and send them to our technical service

.

This can be achieved in two ways:

a. Go, within the SADP list, to the device from which you want to retrieve the password and look at the data in columns 4 and 5.

b. Click directly on the Export button, to generate the Excel file to be sent to us (to avoid errors when entering the data)

10- Safire will send us some security codes, go to step 3, then step 8 and enter the code according to the date you are in.

We remind you that the correct code for the date (Today) will return the equipment to the factory password, which is “12345”

EXAMPLE

If you request the codes, for example for the 7th of October and you are only going to have access to the equipment on the 9th, you have to use the code corresponding to the 9th of October. It is important that the recorder is not restarted until the password is reset.

The password will be the factory default (User: admin / Password: 12345).

IMPORTANT: When sending the file or the required data, the device cannot be turned off under any circumstances, otherwise the procedure would have to be redone

Change Video, Audio and Compression Format Settings via Web Browser (Cameras)

To change the video and audio settings from a browser, we have to enter the IP of the camera in the address bar:

After accessing the camera with your credentials, we must access “CONFIGURATION” and then the left menu, VIDEO AND AUDIO.

Remember that in some models of IP cameras the image is not encoded in H265 or H265+, therefore the option to modify the compression format may not offer the options mentioned above.

In this other field is where you can modify the values of Bitrates, frames and bit rate type to save the bandwidth used by the camera.

In the image below we can see that the bitrate has decreased a lot by just changing the Video Enconding to H.265 and then enabling H.265+.

We could save even more bandwidth by changing other parameters (such as image resolution), but that depends on each installation, it is not always mandatory.

Create double verification of access to recordings to a non-administrator user

This function is only supported on 8 Series NVRs.

It is sometimes required to restrict access to certain privileges to an operator user, where a coordinator without administrator permits can temporarily allow access to those blocked privileges.

Example:

Configuration:

How to configure the NTP server in SAFIRE

Note:

This test was performed with an SF-XVR6108AS-1FACE recorder firmware version V4.24.001 build 201015

1. Open the Settings page through the web browser or in the SCC (Sgo to Control Center)

2. System settings

3. Time settings

4. Select time zone

5. Enter the address of the time server (NTP)

You have to specify the time zone and domain name, as follows:

European NTP servers:

uk.pool.ntp.org (UK)

de.pool.ntp.org (Germany – Deutschland)

fr.pool.ntp.org (France – Française)

es.pool.ntp.org (Spain – España)

it.pool.ntp.org (Italy – Repubblica Italiana)

nl.pool.ntp.org (Netherlands – Nederland)

no.pool.ntp.org (Norway – Norge)

pt.pool.ntp.org (Portugal – Portuguesa )

se.pool.ntp.org (Sweden – Sverige)

6. Save

Example: XVR

Example: NVR

Example: IP camera

ADAM module configuration with Safire NVR

The ADAM relay module is compatible with the SF-NVR8xxx-4K, excluding the -FACE and -AI

It is very important to check the NVR firmware, it must be version 4.50 or higher

IP CONFIGURATION ADAM MODULE

It is only necessary to set the IP for the ADAM module, for this purpose use the ADAM Net Utility software

• https://athena-visiotech.s3-eu-west-1.amazonaws.com/V675-H4B6mOlDBqJTbtN/AdamApax%20.NET%20Utility%20V2.06.00%20B10.msi

The device is detected, the factory IP is set to 10.0.0.1 and the password “00000000”, it is added to the software and when selecting it, it will ask for the password:

In the Network section the appropriate IP is set and the changes are applied, with this the module would be ready to be added to the Safire NVR

ADDING THE MODULE TO THE SAFIRE NVR

Remember that it must have a version 4.50 or higher

In the Alarm Extension section the IP of the module will be added, the maximum number of inputs and outputs in the NVR can be 6 (even if the module has more). A maximum of 5 ADAMs can be added

Once added, the inputs and outputs of the module are already available in the recorder and can be used as any relay of the NVR itself:

How to make Edge run in Internet Explorer mode

Note:

This article is created on Windows 10 Enterprise Version 21H1 with a 2.20GHz Intel(R) Core(TM) i7-8750H CPU.

1. Open the “Edge” browser

2. Go to the top right and click on the options icon

3. Scroll down to Settings section

4. Within the settings go to “Default Browser”

5. On the right hand side, select “Allow”

6. Click on “Reset”

7. When “edge” has restarted, open the URL to be run in “Internet Explorer” mode.

8. Click with the mouse on the tab and “Reload tab in Internet Explorer mode”

Note: Not all options may be available with some devices

Endpoint request timed out

The RTSP protocol itself does not have encryption, for that there is SRTP or proprietary implementations, but it is not common in the streams of the main CCTV providers.

RTSP requires authentication with username and password, but it is not transmitted directly encrypted, if encrypted transport is required it would require the use of a tunnel with SSL encryption for the communication channel.

When accessed via Hikvision or Safire P2P service, a verification code is used to encrypt the video stream transmission communication channel, but it does not affect whether the RTSP port is accessed directly (directly on LAN or remotely via NAT).

SAFIRE: Continuous recording combined with event recording

For this FAQ we use the:

Recorder: SF-NVR6104-4K4P-VS2Firmware

: V4.30.005 build 201028Safire

Control Center V3.2.0.57 build 20210726

step 1 – Check that the recording schedule is in Continuous mode.

2nd Step – Configure a VCA or Motion Detection rule.

Check also if the “Notify remote center” option is checked and if the Trigger Recording corresponds to its respective channel, in our case D1.

Once we have these settings we can wait a few minutes and check the events.

With the “SAFIRE CONTROL CENTER” running, go to DEVICE MANAGEMENT and add the recorder to the Software.

3rd Step – Check events generated, choose “EVENT CENTER”

Once in the Event center, select REAL TIME EVENT and then we can check the events in real time.

Once confirmed that there are events we can do a search of the recordings.

4th Step – Check recordings, choose the “REMOTE PLAYBACK” option.

We choose the date according to the search need, the NVR channel and below all the type of Event, in our case we should choose “LINE CROSSING DETECTION”.

We will have a result in which we can choose the files on the right side and below in the line of events, we can choose directly the point to reproduce.

How to install Safire Connect on an Apple Mac laptop or PC with an ARM M1 processor

How to install Safire Connect on an Apple Mac laptop or PC with an ARM M1 processor.

1. Open App Store

2. Search for Safire Connect in iPhone and iPad apps

3. Click GET

4. Open the Safire Connect app

5. Login with your credentials.

6. You can now use the app similarly to your mobile device.

Safire – Access IP camera web interface from NVR with built-in PoE switch

If you need to access an IP camera that is connected directly to a NVR PoE switch, you don’t need to connect the network cable from the PC to the NVR PoE switch, just enable the NVR Virtual Host.

1 – Access the advanced network settings / Other and then enable the option indicated, remember that each time you restart the recorder the option will be unchecked, you will have to enable it again.

2 – Access the Camera Management option and click on the link that the recorder enables to access the camera.

This way, the maintenance procedure to the camera will be easier than connecting and disconnecting cables.

First configuration of the Safire Control Center

When you want to connect to your Safire cameras using a PC or laptop with Windows installed:

1. You need to have a Safire IP camera or a Safire recorder

2. The recorder or cameras need to be connected to the same computer network as your PC

3. When 1 and 2 are correct continue.

4. Download and install Safire Control Center

• To download the Safire Control Center, use the link – (latest version as of 7/19/2021)
• Safire Control Center V3.2.0.57 build 20210702

5. Unzip the downloaded file

6. When the download is finished double click on the file“Safire_Control_Center_v3.2.0.57_build_20210702.exe”

7. Follow the installation steps from the installation window

8. Then click Finish

​

9. When you select “launch client” the Safire Control Center is launched

10. Click on Device Management

​

11. At the top left, click Online Device to search for all Safire devices on your network.

12. Select the devices you want to add

13. And click Add

14. A new window will appear

15. Use the credentials that were created for your devices

16. Click “Add” and the devices will appear at the top

​

17. Click the start button in the top left corner

​

18. Press the home button in the top left corner to return to the home screen

Creating auxiliary screens in SAFIRE CONTROL CENTER

If necessary, the SAFIRE CONTROL CENTER can create up to 3 additional screens to the main software, that is, a total of 4, always depending on the decoding capacity of our PC.

The maximum preview of the auxiliary screen is 3, so a total of 4 windows can be seen with a maximum of 64 cameras per window.

Select the MENU option in Safire Control Center and then select the last option “Auxiliary Screen Preview”.

The result is an auxiliary window where we have the option to drag it to another screen and have it displayed on both screens 

This FAQ has been made with software version V3.2.0.57 build20210526

What is the public IP address of Procloud services?

The SafireService platform architecture is designed to expose only the services that need to be consumed by client applications, i.e. the frontends that render to web browsers and the backends that process requests from these frontends. More complex services such as those that perform device checks do not expose any IP publicly.

GPU Image Decoding in SAFIRE CONTROL CENTER

To have a smoother video display in SAFIRE CONTROL CENTER, it is recommended to enable the option for preferred GPU decoding, if the PC has a dedicated graphics processor.

Open “SAFIRE CONTROL CENTER” and select “SYSTEM CONFIGURATION”

Access “IMAGE” and enable the option marked “Hardware Decoding Preferred”.

Close the software and open it again for the changes to take effect.

How it works when the recorder has two RJ45s in SAFIRE

Safire’s dual RJ45 NVRs can work both ways, one port backing up the other (fault tolerant mode) or independent networks (multi-direction mode), each with its corresponding IP range (similar to an NVR with integrated PoE ports, whose network segments are independent)

HTTPS access on a device from Safire

HTTPS access on Safire computers is disabled by default, to enable it you have to create a certificate, the easiest way is to create it with your own signature:

The data to indicate can be whatever you want, but the Hostname/IP section must be the address of the equipment, so if you indicate the local IP of the same I can only access by HTTPS using that address, not being able to do so remotely; another section to consider is the validity which will expire HTTPS access after these days:

Once this data has been saved, HTTPS can be activated:

To access the equipment will be done indicating https://IP:PORT, the port if it has not been modified and remains the 443 is not necessary to specify it, if it had been changed then it is essential to put it.

When accessing the browser will give us a warning that the connection is not private, this is because the certificate signature is self-signed, just go to the next section to have access:

TrueSense System Configuration to Detect People and Vehicles

EasyConnect (P2P) configuration on a SAFIRE recorder

To access a Safire recorder remotely without the need to open ports, EasyConnect (P2P) must be enabled by following the procedure below:

Accessing the recorder via web interface

1 – Click on Configuration
2 – Advanced settings
3 – Enable by checking the option “Enable” and then a pop-up will appear, click on OK.

4 – Define a password for the Video stream encryption:

We recommend a complex password and preferably different from the “admin” password, it is very important to know that this password is not linked to the recorder administrator’s password.

5 – Very important to check if the STATUS is really ONLINE.

6 – If the device does not connect to the P2P server, check the DNS.

Exporting and importing backups from Safire Control Center software

The steps to export and import the Safire Control Center software backup would be as follows:

• Export the software configuration file:

This file is a compressed file that does not need to be unzipped. It contains all the software information

• Import the file into the new software:

IMPORTANT: for the backup uploading to work it is essential to close the software, but also the Safire Control Center SERVER service which does not close automatically when closing the software:

When restarting the software we must have all the terminals and configurations of both cameras, video door phones and access controls of the previous software

Limitations of FACE recorders

Face Recognition = Face Capture + Face Comparison

If the face capture is performed by AI2 cameras, we will have face recognition in X channels, where X is the number of -XFACE containing your reference. To make a face comparison, a face capture is required, so it is important to know the number of channels that the recorder has available to make face capture.

Ex

:SF-NVR8216-4K-8FACE8ch

with Face Recognition using AI2 Cameras

Configuration recommendations for proper functioning of push notifications in Safire Connect Android

Under Settings – Applications – Safire Connect we must ensure that we have granted all camera, speaker, microphone, etc. permissions and that we have not been denied any.

In addition to this: also make sure that we allow you to use mobile data, as well as wifi

and that in the notification section we have everything marked.

Also in the battery section of your mobile device, make sure that Safire Connect is allowed to work in the background.

All this is usually already activated on many phones, but there are others, especially Xiaomi, where some of the above features may be missing.

Adding Safire cameras or recorders to a SAFIRE NVR remotely

The only point of attention we have to take into account is to open the ports in the router corresponding to the installation of the cameras. And then add that public IP address in the NVR with the proprietary protocol port (which in Safire is 8000).

If it is a recorder that you want to add, by adding the public IP address (with port 8000) of the secondary recorder, a message will appear that allows you to choose specifically which channels of the secondary recorder you want to acquire in the primary recorder.

This option is the most recommended, instead of choosing a NAS, PC-Recorder, ftp, etc… since an NVR is a more reliable computer from this point of view, sinc it is:

– dedicated to this function;

– a kind of device that consumes less energy;

– a device which is managed from the same applications as the rest of the cameras or recorders in the installation, being easier to visualize and from which it’s easy to extract the information in an intuitive way, as well as its configuration (by an ecosystem similarity principle);

– a device which does not involve the payment of licenses;

– a device that can be monitored through the ProCloud service of http://safire.services.

How to set up NAS as a backup disk on a SAFIRE computer

The NAS has to support NFS protocol.

1. Adding the NAS to the team

1.1 Go to the configuration section of the hard disks and click on the button at the bottom left

“Add”.

1.2 In this window, we are going to compile the fields “Network disk IP” and “Network disk direct” with the NAS information.

2. Changing the storage mode of hard disks

2.1 Go to the advanced settings and choose “HDD Group” as the storage mode.

2.2 Click on “Next” and the computer will ask you to restart. We say yes.

3. Formatting the NAS hard drive

When the recorder restarts, it will ask us to format the NAS hard drive. We will accept and go to the configuration section of the disks. From that section we will be able to monitor the progress of the formatting process.

4. Configure the NAS hard drive as a backup

4.1 When the formatting is finished, click twice on the line of the NAS hard disk or on the icon for editing.

4.2 In the window that appears, choose the “Redundancy” option as the status and save the changes by clicking on OK.

5. Finished configuration

If everything has been configured correctly, we will find ourselves with a configuration of this type:

Extra. Viewing the NAS recordings

In case we need the recordings from the NAS, we can access the network drive through Windows Explorer and open the files through the VSPlayer software.

How to configure the SNMP monitoring service on SAFIRE (or Hikvision) equipment

The steps to follow are hereby presented:

– install the specific MIB search engine

– log into the recorder via another search engine (e.g. Internet Explorer)

– navigate the machine menu as follows: Configuration–>Network–>Advanced Settings–>SNMP, and once entered the section of interest click on Enable SNMP v2c

– insert in the Trap Address tab the IP address of the computer on which the MIB has just been installed and click on Save

– click on File and then on Load in the MIB search engine

– open the SNMP file you want to use

– insert, in the upper left bar, the IP address of the recorder and click on Advanced Parameters

– fill in the fields of the window that opens with the same data as previously set in the configuration menu of the recorder (except for the IP address, clearly) and click on Ok

– click on File again, then on Save Session and choose a path to save the configuration

– click on the created path, then click on Walk; further on Tools and Trap Receiver to also configure that port (in particular in Tools–>Option), which in the example above we had configured in the recorder as the 162

In this way we can already visualize, in the bar called Operations, all the start/restart/stop events of the recorder.

Video Tampering in SAFIRE

Video Tampering is normally used to detect when the camera is covered, preventing us from seeing the scene properly.

The function can be configured within the basic event section, associated to motion detection:

Different reactions of the device can be configured when detecting video tampering; sending an email, triggering a relay output of the recorder or of the same camera, triggering a recording of any channels, moving to a PTZ preset or sending a push notification to the app.

It is also possible to set the video tampering as active by schedule.

Configuring a RAID1 in a SAFIRE videorecorder

1. We enter the HDD section, then we navigate the Advanced section and change the mode from quota to group and select the cameras that we want to record in the secondary hard disk’s space.
2. Once the previous step has been completed, we enter in general and click on the edit button on the hard disk; a screen will appear where we’ll have to check the redundancy box and choose the group that we had previously configured with the desired channels.

PC requirements by number of channels, coding power and video quality for SAFIRE Control Center

Specifications, including sample performance, are available in every Download section of Safire products.

https://athena-visiotech.s3-eu-west-1.amazonaws.com/g1WHVnEBNOqssiu8YU0y/SCC_Datasheet_EN.pdf

Error 153 in Safire Connect

The error is due to a problem in the app that causes it to misinterpret video stream requests to the recorder and to consider them as consecutive access attempts to the computer, which causes the device to lock itself up (in fact, error 153 is usually generated by illegal accesses).

The way to prevent this error from occurring is to uncheck the “Illegal login lock” option. Unchecking it does not take into account illegal access attempts, and therefore the above error does not occur.

​

In some recorders it can only be done from the Safire Control Center (thus from PC), while it cannot be done from the local menu of the recorder itself.

​

In cameras, the menu is presented as in the image below:

EasyConnect – P2P device sharing

To share a Safire device with other users, be it an IP camera or a recorder, the procedure is the same.

Let’s demonstrate how to share from a Browser.

Step 1 – Access the website that gives access to the Safire Cloud, http://easyconnect.safirecctv.com/

We’ll be accessing our Cloud account soon.

Once inside our account, we choose the product to share and click on the SHARE option.

A new window will open, and then we will have to enter the email address of the person with whom we want to share the product. In addition, it is very important to define what kind of permissions the person will have.

In this example, our product is a SAFIRE Video Door Phone, therefore if we do not apply all the permissions, the user who benefits from the compartment may not be able to speak or receive the alarms.

So it is very important to apply the permissions correctly.

Safire: Activate an alarm using the IP address from an IP camera.

For this guide we have used a Safire SF-HTVR8108A-HEVC recorder and an IP camera with alarm input.

To activate an alarm input of a recorder remotely from a wireless IP camera is very simple, to do this first access the recorder and go to the menu Camera Management.

1 – CONFIGURATION

2 – SYSTEMS

3 – CAMERA MANAGEMENT

4 – IP CAMERA

5 – ADD

Once the IP camera is added, we proceed to the configuration in the recorder. To be sure that the connection is stable and that everything works, we check that the STATUS of the camera is ONLINE.

In the recorder we will access the following menu:

1 – CONFIGURATION

2 – EVENT

3 – BASIC EVENT

4 – ALARM INPUT

The next step is to set the alarm input:

1 – Alarm input number

2 – Alarm type: We can choose between NO and NC

At this point we already have the Alarm input of our IP camera linked directly to an alarm input of the Recorder.

In LINK METHOD we can choose what to do when the alarm input is activated, such as activating an alarm output of the recorder, moving a PTZ or generating an audible warning on the recorder.

In this way, we have connected the alarm input of an IP camera to an alarm input of the recorder and saved ourselves the wiring.

Checking and updating Firmwares in SAFIRE IP Cameras or video recorders

In this procedure we will use the Internet Explorer browser, we are going to access via IP address to the camera:

After introducing the IP camera address and logging in, let’s click on CONFIGURATION.

In the CONFIGURATION menu, we have to access SYSTEM SETTINGS, and check the device model and firmware version in the BASIC INFORMATION menu.

Then look for the camera model on te VISIOTECH’s website.

Download the file and then extract the update file from the compressed folder you just downloaded. The update file is called digicap.dav. After the file is unzipped, enter the path of the unzipped file folder in the camera’s Upgrade&Maintenance menu.

Click on MAINTENANCE and then on Browse to find the location of the file; once selected, click on Upgrade. A message will appear indicating that the camera will automatically restart after the update. Click OK.

When rebooted, return to the SYSTEM CONFIGURATION menu, and check the version to make sure that the camera has been updated.

Camera Recording Mode not Configured

Back to Top

In UniFi Video, cameras must first be configured to either Always Record or Record Only Motion mode before recordings will be generated. You can view the recording mode in the Camera page of UniFi Video.

To change the recording mode:

1. Log in to the UniFi Video Controller and go to the Cameras section.
2. Open a camera’s Properties pane by clicking on the camera.
3. Click on the Recording tab.
4. Under the Configuration section, in the Record Mode dropdown, choose either Always Record or Record Only Motion, then click Save.

If Schedules are in use, verify the Schedule configuration is appropriate. You may also need to verify that the time zone is set correctly under Settings > Time & Date, and that the NVR has sufficient internet access to be able to update its time via NTP.

Inadequate Motion Sensitivity Settings

Back to Top

If Record Only Motion is selected, make sure that the Motion Sensitivity settings are configured in a manner adequate for the scene that is being monitored. To configure Motion Sensitivity:

1. Log in to the UniFi Video Controller and go to the Cameras section.
2. Open a camera’s Properties pane by clicking on the camera.
3. Click on the Recording tab.
4. Under the Motion Detection section (click to expand), click the Configure button in the Zones section.
5. In the Window that appears, verify that the motion detection zone covers the area you wish to monitor, and increase Sensitivity as needed until motion events are triggered reliably.

Remember to use the Test Zone functionality to test your settings, then click the Save button to store the changes.

Incorrect Recording Path

Back to Top

If the recording path is not set to a valid directory, UniFi Video will fail to store recordings. While the interface will validate that the path is correct during configuration, it is possible that the path may be incorrect after a configuration is restored from backup, or the filesystem has been changed at the OS level.

Verify that the recording path is correct under Settings > System Configuration > Recording Path.

For reference, the default recording paths are:

• Windows Custom Installs: C:\ProgramData\unifi-video\data\videos
• Linux Custom Installs: /usr/lib/unifi-video/data/videos
• UVC-NVR / UVC-NVR-2TB: /srv/unifi-video/videos

Recording Path has Incorrect Permissions (Linux-Based NVRs)

On Linux-based NVRs, the unifi-video user and group must be correctly assigned to the target recording directory so that UniFi Video can store recordings. The user and group can be unexpectedly changed while mounting an external device, browsing the structure using software, or making configuration changes.

To correct the permissions, SSH into the NVR and issue the following commands to re-assign all permissions correctly. Be sure to change the path as necessary to reflect your environment. The chown command may take a significant amount of time depending on the number of recordings in storage.

sudo service unifi-video stop
sudo chown -R unifi-video:unifi-video /srv/unifi-video/videos
sudo service unifi-video start

In certain cases—particularly when using network attached storage, the permissions or ownership of the root directory of the mounted storage may change. To avoid this, create a subfolder to use as a recording target and assign the appropriate permissions.

External Storage Device is Not Mounted

If external storage is used as the recording target, such as an external hard drive connected via USB or a NAS appliance, it is possible that the device has unexpectedly become unmounted. In some cases, the storage may not successfully mount after the NVR is rebooted, or the device may become unavailable during operation due to a disconnect, network issue, or configuration change.

Access the storage path on the NVR via SSH or Windows Explorer as applicable, and verify that the expected storage size is available and the storage is correctly mounted with appropriate permissions. In certain scenarios it is possible that UniFi Video may be writing to the local mount path while the storage device is unmounted, effectively consuming storage on the root or C:\ drive and interfering with the mount process.

System is in Emergency Shutdown State

If the available free space in the target recording directory is less than the Space to Keep Free setting, UniFi Video will enter Emergency Shutdown mode to maintain stability. In this mode, no new recordings will be stored to disk. Emergency Shutdown mode will be indicated as a log entry in server.log. To troubleshoot this issue:

1. Verify the video storage paths, as detailed above.
2. Verify that the Space to Keep Free storage retention settings are configured appropriately considering the size and configuration of your storage. Go to Settings > click the System Configuration button > Configure tab > Space to Keep Free and modify the slider accordingly. The UVC-NVR / UVC-NVR-2TB use a default setting of 10GB and 40GB respectfully.
3. Perform a Database Analysis, with Restore Recordings enabled. This feature can be accessed from Settings > System Configuration > Tools. Be sure to check Restore Recordings, then click Analyze. This is particularly important after restoring a configuration backup in order to import old recordings so they can be added to the purge rotation to free space.

If the Emergency Shutdown state persists, review the server.log and purge.log file for further entries that may describe the cause.

RAMDisk is Not Configured Correctly (Windows NVR)

If UniFi Video is unable to store inbound video segments to the temporary cache, recordings will not be processed. Verify that the RAMDisk has been correctly configured, is mounted with sufficient space (minimum 3GB), and that the path has been properly set in system.properties.

For more detailed information on the use of a Windows RAMDisk, see: UniFi Video – Using a RAMDisk as a UniFi Video Temporary Directory in Windows

Database is Inconsistent or Corrupt

In certain scenarios, a database that has inconsistent data may impede the NVR’s ability to process recordings. If all prior options have been exhausted, a database reset will restore the data and structure without losing vital configuration or prior recordings.

Overview

This article includes the most common issues that arise with UniFi Video connections done over the cloud. Cloud connections with UniFi Video are those done via https://video.ui.com/.

NVR Doesn’t Appear When Accessing Via Cloud

After logging in to https://video.ui.com, a prompt to Select NVR with a list of NVR options should appear. If an NVR is missing from that list, follow these steps:

NOTE:This only applies if for NVRs that have previously been adopted to Ubiquiti Cloud. Otherwise the appropriate step would be to click on Set Up New NVR.

Solution Steps

1. Log in to your UVC-NVR locally via its IP address. If you don’t know what the IP address of the NVR is, find it using the Ubiquiti Discovery Tool (Download Chrome App).
2. Verify that you are logged in with the email address of the Super Admin as seen in the Users section of the UniFi Video Controller.
3. Check to make sure the NVR is still adopted via the NVR UI in Settings.

Cannot Connect to NVR Via Cloud

After the NVR has been successfully adopted via video.ui.com, if the NVR is inaccessible via Cloud, determine the NVR has a red or green status icon in video.ui.com. The red or green status indicates whether or not the NVR is connected to the Ubiquiti cloud. Many times, even an NVR with a red (disconnected) status could still be fully functional, aside from the loss of Cloud access.

Solution Steps

Red Status. This means that your NVR is not reaching out to Cloud. Follow these steps to troubleshoot:

• Check the UI Status page to see if there is any issue on our side.
• Verify that the name of the NVR as shown in the UniFi Video Controller’s Settings matches how it appears in video.ui.com.
• If the NVR in question was restored from another UVC-NVR, it should be re-adopted. To do so, select the NVR that is inaccessible and click “Remove selected NVR”. Then proceed to re-adopt the NVR to the Cloud.
• Use this guide for best networking practices: UniFi-Video – Ports Used.

Green Status.

If your NVR has a green status, but you still cannot connect to your NVR, that means the the NVR is connected to Ubiquiti Cloud, but the device being used and the NVR can’t reach each other. See this guide for best networking practices: UniFi-Video – Ports Used to fix this issue.

Issues Adopting NVR to Cloud

Solution Steps

1. Make sure that all outbound Ports from the NVR are open and available, as per UniFi-Video – Ports Used.
2. This functionality makes use of some special features of ES6. It is recommended to use Google Chrome for best results.
3. Try clearing the browser cache and try an incognito window as well. Some browser extensions may interfere with this functionality.

UniFi Video – Troubleshooting Camera Disconnects

Overview

This article provides several possibilities to test when facing a camera that will disconnect for no apparent reason.

Introduction

UniFi Video cameras may disconnect from the NVR for a variety of reasons. Identifying whether the behavior affects specific cameras or all of them, whether the disconnects follow a pattern (such as disconnecting during sunset), or simply remain disconnected, will help identify the root cause of the issue.

Most importantly, consider if the camera disconnections warrant troubleshooting in the first place. Often camera disconnects can be triggered by changes made to the network, such as disconnecting a cable, restarting a switch, changing configurations, or even a power outage. Comparing the timestamp of the disconnect with the events and alerts from your UniFi Controller or network hardware may reveal the cause.

For cases where further investigation is required, this article discusses the common causes for camera disconnects.

Faulty Cable Infrastructure

Faulty wired infrastructure may cause unpredictable behavior, including camera disconnects or random reboots. Even though a camera may initially establish a network connection when first installed, a damaged or unreliable signal path can present problems that don’t become apparent until external factors such as interference, vibration, temperature fluctuations or further wear and tear affect the cabling.

The easiest way to quickly rule out wired infrastructure faults is to remove the camera from it’s installed location, and connect it using a short, known-good patch cable to the same switch that the NVR is connected. If the problem is resolved, then the issue is either related to the network hardware between your NVR and cameras (network switches, wireless links, etc), power related (as discussed below), or network cable related.

Problems caused by faulty network cabling are often seen in conjunction with:

• Long cable runs (exceeding the 100 meter maximum)
• Poor quality or damaged cable
• Faulty or incorrect RJ45 terminations
• Not using outdoor rated STP cable when appropriate
• ESD damage, due to improper grounding / shielding

Inadequate Power Supply

UniFi Cameras require a stable power supply in order to operate reliably. If the camera does not receive enough power, the camera may behave erratically causing disconnects.

A common symptom of a camera that doesn’t receive adequate power is when the device disconnects around sunset, as the camera will switch to night mode thus enabling the IR LEDs which more than double the power draw. Additionally, if a single power source is supplying multiple devices simultaneously, one or more devices may not boot properly after a cold start such as a power outage.

The power draw requirement for each camera model is documented in the product Data Sheet, which is downloadable in our Downloads page or at the bottom of each model’s page when navigating from our products page. Keep in mind that the cabling and associated infrastructure between the power source and the camera will generate resistance increasing the amount of power used and should be factored into the total wattage required from the power source. The length and quality of cable, quality of terminations, and additional in-line connections such as a patch panel should be considered.

To test if inadequate power is the root cause of camera disconnects, uninstall the camera from its mounting location and connect it to a suitable power supply such as a PoE switch or PoE injector using a short, known-good patch cable. Cover the light sensor typically located on the front of the camera in order to trigger a switch to night mode and turn on the IR LEDs or leave it overnight to go through a full 24 hour cycle.

If powering multiple devices off a PoE-IN switch such as a NanoSwitch, factor in the power draw of all connected devices, the power consumption of the switch itself, and estimate loss from cabling infrastructure. A NanoSwitch will typically require at least a 24V 1A PoE injector in order to power more than one camera or a camera and an airMAX radio.

If powering the cameras using a PoE switch, verify that the connected devices are not exceeding the total power budget available from the switch. A PoE switch should generally not be operated near its maximum power rating, as headroom should be allowed for the increased draw during startup.

If powering a camera using a PoE injector or an Instant 802.3af adapter, verify that the injector and adapter are adequate for the camera, and if necessary test using a different known-good injector or adapter. Instant 802.3af adapters in particular may work best if installed on the camera-side of the network cable, rather than at the switch.

Cabling infrastructure problems may also be a source of power related symptoms, and the troubleshooting steps from the previous section should be followed.

Unreliable Wireless Connection

If the camera is connected to the network via a wireless connection, as would be the case of a  G3-Micro, or when using external hardware like an airMAX radio as a client, verify that the wireless connection is stable enough to sustain the connection.

To help determine if the wireless connection is the cause for your disconnects, consider moving the camera or client radio within a few feet of the access point (AP). If the connection stabilizes, then the wireless connection needs to be addressed. Even if the connectivity issue persists, the wireless connection should still be investigated.

Factors that may cause frequent wireless disconnects include:

• Low wireless signal (SNR), as read either by the AP or the client (or camera)
• High interference (noise) caused by external sources, such as non-802.11 networks, machinery or appliances
• High wireless channel saturation, caused by high client density or nearby networks on the same channel

To improve the wireless connection, you can:

• Move the camera or the AP closer to each other, in order to reduce the distance and improve the wireless signal.
• Move the camera or the AP away from sources of interference, such as microwaves or cordless phone bases.
• Change the wireless network channel to one with lower utilization and fewer networks. You can use Ubiquiti’s WiFiman mobile application (available for iOS and Android) to identify channels with less networks, or UniFi’s built-in RF Environment scan.
• Install an additional AP closer to the camera on a separate channel, in order to reduce the wireless network load and improve the connection quality.

Please review the UniFi and airMAX Troubleshooting sections for further wireless help articles if necessary.

IP Address Conflicts

If the camera and another device on the network have the same IP address configured, it may cause the camera to frequently connect and disconnect. This will occur as the NVR will receive conflicting information as to what MAC address is associated with a specific IP address and as a result, NVR and camera traffic will be incorrectly routed to the wrong device.

• If the camera IP address has been manually configured, verify that the IP chosen is outside of the DHCP scope configured for the subnet on your router.
• Make sure that no other device on the network has been configured with the same IP address, either manually in the device configuration, or via a DHCP reservation (Static IP assignment) in the UniFi Controller or third-party router.

Inconsistent Camera Authentication or Configuration

Incorrect credentials, bad certificates, or other configuration related issues may cause connection failures and repeat disconnects from a camera. This is typically easily resolved by resetting and re-managing the camera:

1. In UniFi Video webUI, navigate to the Cameras section, and click on the corresponding camera to open the configuration pane.
2. Select the Manage tab and click Unmanage to expand the section. Click the Unmanage button and confirm.
   User Tip:In some browsers if there is another subsection expanded in the Manage tab, when you click on Unmanage it seems like nothing is happening. Collapse all other sections by clicking on them and try again.
3. In a new browser tab, open the camera’s web interface by browsing to the camera’s IP address as seen in the camera’s configuration pane.
4. Log into the camera interface using ubnt as the username. Depending on whether the camera was able to reconnect after it was unmanaged, the password may have been reset to ubnt, or you may need to use the Camera Password as configured in UniFi Video’s Settings page.
5. Take note of the network configuration settings if necessary, then proceed to factory reset the camera.
6. Once the reset is complete, re-manage the camera and verify configuration and connectivity.

Installation Environment

In rare circumstances, cameras that are installed in extreme conditions may experience overheating and become disconnected from the controller. Refer to the maximum environmental temperature rating for your camera model if the camera is installed in a high temperature location and relocate if necessary.

Low Bandwidth Warning

Overview

This article describes a few options to improve slow video streams which trigger the “Low Bandwidth” warning on the UniFi Video live view.

Introduction

Streaming is a very intense process for any machine. Even with newer and newer hardware, it is difficult to keep up with the demand for real time video in most use cases. This article includes a few pointers on what to check to determine the cause of the slow video stream(s) that triggers the Low Bandwidth warning in UniFi Video Live View.

This warning will appear if the client machine (i.e. computer where Live View is being used) is struggling to keep up with the demand for video decoding, or if the NVR hardware is slowing down due to some CPU intensive process. It does not necessarily mean the camera or NVR have low bandwidth.

ATTENTION:If you do not see the Low Bandwidth message like in the picture above, skip to step 2.

Step 1: Network Troubleshooting

In most cases the upload speed of one of the elements in the network is the culprit of triggering a Low Bandwidth warning. Always perform a thorough troubleshooting as described in this section first, before moving on to troubleshoot the camera.

Check the upload speed. Check the machine’s connection to the NVR—specifically the NVR’s effective upload speed. If the NVR is separated over the internet (WAN) then that network’s upload speed is a factor. You’ll need to make sure your network speed is up to the task. The following diagram shows a scenario where the UBNT cloud or port forwarding is being used to reach the NVR.

Notice the numbered connections from the camera all the way to the mobile, where a user is viewing the live video. Any one of these five connections could be the cause of the slow stream. In other words, the slowest upload speed of any of these will be the maximum speed available for the video stream.

In this second scenario, a local machine is used to view the video streams from the NVR, so the path from camera to user is shorter. Again, any of these connections can be the cause of low bandwidth. Check what the speed of each one is to determine if one of them is the cause. Typically, we find step 4 to be the culprit: make sure to check your WAN upload speed with your internet provider.

Step 2: Camera Troubleshooting

In the vast majority of cases, the Low Bandwidth warning is related to upload speeds and would become evident once the investigation mentioned in the section above is performed. In rare cases the issue will be related with the cameras. There are three ways this error could appear:

• On one camera stream
• On multiple camera streams
• On all camera streams

One Camera Stream

If symptoms only exhibit on one camera, it’s most likely a connection issue, or camera firmware issue. Try the following:

1. Reboot the camera.
2. Make sure the camera’s firmware is up to date.
3. Try swapping the camera’s ethernet cable, port, and uplink switch to cover all bases.

Multiple Camera Streams

1. If the same cameras present symptoms every time, it is likely a camera connection, or camera firmware issue. Try to establish a commonality between the cameras:

1.1 Are they on the same Switch? Test one of them on another switch or compatible POE injector.

1.2. Are they on another LAN? Make sure ports 7442 and 6666 are open to the NVR.

1.3. Are they on the same firmware? Try manually uploading a new firmware from our Downloads page on one of the cameras.

2. If symptoms appear on different cameras every time, it’s most likely a client-side processing issue. In other words, the computer used to view the video stream. To verify: open Task Manager (Windows) or the Activity Monitor app (macOS) and view the computer’s CPU usage.

You should be looking at the stats for the browser used to run UniFi Video. Mobile devices don’t always include a CPU monitor, you may have to install an app that functions as one. Alternatively, you can test on a computer to verify if the Low Bandwidth message appears, if it doesn’t, then the issue is with the mobile’s CPU is very probable that the phone’s CPU usage is at a very hione, or you can test the connection on a computer first to determine if the mobile’s speed is the problem.

All Camera Streams

In most cases this is indicative of a poor connection or a slow client-side CPU. Make sure to check the client’s CPU usage using the same instructions shown above, both before and after opening the video stream.

How to Reset a Camera to Factory Default Settings

Overview

There are two ways to reset your camera. The recommended method is to physically reset the device by using the reset button on the camera. Resetting via the WebUI is also possible in most cases. Find both processes described below.

Introduction

If you are unable to manage or otherwise configure a camera, it’s likely it will need to be reset back to factory settings. Once the reset has been completed, the camera login credentials should revert back to ‘ubnt’ for both the username and password.

Physical Reset

The reset button’s location will vary from model to model. Please check the camera’s Quick Start Guide to find its specific location. QSGs can be found in the Downloads page. Use a paper clip or a similar object to push the button within the small reset hole.

1. While the camera is powered on, press and hold the reset button for 10 seconds.
2. Release the button (the LEDs will stop glowing).
3. Do not disconnect the camera from its power source during the reboot process.
4. The camera will restore factory settings after a few minutes.

Camera WebUI Reset

Although the physical reset is the recommended method of taking your camera back to factory defaults, sometimes a WebUI reset can be more convenient. Find the camera’s IP address via WiFiman, or UniFi Video and then follow the steps below:

1. Connect to the camera’s IP address in your browser, and log in.
2. Go into the System tab.
3. Under the Maintenance section you will see the link for Reset to Defaults.
4. Click it and wait for your camera to be reset. Don’t unplug the device during this process.

How to Factory Reset an NVR Appliance

Overview

Read Next : Ubiquiti Unifi Cameras Firmware Software Download

This article explains how to reset an NVR Appliance to its original factory settings.

NOTES & REQUIREMENTS:

• The following guide is based on UniFi Video version 3.1.x and later.
• Factory resetting an NVR will remove all previous management settings and video data. Any custom configuration changes applied by the system administrator will be lost, such as file-systems mounted on iSCSI volumes or locally attached external disk drives.
• The default IP address of the NVR appliance is 192.168.1.30 (but will retrieve a DHCP-assigned address if a DHCP server is present).

Introduction

There are three methods to factory reset your NVR: via Graphical User Interface, Command Line Interface, or the reset button on the actual device. After resetting your NVR to factory defaults, please follow this article to bring it back to current firmware: UniFi Video – How to Update the NVR via SSH.

Graphical User Interface (GUI)

1. Open the NVR landing page in a browser (http://<NVR_APPLIANCE_IP>/). You do not need to include the default port “7443” as the NVR hardware itself is what will be managed, not UniFi Video.
   
2. Click on the gear icon on the upper right hand corner of the page to access the Configure Device page.
3. Log in as “root” system account (username/password should be either ubnt/ubnt or root/ubnt). If you’ve changed this password, and don’t have it anymore, proceed to the Hard (physical) reset method.
4. Navigate to the Maintenance tab.
5. Click “Reset to Defaults” button next to “Reset To Factory Defaults:”
   
6. Re-open the NVR landing page in a browser (http://<NVR_APPLIANCE_IP>/).

Command Line Interface (CLI)

1. Open a shell session to the NVR appliance e.g. ssh root@<NVR_APPLIANCE_IP>
2. Enter the following command-line
   nvr-systool reset2defaults
3. Re-open the NVR landing page in a browser (http://<NVR_APPLIANCE_IP>/).

For more options, type nvr-systool --help to list other administrative parameters. The nvr-systool is used by the NVR management console where this CLI approach is equivalent to the GUI steps.

Hard (Physical) Reset

1. Press and hold the Reset button (the crescent moon button) located below the Power button for 10+ seconds. The device will take up to 60+ seconds to restore the default configuration and return to the original factory version.
2. Re-open the NVR landing page in a browser (http://<NVR_APPLIANCE_IP>/).

UVC-Micro/G3-Micro Recovery

Overview

This article demonstrates how to recover a UVC-Micro and UVC-G3-Micro.

Introduction

The methods described in this article are comparable to a TFTP recovery done on a UVC, UVC-Dome, or UAP for example. The difference is that the UVC-Micro does not have an Ethernet interface, therefore, there is no direct way to interface with the unit via TFTP. Instead, the UVC-Micro makes use of the SD-Card slot on the back of the unit. In the case of the UVC-G3-Micro, on-board storage is used instead.

Steps: UVC-G3-Micro Recovery

1. Disconnect power from the UVC-Micro.
2. Insert a paperclip or similarly narrow object in to the reset hole on the opposing side of the LED and press down.
3. Continue holding this button while you apply power to the UVC-Micro. The LED will turn on and remain steady.
   User Tip:Hold the camera in one hand, and the paperclip pressing the button in the other. Have the magnetic base on a flat surface with the power adapter connected to the base. Slowly lower the camera over the base. The magnet will snap on, applying power. Be careful not to release the button.
4. After approximately 15-20 seconds, the LED will flash once. This is the indicator that the reset button may be released.
5. After an additional 30 seconds or so, the UVC-Micro will start emitting a tone indicating that the camera is in a default state and is ready to be provisioned.

Steps: UVC-Micro Recovery

NOTES & REQUIREMENTS:

If performing this recovery with a Windows computer, it will be necessary to download and install Win32 Disk Imager (Free). The firmware binary can be obtained from the firmware downloads page, or the Video Controller in the following places:

• Windows: C:\ProgramData\unifi-video\fw\A5S\
• Linux: /usr/lib/unifi-video/fw/A5S/

*The filename has been intentionally omitted as it will change depending on the software installed. There will be only one file in this folder.

1. Insert a microSD card (20MB or larger).
   WARNING:Contents will be overwritten. Please back up any contents that you wish to retain.
2. Write the firmware file to the microSD card. For Windows, see Note 1 below. For Linux & Mac, see Note 2 below.
   1. If using Windows follow this process:If using Windows, copy the .bin file to the same folder, then rename the copied .bin to have an extension of .img instead of .bin. Use Win32 Disk Imager to write the image to the drive letter of the microSD card.  Your result should look like this:

      

      Where:

      D:/Downloads/UVC.gen2.v3.1.0.38-devel.89002e2.150421.2034.img would be a firmware binary renamed to have a .img file extension

      [I:\] is the drive letter assigned to this microSD card by Windows. Then, all that is left is to click the Write button.

   2. If using Linux or Mac OS X follow this process:If using Mac or Linux, the dd command is used:

      dd if=/path/to/firmware/file.bin of=/path/to/microsd/card bs=8M; sync

      Root privileges may be required to be able to use dd. If this is the case, issue the following command prior to the dd command:

      sudo su -

      To find the path to your microSD card (what follows the “of=” part in the command above), you can use diskutil (Mac) or dmesg or fdisk (Linux).  Here are options for both Mac and Linux.

3. Unmount and remove the microSD card from the computer.
4. Disconnect power from the UVC-Micro.
5. Insert the microSD card into the spring-loaded slot in the back of the UVC-Micro.
6. Insert a paperclip or similarly narrow object in to the reset hole on the opposing side of the LED and press down.
7. Continue holding the reset button while you apply power to the UVC-Micro. The LED will turn on and remain steady.
   User Tip:Hold the camera in one hand, and the paperclip pressing the button in the other. Have the magnetic base on a flat surface with the power adapter connected to the base. Slowly lower the camera over the base. The magnet will snap on, applying power. Be careful not to release the button.
8. After approximately 15-20 seconds, the LED will flash once. This is the indicator that the reset button may be released.
9. After an additional 30 seconds or so, the camera will start emitting a tone indicating that it’s in a default state and is ready to be provisioned.
10. To reuse the microSD card, insert it back into the computer and reformat it.

How to Adopt a Remote Camera that is not Displaying in the NVR

Overview

This article helps troubleshoot a remote camera that is not appearing in UniFi Video.

NOTES & REQUIREMENTS:

• This procedure is not necessaryif all devices are on the same Layer 2 Network, or Broadcast domain.
• UniFi Video v3.1.5 is the last version that supports airCam models.

Introduction

This article is useful if your cameras are on a different network than your NVR, or are otherwise not appearing in your NVR’s camera list. There are two methods to adopt directly, Manual adoption, or Token Adoption. Token adoption is faster than Manual Adoption, especially when configuring multiple cameras.

Steps: Manual Adoption

1. Navigate to the camera’s web interface by entering its IP address in the browser.
2. The default username and password is ubnt/ubnt. (If unsuccessful try root/ubnt)
3. Enter the IP address of the NVR in the UniFi Video server field.

5. Click Save Changes at the bottom of the page.

6. Return to the NVR web interface by entering the NVR’s IP address in the browser.

7. On the Cameras view, enable the Unmanaged filter and locate the camera.

8. Proceed to adopt the camera.

Steps: Token Adoption

1. Navigate to the NVR’s Settings page.
2. If the Camera Adoption Token field is empty, click NEW TOKEN.
   ATTENTION:The token is only valid for 30 minutes, it will then disappear.
3. Navigate to the camera’s web interface by entering its IP address in the browser.
4. Enter the IP address of the NVR in the UniFi Video server field.
5. Enter the Adoption Token in the  Adoption Token field.
6. Click SAVE CHANGES. The Camera will automatically be adopted to your NVR.

How to Reset a UniFi Video Installation for Windows

Overview

This article will outline how to reset a UniFi Video installation and how to restore recordings under the Windows operating system. The article for resetting a Linux installation (or our hardware NVR), can be found here.

NOTES & REQUIREMENTS:

Please note that this will clear out all settings and managed cameras but therecordings will remain. If you do not restore a configuration backup, it will be necessary to re-manage the cameras, set up motion zones/sensitivities, reconnect the install to the cloud, etc. This method should only be used after a database repair has been attempted and been advised by a Ubiquiti employee.

Steps to Reset a UFV Installation

For versions 3.10.1 or Earlier:

1. If you wish to restore your current configuration after the reset, ensure you have a configuration backup, or generate one from the Settings page in UniFi Video before proceeding.

2. Shutdown UniFi Video via the notification area icon.

3. Run Notepad as an Administrator.

4. Select File > Open and navigate to C:\ProgramData\unifi-video\data\system.properties 

5. Locate the line that reads:

is_default=false

and change it to:

is_default=true

6. Restart UniFi Video via the notification area icon.

7. It will take a moment to wipe out the database and restart the web service.

8. Access the install as usual (https://[Your UniFi-Video IP address]:7443). The complete process of how to access the initial setup wizard can be found in the UniFi Video User Guide.

9. The initial setup wizard will appear. Either restore the backup saved prior to recover your configuration or complete the configuration wizard to configure the system.

10. As always, the first thing you should do after completing the wizard is to go to Settings > NVR Settings > Configure tab and check your storage path as well as the ‘Space to Keep Free’ setting.

For versions 3.10.2 or Later:

1. If you wish to restore your current configuration after the reset, ensure you have a configuration backup. You can generate one from the Settings page in UniFi Video.
2. Navigate to Settings > System Configuration > Configure > Tools > Controller – Check the Reset Box, and Click the Restart button. (You will need to be the Super Administrator to see this option.)
   
3. After a couple minutes, The initial setup wizard should appear (you may need to refresh your browser) – Either restore the backup saved prior to recover your configuration or complete the configuration wizard to configure the system.
4. As always, the first thing you should do after completing the wizard is go to Settings > NVR Settings > Configure tab and check your storage path as well as the “Space to Keep Free” setting.

Steps to Restore Recordings

The following methods demonstrate how to restore recordings.

For versions 3.9.0 or later:

1. Go to Settings > NVR Settings > Configure tab > Expand Tools section.
2. Check the “Restore Recordings” option, and click ANALYZE:
   

For versions 3.8.5 or earlier:

1. Edit the system.properties file (C:\ProgramData\unifi-video\data\system.properties) and add the following to the bottom:
   recording.recovery=true
2. Restart the UniFi Video service via service unifi-video restart.
3. Log in to the web interface.
4. Go to Settings > NVR Settings > Configure tab > Expand Tools section > Click the Analyze button. Your recordings will only restore if the storage path is correct.
5. Restoring recordings can take some time (anywhere from 30 minutes to 5+ hours depending on how many you have). You can continue to use the system as normal, as well as continue to manage your cameras and set up your configuration, but make sure you stay logged in while the analysis is complete.  A simple way to do this would be to open a Live Feed from a camera or a Live View to prevent the system from logging you out.

cp /path/to/firmware.bin ~/

tftp 192.168.1.20; bin; put ~/firmware.bin