Hikvision in Link’nX: event triggers and privacy mask
Link’nXAdministratorInstaller
Link’nX web: Hikvision actions and triggers of a declared camera
In Link’nX, a Hikvision action enables or disables a camera’s privacy mask. A Hikvision trigger starts a scenario on a camera event: motion, intrusion, line crossing, license plate, recognized face, people counting or temperature alarm.
For the authorized installer or administrator. The zones, rules and functions used must be configured on the relevant model: a choice offered in Link’nX does not create that capability on the camera.
Before you start
Section titled “Before you start”- The camera is declared in Link’nX.
- For a trigger, the transmission of the camera’s events is configured.
- For a mask action, the privacy mask is prepared in the camera configuration.
Enable or disable the privacy mask
Section titled “Enable or disable the privacy mask”- Open Actions → Add. In Select an action type, choose HIKvision, then fill in Name.
- In Hikvision devices, select a camera.
- In Action, choose Enable privacy mask or Disable privacy mask.
- Click the floppy disk at the bottom right and wait for Success!.
- To automate it, add the action to the relevant scenario.
Saving does not run the command. To edit or duplicate an action, follow the actions guide.
Create a trigger on a Hikvision event
Section titled “Create a trigger on a Hikvision event”- Open Triggers → Add. In Select a trigger type, choose HIKvision, then fill in Name.
- Choose Event first, then select Hikvision device(s). Follow this order when creating.
- In Event conditions, fill in the necessary criteria using the table in the next section. The fields change with the event; their help appears on hover.
- Save with the floppy disk at the bottom right and wait for Success!.
- Associate the trigger with the intended scenario, with the desired actions: a saved trigger is not automatically associated with a scenario.
The criteria filled in must all match the received event. For simple filters, an empty field or — ignores the criterion. After changing the event, review all the criteria. People counting and the recognition rate require the settings described below.
For editing, duplicating or confirming the affected scenarios, follow the triggers guide.
Choose the criteria for each event
Section titled “Choose the criteria for each event”| Event | Criteria to prepare |
|---|---|
| Motion detection alarm | No additional filter in this form. |
| Intrusion detection, Line crossing detection, Region entrance detection, Region exiting detection | Exact Region ID; Detection target type → Human / Vehicle / —. An empty criterion accepts all the values of that criterion. |
| Automatic number-plate recognition alarm | License plate number without added spaces; Accessibility rule → Vehicle is allowed (whitelisted) / Vehicle is blocked (blacklisted) / —. The allow list is configured on the camera. |
| Face recognition | Name identical to the one configured on the camera if you target a person; Minimum recognition rate: slider, from 0 to 100%. |
| Person density detection | Operator and People amount, to be filled in together; Custom name and Rule name to specify the level or rule configured on the camera. |
| Regional People Exception Alarm | The relevant Rule name, if you filter a rule. The alarm must be defined on the camera. |
| Temperature Measurement Precautionary Alarm, Temperature Measurement Alarm | The relevant Region ID, if you filter a region. The thresholds are configured on the thermal camera, not in this trigger. |
People counting
Section titled “People counting”Choose the greater than, less than or equal to symbol according to the goal, and always fill in the number together with the operator. Do not leave a rule name alone with an incomplete operator/number pair.
Fictitious example: the “greater than” operator and People amount = 0 suit a rule intended to react as soon as at least one person is counted. For the != choice or a comparison not described here, have the applicable path confirmed by support.
License plate
Section titled “License plate”The path described here covers the plate and the access rule, not an opening or closing automation based on the direction of movement. If the result of an automation depends on the Movement direction of the vehicle from the camera, contact support before putting it into service.
Face recognition
Section titled “Face recognition”Explicitly set the intended rate after choosing the event, then review it after saving. The slider help recommends a rate from 60% to 90%: too low, it may accept unknown individuals; too high, it may reject an expected person.
This rate is a matching criterion, not a guarantee of identification. Keep the threshold intended with the installer, without lowering it just to make an automation react. The form asks for neither a face image nor a database of people.
Check the result
Section titled “Check the result”- Find and reopen the action to review the camera and the command. For a trigger, review the camera, the event and the criteria, including the recognition rate.
- Check that the trigger and the actions are in the intended scenario, then the activation and conditions of that scenario.
- Test on site: trigger the expected event if possible and watch the scenario react. For the mask, check the expected privacy result on the image when the action runs. Success! confirms the save, not the result on the camera.
Troubleshooting
Section titled “Troubleshooting”- Trigger with no reaction: first check the camera and the event type, then the criteria: region identifier, target, plate without stray spaces, configured rule, complete operator/number pair or intended threshold.
- Criterion too precise: it can exclude an event. Before removing a criterion from an access automation, check the consequences.
- Event present on the camera but no reaction in Link’nX: review the transmission configuration, then the association with the scenario, its activation and its conditions. Events depend on this transmission, which is separate from commands: check it even if the mask action works.
- The form does not keep the expected criteria, or the checks above have failed: contact support.
Contact support
Section titled “Contact support”Write to support@can-nx.com stating the project and gateway, the camera model, the action or trigger concerned, the event, the symptom and the tests carried out. Do not send a password, a real plate, a face photo or a private database.
French labels: HIKvision, Appareils Hikvision, Activer le masque de confidentialité / Désactiver le masque de confidentialité, Évènement, Appareil(s) Hikvision, ID/numéro de la région, Type de cible à détecter., Numéro de la plaque d’immatriculation, Règle d’accès, Taux de reconnaissance minimal :, Opérateur, Nombre de personnes, Nom de la règle; events Détection de mouvement, Détection d’une intrusion, Reconnaissance faciale and Détection d’une densité de personne.