End of support for Non UnifiOS devices

After November 1st, 2021 new releases of this integration will no longer support devices that do not run UnifiOS. This will affect all users who have a CloudKey+ with firmware version 1.x
All user with a UDMP, UNVR or a CloudKey+ with firmware V2.x will not be affected by this change.

We estimate that the number of users still having demand for this, is so small that it is no longer worth the time and effort we have to put in to support it. If you are on a CloudKey+ with FW 1.x, please make sure to upgrade it to a V2.x before November 1st, to be able to continue to upgrade this Integration and get bug fixes and new features.

The UniFi Protect Integration adds support for retrieving Camera feeds and Sensor data from a UniFi Protect installation on either a Ubiquiti CloudKey+ ,Ubiquiti UniFi Dream Machine Pro or UniFi Protect Network Video Recorder.

There is support for the following device types within Home Assistant:

• Camera
  • A camera entity for each camera found on the NVR device will be created
• Sensor
  • A sensor for each camera found will be created. This sensor will hold the current recording mode.
• Binary Sensor
  • One to two binary sensors will be created per camera found. There will always be a binary sensor recording if motion is detected per camera. If the camera is a doorbell, there will also be a binary sensor created that records if the doorbell is pressed.
• Switch
  • Several switches will be created per camera found. What switches is depended on the capbability of the specific camera. But typically these switches are used to control recording mode, Infrared and Video mode settings.
• Light
  • A light entity will be created for each UniFi Floodlight found. This works as a normal light entity, and has a brightness scale also.

It supports both regular Ubiquiti Cameras and the UniFi Doorbell. Camera feeds, Motion Sensors, Doorbell Sensors, Motion Setting Sensors and Switches will be created automativally for each Camera found, once the Integration has been configured.

1. Hardware Support
2. Prerequisites
3. Installation
4. UniFi Protect Services
5. UniFi Protect Events
6. Automating Services
   • Send a notfication when the doorbell is pressed
   • Setting Recording or IR Mode
   • Person Detection
   • Input Slider for Microphone Sensitivity
7. Enable Debug Logging
8. Contribute to Development

This Integration supports all Ubiquiti Hardware that can run UniFi Protect. Currently this includes:

• UniFi Protect Network Video Recorder (UNVR)
• UniFi Dream Machine Pro (UDMP)
• UniFi Cloud Key Gen2 Plus (CKGP)

The first two devices run UniFi's own operating system called UniFiOS, and the CKGP with Firmware V2.0.18 or greater also runs UniFiOS. This is important to note, as you will need to know this during installation if your NVR Device runs UniFiOS or not.

Ubiquity released V2.0.24 as an official firmware release for the CloudKey+, and it is recommended that people upgrade to this UniFiOS based firmware for their CloudKey+, as this gives a much better realtime experience.

CKGP with Firmware V1.x do NOT run UniFiOS

In the following we are refering to Devices that do run UniFiOS as UniFiOS Devices and devices that do NOT run UniFiOS as NON UniFiOS Devices

NOTE: Ubiquiti has now officially launched the V2.0.24 FW for the ClodKey Gen2+ which is a UniFiOS FW. So as of V0.8.0 of this Integration, no more testing and development is done on NON UniFiOS Devices. What is already working will still be there, but there is no guarantee that new features will work on these devices.

Before you install this Integration you need to ensure that the following two settings are applied in UniFi Protect:

1. Local User
   • Login to your Local Portal on your UniFiOS device, and click on Users
   • In the upper right corner, click on Add User
   • Click Add Admin, and fill out the form. Specific Fields to pay attention to:
     • Role: Must be Limited Admin
     • Account Type: Local Access Only
     • CONTROLLER PERMISSIONS - Under UniFi Protect, select Administrators.
   • Click Add in at the bottom Right.

HINT: A few users have reported that they had to restart their UDMP device after creating the local user for it to work. So if you get some kind of Error 500 when setting up the Integration, try restart the UDMP.

2. RTSP Stream

   The Integration uses the RTSP Stream as the Live Feed source, so this needs to be enabled on each camera. With the latest versions of UniFi Protect, the stream is enabled per default, but it is recommended to just check that this is done. To check and enable the the feature

   • open UniFi Protect and click on Devices
   • Select Manage in the Menu bar at the top
   • Click on the + Sign next to RTSP
   • Enable minimum 1 stream out of the 3 available. UniFi Protect will select the Stream with the Highest resolution

