Hikvision integration with Link’nX: events and scenarios
With Link’nX, the events of a Hikvision camera can trigger scenarios: motion detection, intrusion, line crossing, region entrance or exit, license plate, face recognition, person density or temperature alarms. An action can also enable or disable the camera’s privacy mask. This page sums up what the integration does and the commissioning order.
What the Hikvision integration does
Section titled “What the Hikvision integration does”| Need | Where to configure it | Guide |
|---|---|---|
| Declare the camera with its IPv4 address and account | Devices → Security & Access → Hikvision | Declare a Hikvision, Reolink or UniFi Protect camera |
| Send the camera’s events to Link’nX | Camera interface, with the How to configure HIK device help | Prepare the transmission of Hikvision events |
| Start a scenario on an event, filtered by region, target, plate, name or rule | HIKvision triggers | Use Hikvision commands and events |
| Enable or disable the privacy mask in a scenario | HIKvision actions | Use Hikvision commands and events |
Step-by-step commissioning
Section titled “Step-by-step commissioning”- Declare the camera: name, IPv4 address, username and password of the intended account.
- Configure event transmission in the camera: Link’nX address as the destination, URL /hik, then Notify Surveillance Center for each event to process.
- Prepare the HIKvision trigger or action, choosing the event before the camera.
- Add it to the intended scenario, then check the scenario’s activation and conditions.
Good to know
Section titled “Good to know”- In the variant illustrated by the help, the destination is set in Configuration → Network → Advanced Settings → Alarm Server, under HTTP Data Transmission, over HTTP on port 4000. The help recommends fixed IP addresses for the camera and Link’nX.
- Zones, rules, thresholds, the plate allow list and people’s names are configured on the camera; the Link’nX trigger filters the events received.
- In a trigger, all the criteria filled in must match; an empty field or — ignores a simple filter. Counting requires an operator and a number of people, face recognition a minimum rate from 0 to 100%.
- The privacy mask must be prepared in the camera. A mask action that works does not prove that events are transmitted.
- An automation based on a vehicle’s direction of movement, or a != comparison, must be confirmed with support before it is put into service.
Reolink and UniFi Protect cameras are declared in the same guide: see Reolink and UniFi. For other cameras and intercoms, see Security and video surveillance.