---
title: Add a Hikvision, Reolink or UniFi Protect camera in Link’nX
description: "Add a Hikvision or Reolink camera or a UniFi Protect device in Link’nX: IP address, account, HTTPS port, NVR channel, Protect device id and device kind."
canonical: https://wiki.can-nx.com/en/guides/link-camera-devices/
language: en
product: Link’nX
audience:
  - administrateur
  - installateur
context: "Link’nX web: Devices, Security & Access, Hikvision, Reolink or UniFi Protect declaration"
---

# Add a Hikvision, Reolink or UniFi Protect camera in Link’nX

Context: Link’nX web: Devices, Security & Access, Hikvision, Reolink or UniFi Protect declaration

Declare a Hikvision or Reolink camera, or a UniFi Protect device (camera, light, sensor or chime), in Link’nX with its IPv4 address, the connection account and the fields specific to its family. This declaration is the prerequisite for the device’s commands, events and KNX associations.

Intended for the authorized installer or administrator.

## Before you start

- Check the project and the gateway in Link’nX.
- Have ready the connection address, the account intended for the device and the expected functions.
- Enter the credentials in the Link’nX form only.

## Open the form of the right family

1. Open **Devices → Security & Access**, then **Hikvision**, **Reolink** or **UniFi Protect**. You can also search for this name in **Search a device...**. On mobile, first open the three-line menu. For a missing or locked card, follow the [navigation guide](https://wiki.can-nx.com/en/guides/link-navigation/).
2. Click **Add**. The form is titled **Hikvision camera declaration**, **Reolink camera declaration** or **UniFi Protect declaration**.

## Fill in the declaration

1. Fill in **Name**, required and limited to 64 characters. Choose a name that distinguishes the hardware, for example “Reception camera” (fictitious example).
2. Fill in the fields specific to the family, described in the table below.
3. Fill in **Username** and **Password**, both required. Enter the values of your installation, never example values.

| Family | Connection and specific fields |
| --- | --- |
| **Hikvision** | **IP address**: IPv4 of the camera. Have the account authorized for the expected functions ready. Event transmission also requires the [Hikvision configuration](https://wiki.can-nx.com/en/guides/link-hik-events-setup/). |
| **Reolink** | **IP address**: IPv4 of the camera or address intended for the relevant channel. **Port**: HTTPS port, prefilled with **443**, between **1 and 65535**. **Channel**: index greater than or equal to **0**; the help indicates **0** for a single-lens camera, or the NVR channel. Have the exact channel of the installation confirmed. |
| **UniFi Protect** | **IP address**: IPv4 of the UniFi Protect/NVR controller that manages the device. **Protect device id**: exact identifier of the device in Protect, different from the controller address. **Device kind**: **Camera**, **Light**, **Sensor** or **Chime**, depending on the hardware. The initial choice is **Camera**. |

For UniFi Protect, the field help indicates that the identifier can come from the device URL or from the Protect configuration information. Several devices can share the address of the same controller while having distinct identifiers and kinds. If you do not know which identifier to use, ask support for it without sending a full connection URL, a token or a private export.

For Reolink, **Another Reolink camera already uses this IP address** blocks a new declaration with an address already in use: check the existing list. If you need to declare several channels of the same NVR with the same address, have support confirm the appropriate path, without replacing the address with an arbitrary one.

## Save the declaration

1. Click the **floppy disk at the bottom right**. Wait for **Success!** and the return to the list.
2. Find the row with its **Name** and its **IP address**. Reolink also displays **Port** and **Channel**.

## Edit or delete a declaration

1. Click the **Edit** pencil of the row. The title becomes **Hikvision camera modification**, **Reolink camera modification** or **UniFi Protect modification**.
2. Correct the values, save with the floppy disk and wait for **Updated!**.

In the Hikvision and UniFi Protect forms, changing **Password** displays **Confirm password**. Enter the same new value in both fields; **Passwords do not match** indicates a confirmation to correct. The Reolink form keeps a single **Password** field, without confirmation.

To abandon a change, leave the form. In **Unsaved changes**, **Cancel** keeps you in the form and **Don't save** discards the changes.

Before deleting a declaration, have the actions, triggers, scenarios and KNX associations that use it checked. If the consequences are not established, ask support for help.

## Check the result

1. Reopen the declaration with the **Edit** pencil and review the saved values.
2. Then test a real function of the device, a command or an event, with the guide for its family: **Success!** confirms that the declaration is saved, not the connection to the hardware.

| Family | Next step |
| --- | --- |
| **Hikvision** | [Prepare event transmission](https://wiki.can-nx.com/en/guides/link-hik-events-setup/), then [use Hikvision commands and events](https://wiki.can-nx.com/en/guides/link-hik-automation/) |
| **Reolink** | [Control the camera and use its detections](https://wiki.can-nx.com/en/guides/link-reolink-automation/) or [map it to KNX commands and feedback](https://wiki.can-nx.com/en/guides/link-reolink-gateway/) |
| **UniFi Protect** | [Control UniFi Protect and react to events](https://wiki.can-nx.com/en/guides/link-unifi-protect-automation/) or [map it to KNX commands and feedback](https://wiki.can-nx.com/en/guides/link-unifi-protect-gateway/) |

## Troubleshooting

- The floppy disk stays grayed out: check the required fields and the IPv4 format. For Reolink, also check for a duplicate address, the port and the channel. For UniFi Protect, check the identifier and the device kind. After a Hikvision or UniFi Protect password change, check its confirmation.
- The declaration is saved, but a command or an event does not work: check that it is the right device, then its connection address and the intended account. For UniFi Protect, check the controller address, the device identifier and its kind separately. For Reolink, check the channel. Then go through the configuration specific to the function in the family guide listed above.

## Contact support

If these checks have already failed, write to support@can-nx.com with the product, the model, the project and gateway, the expected function, the message displayed and the tests carried out. Do not send a password or a private file.

French labels: **Ajouter**, **Nom**, **Adresse IP**, **Nom utilisateur**, **Mot de passe**, **Port**, **Canal**; for UniFi Protect, **Identifiant de l'appareil Protect** and **Type d'appareil** (**Caméra**, **Éclairage**, **Capteur**, **Carillon**); after changing the password, **Confirmer le mot de passe**.