1. Local User
   • Login to UniFi Protect, and click on Users
   • Either select an existing User or Create a new one.
   • Specific Fields to pay attention to:
     • Roles: Must be part of Administrators group.
     • Local Username: Must be filled out
     • Local Password: Must be filled out

2. RTSP Stream

   The Integration uses the RTSP Stream as the Live Feed source, so this needs to be enabled on each camera. With the latest versions of UniFi Protect, the stream is enabled per default, but it is recommended to just check that this is done. To check and enable the the feature

   • open UniFi Protect and click on Devices
   • Select Manage in the Menu bar at the top
   • Click on the + Sign next to RTSP
   • Enable minimum 1 stream out of the 3 available. UniFi Protect will select the Stream with the Highest resolution

This Integration is part of the default HACS store. Search for unifi protect under Integrations and install from there. After the installation of the files you must restart Home Assistant, or else you will not be able to add UniFi Protect from the Integration Page.

If you are not familiar with HACS, or havn't installed it, I would recommend to look through the HACS documentation, before continuing. Even though you can install the Integration manually, I would recommend using HACS, as you would always be reminded when a new release is published.

Please note: All HACS does, is copying the needed files to Home Assistant, and placing them in the right directory. To get the Integration to work, you now need to go through the steps in the Configuration section.

Before you restart Home Assistant, make sure that the stream component is enabled. Open configuration.yaml and look for stream:. If not found add stream: somewhere in the file and save it.

To add UniFi Protect to your Home Assistant installation, go to the Integrations page inside the configuration panel, click on 'ADD INTEGRATION', find UniFi Protect, and add your UniFi Protect server by providing the Host IP, Port Number, Username and Password.

Note: If you can't find the UniFi Protect integration, hard refresh your browser, when you are on the Integrations page.

If the UniFi Protect Server is found on the network it will be added to your installation. After that, you can add more UniFi Protect Servers, should you have more than one installed.

You can only add UniFi Protect through the Integration page, Yaml configuration is no longer supported.

When you upgrade your CloudKey+ from FW V1.x to 2.x, your CK wil move to UniFiOS as core operating system. That also means that where you previously used port 7443 you now need to use port 443. There are two ways to fix this:

• Delete the UniFi Protect Integration and re-add it, using port 443.
• Edit the file .storage/core.config_entries in your Home Assistant instance. Search for UniFi Protect and change port 7443 to 443. Restart Home Assistant. (Make a backup firts)

host:
(string)(Required)
Type the IP address of your UniFi Protect NVR. Example: 192.168.1.1
Important If you run UniFiOS this must be the IP Address. of your UDMP

port:
(int)(Optional)
The port used to communicate with the NVR. Default is 7443.
Important If you run UniFiOS the port must be specified and it must be 443.

username:
(string)(Required)
The local username you setup under the Prerequisites section.

password:
(string)(Required)
The local password you setup under the Prerequisites section.

deactivate rtsp stream
(bool)Optional
If this box is checked, the camera stream will not use the RTSP stream, but instead jpeg push. This gives a realtime stream, but does not include Audio.

scan_interval:
(int)(Optional)
How often the Integration polls the UniFi Protect Server for Event Updates. Set a higher value if you have many Cameras (+20). This value only is only relevant for People using a CloudKey with V1.x FW. CloudKey V2.x, UDMP and UNVR users get the data pushed, so polling not needed.
Default value: 2 seconds

anonymous_snapshots:
(bool)(Optional)
If you need to save a Snapshot more often than every 10 seconds, enable this function. See below for prerequisites.
Default value: False

To use the Anonymous Snapshot, you must ensure that each Camera is configured to allow this. This cannot be done in UniFi Protect, but has to be done on each individual Camera.

1. Login to each of your Cameras by going to http://CAMERA_IP. The Username is ubnt and the Camera Password can be found in UniFi Protect under Settings.
2. If you have never logged in to the Camera before, it might take you through a Setup procedure - just make sure to keep it in UniFi Video mode, so that it is managed by UniFi Protect.
3. Once you are logged in, you will see an option on the Front page for enabling Anonymous Snapshots. Make sure this is checked, and then press the Save Changes button.
4. Repeat step 3 for each of your Cameras.

The Integration adds specific UniFi Protect services and supports the standard camera services. Below is a list of the UniFi Protect specific services:

Note: When using camera.enable_motion_detection, Recording in UniFi Protect will be set to motion. If you want to have the cameras recording all the time, you have to set that in UniFi Protect App or use the service unifiprotect.set_recording_mode.

The following UniFi Protect events are triggered when running this Integration:

