Overview | Configuration | Bookmarked Events |
Overview
The NX Witness integration allows multiple NX Witness servers and cameras to be used with a PDK.io Customer Account. When configured, the NX Witness integration enables the sending of events, generation of bookmarks, and the activating of devices from the NX Witness application.
Configuration
Requirements
- The Network Optix NX Witness VMS integration is only available for PDK.io 2.0 Customer Accounts.
- This integration requires v5.1 or later of the Network Optix NX Witness application.
- To be able to use the NX Witness integration, the Partner attempting to configure the Integration must have either the Owner or Administrator role in the NX Witness application.
- A Partner with Integrator permission is required for the initial setup of the NX Witness integration. For information on this, refer to the article about System Settings - Integrations.
The NX Witness integration allows a Partner to configure specific Readers and Cameras for notifications and Bookmarked Events are required. Viewing of the camera video display is not supported inside PDK.io and can only performed from the NX Witness application.
If the connection between PDK.io and NX Witness stops working, an email will be sent to the Owner of the PDK.io account. If additional users should receive these notifications, we recommend forwarding the message from your email system.
Settings
NX Witness System - Select from the NX Witness systems that your email account has access to. If the NX Witness system is not listed, follow the steps from Network Optix to connect the NX Witness system to the cloud. For information regarding the setup of the NX Witness system, please refer to the Documentation from Network Optix.
NX Witness Server - Select from the online NX Witness servers connected to the NX Witness system.
PDK Cloud Node - Select between the Cloud Node available on the PDK.io Customer Account.
PDK Partition - Select the Partition on the Customer Account.
During setup and configuration of the NX Witness integration, a Partner will need to select the Cloud Node (PDK Cloud Node) and PDK Partition, then the Device (PDK Device) to associate with the camera(s).
Filter cameras by name -
Camera Name - This displays the name of the Camera as configured in the NX Witness application, above a recent image from the camera from the NX Witness application.
PDK Device - Select the PDK.io Device to associate the Camera with, multiple cameras can be associated with a single PDK.io Device. The associated PDK.io Device events listed below will be sent to the NX Witness application.
Display a lock trigger - This will display a Lock 'soft trigger' icon in the lower right corner of the associated Live Camera Stream in the NX Witness application.
Display an unlock trigger - This will display a Unlock 'soft trigger' icon in the lower right corner of the associated Live Camera Stream in the NX Witness application to Open/Close the Device for the Dwell time configured for the Device.
Bookmarked Events
The Soft Triggers events and Event notifications sent from PDK.io to NX Witness will produce Bookmark events in the NX Witness application.
The following table shows the PDK.io Events and associated NX Witness Generic Events that are sent from PDK.io to the NX Witness system for notification/display in the NX Witness application.
VMS Event | VMS Message | PDK Event |
device.input.relay.off | <deviceName> locked | Device deactivated/locked |
device.input.relay.on | <deviceName> unlocked | Device activated/unlocked |
device.alarm.forced* | <deviceName> forced alarm activated | Device Forced |
device.alarm.forced.cleared | <deviceName> forced alarm deactivated | Device Forced Cleared |
device.alarm.propped.off | <deviceName> prop alarm deactivated | Device Propped Cleared |
device.alarm.propped.on* | <deviceName> prop alarm activated | Device Propped |
device.autoopen.off | <deviceName> auto open deactivated | Device Auto Open deactivated |
device.autoopen.on | <deviceName> auto open activated | Device Auto Open activated |
device.autoopen.override.off | <deviceName> auto open override deactivated | Device Auto Open Deny Deactivated |
device.autoopen.override.on | <deviceName> auto open override activated | Device Auto Open Deny Activated |
device.forceclose.off | <deviceName> DND deactivated | Device Do Not Disturb Deactivated |
device.forceclose.on | <deviceName> DND activated | Device Do Not Disturb Activated |
device.forceopen.off | <deviceName> force unlock deactivated | Device Force Open Deactivated |
device.forceopen.on | <deviceName> force unlock activated | Device Force Open Activated |
device.input.rex.on | <deviceName> REX activated | Device REX Activated |
device.request.allowed | <firstName lastName> allowed access to <deviceName> | Device Access Allows |
device.request.denied | <firstName lastName> denied access to <deviceName> | Device Access Denied |
device.request.unknown | Unknown user denied access to <deviceName> | Device Unknown Credential |
* The 'device.alarm.forced' and 'device.alarm.propped.on' Generic Events are sent from PDK.io to the NX Witness application, with a 'Force Acknowledge' alert set. A Force Acknowledge alert will require interaction within the video system and may require a note to be added to the alert. Notifications for Force Acknowledge alerts are only available in the NX Witness desktop application.
Comments
0 comments
Please sign in to leave a comment.