Adding NVRs
If you prefer adding cameras through an NVR rather than camera-by-camera, please start by following the steps in Getting started.
Alarm sending from an NVR is almost identical to the process outlined in Adding cameras and most steps can be followed as-is. We also have vendor-specific APIs for some NVRs (see below) to streamline the process.
If this applies to your NVR, everything is probably already working great after following the above guide! Great job!
Sometimes, however, NVRs are a bit more challenging than other devices to set up. A common problem you may run into is:
Multiple cameras appear as only one
Alarms from every camera in the NVR may show up as a single camera in the Irisity Alarm Filter. This state is not sustainable since the AI filtering engine will not work if images and clips connected to one camera do not come from the same camera consistently.
If this happens to you, there are a few ways to mitigate the problem. Read on in the following sections to find more ways to efficiently add NVRs.
If Irisity's Alarm Filter has a vendor-specific API available, use that. The vendor-specific handling of incoming alarms allows us to decode the alarm package fully to distinguish between images and clips from different channels. We currently support: We currently support
- Hikvision NVRs
- Uniview NVRs (upcoming support)
If there is no vendor-specific API available, you need to adjust the settings in the NVR to ensure that different camera id:s are sent depending on what channel triggered the alarm.
How to do this differs from manufacturer to manufacturer, but the end result should be as shown below.
Rather than sending alarms from all channels to one URL endpoint, they need to separated:
- Before: Channel 1, 2, 3, 4 are all sending alarms to: POST https://in.alarmfilter.irisity.io/?c=nvr-unique-id-123
- After:
- Channel 1 sends alarms to POST https://in.alarmfilter.irisity.io/?c=nvr-unique-id-123-channel-1
- Channel 2 sends alarms to POST https://in.alarmfilter.irisity.io/?c=nvr-unique-id-123-channel-2
- ...
Rather than sending alarms from all channels to one email recipient, they need to separated:
- After:
- ...
Email recipients can be shortened as needed depending on the support in the NVR. An example is shown below:
Please refer to the API Documentation for full details.
In the section above, we use the camera id to identify a single camera. It is also possible to uniquely identify the NVR and to use a second parameter to identify the channel uniquely within the NVR.
For HTTPS this looks like this:
Before: POST https://in.alarmfilter.irisity.io/?c=nvr-unique-id-123
After: POST https://in.alarmfilter.irisity.io/?nvr=unique-nvr-id-123&c=channel-1
Note that we now have two parameter, nvr= to identify the NVR and c= to identify the camera/channel inside the NVR.
For SMTP this looks like this:
Before: To: [email protected]
Before: To: nvr=unique-nvr-id-123&[email protected]
Note that we now have two parameter, nvr= to identify the NVR and c= to identify the camera/channel inside the NVR.
Please refer to the API Documentation for full details. While the above address is a valid email address, security industry equipment is notorious for having very limited support for characters. We therefore have several options for replacement characters.
If NVR configuration fails for some reason, you can always try Adding cameras one by one instead.
If you have some issues adding NVRs from one or more manufacturers, we're always happy to help. Often we can assist with configuration, and if a vendor-specific API is required we can always collaborate to create that.
Please Submit a support request to get in touch with us!