Below is a couple of examples on how you can automate some of the things you might do with this Integration.

Below is a very basic example on how to perform an action when the doorbell is pressed. Modify the action part to what you want to happen.

alias: Detect Doorbell Pressed
description: Notify User when the doorbell is pressed
mode: single
trigger:
  - platform: event
    event_type: unifiprotect_doorbell
condition: []
action:
  - service: notify.notify
    data:
      message: There is somebody at your door
      title: The doorbell has been pressed

If you want to change Recording Mode or Infrared Mode for a camera, this can be done through the two services unifiprotect.set_recording_mode and unifiprotect.set_ir_mode. These Services support more than 2 different modes each, and as such it would be good to have a list to select from when switching the mode of those settings. I have not found a way to create a listbox as Custom Component, but it is fairly simpel to use an input_select integration and an Automation to achieve a UI friendly way of changing these modes. Below is an example that creates an inputselect* integration for one of the Cameras and then an example of an automation that is triggered whenever the user selects a new value in the dropdown list.

Start by creating the input_select integration. If you are on Version 107.x or greater that can now be done directly from the menu under Configuration and then Helpers. Click the PLUS sign at the bottom and use the Dropdown option. Important Fill in the Option part as seen below for the Infrared Service. If you do it manually add the following to your configuration.yaml file:

# Example configuration.yaml entry
input_select:
  camera_office_ir_mode:
    name: IR Mode for Camera Office
    options:
      - auto
      - always_on
      - led_off
      - always_off
    icon: mdi:brightness-4

If you did it manually, you need to restart Home Assistant, else you can continue.

Now add a new Automation, like the following:

- id: '1585900471122'
  alias: Camera Office IR Mode Change
  description: ''
  trigger:
  - entity_id: input_select.camera_office_ir_mode
    platform: state
  condition: []
  action:
  - data_template:
      entity_id: camera.camera_office
      ir_mode: '{{ states(''input_select.camera_office_ir_mode'') }}'
    entity_id: camera.camera_office
    service: unifiprotect.set_ir_mode

Thats it. Whenever you now select a new value from the Dropdown, the automation is activated, and the service is called to change the IR mode. The same can then be achieved for the recording_mode by changing the options and the service call in the automation.

If you have G4 Series Cameras, it is possible to do object detection directly on the Camera. Currently they only seem to support detecting a Person, but maybe Cars, Animals etc. will be added in the future. Here is an example of how you can use this to send a notification to your phone if a Person is detected on a Camera, where Recording mode is set to motion or always. In this example the camera is called camera.outdoor, so the corresponding Binary Motion Sensor is called binary_sensor.motion_outdoor. It is a very basic example, sending a Notification via the Notify Service Pushover, when a person has been detected, but it can be used to illustrate the use case.

- id: '1603355532588'
  alias: Send message when person detected
  description: ''
  trigger:
  - platform: state
    entity_id: binary_sensor.motion_outdoor
    to: person
    attribute: event_object
  condition: []
  action:
  - service: notify.pushover
    data:
      message: A person has been detected on the Camera
  mode: single

To set the Microphone sensitivity you can use the Service unifiprotect.set_mic_volume but if you want to be able to do this from Lovelace, you can add a Input Slider for each camera and then do it from there. This shows you how you can do that.

• Go to Configuration and select Helpers.
• Click + ADD HELPER and select Number.
• Name your Slider, and then you can leave the rest of the values as default. (Min 0, Max 100, Display mode Slider) and then click CREATE.

Now create a new Automation, that reacts to a value change of the above slider. In this case I named the slider input_number.volume_test_cam and the Camera is called camera.test_cam.

alias: Adjust Mic Sensitivity on Test CAM
description: ''
trigger:
  - platform: state
    entity_id: input_number.volume_test_cam
condition: []
action:
  - service: unifiprotect.set_mic_volume
    data:
      entity_id: camera.test_cam
      level: '{{ states(''input_number.volume_test_cam'') | int }}'
    entity_id: ' camera.test_cam'
mode: single

If logs are needed for debugging or reporting an issue, use the following configuration.yaml:

logger:
  default: error
  logs:
    custom_components.unifiprotect: debug

1. Fork and clone the repository.

2. Open in VSCode and choose to open in devcontainer. Must have VSCode devcontainer prerequisites.

3. Run the command container start from VSCode terminal

4. A fresh Home Assistant test instance will install and will eventually be running on port 9123 with this integration running

5. When the container is running, go to http://localhost:9123 and the add UniFi Protect from the Integration Page.