Nx Witness v4.1

Push Notifications

Finally! Push Notifications are here! That’s right. You can now send Push Notifications to Nx Witness Mobile like a boss.

• Use the Rules Engine to send Push Notifications to mobile devices based on analytic events, motion, soft triggers, and more!
• Users can receive push notifications from multiple systems and turn on/off notifications as they please on their mobile device.
• Users can create custom text for notifications in the Rules Engine via Desktop Client.

New Embedded Browser

The Nx Witness Desktop Client now uses a full-featured embedded Chromium browser (v.77.0.3865) that makes it easier to ever to use “soft integrations” allowing interactive browser-based control of 3rd party software or hardware interfaces and / or custom web-based integrations.

Cameras Web Page in Camera Settings Dialog – with the new browser camera web pages can now be opened up in the Camera Settings dialog allowing users to configure/access camera web pages inside Desktop Client even when connecting to their system remotely.

System Health Monitoring

System Health Monitoring in Cloud and local Server Web admin makes it easy to keep any eye on the health of your system devices so you can be proactive in keeping your system up and running.

Alerts – automatically detected / identified problems with a System
System Info – # of servers, channels, storage located, users, etc
Servers – storage state, CPU usage, NICs state, hardware spec, etc.
Cameras – online/offline state, resolution, fps, quality, etc.
Storage Locations – path, server, type, status, read/write rate, etc
Network Interfaces – name, server, state, IP address, I/O rates

Analytics Events Region of Interest (ROI) Configuration in Camera Settings

Nx Witness v4.1 also introduces the ability for operators to configure the region of interest for in-camera analytics events by drawing lines, boxes, polygons and more when configuring a camera-based video analytic from the Desktop Client (no need to go to the camera web page).

• Currently supports Hanwha AI cameras using firmware version 1.41.xx or higher.
• Want more brands? Yell at our Developers on the Nx Community and get your friends to up-vote your suggestion.

BEST SERVER SELECTION

• In prior releases, Desktop Client would connect to a random available server via Cloud. Now Cloud connections are routed through the Server with the best uplink.
• Added the ability for users to specify the preferred Server for connections. The configured Desktop Client will attempt to connect to the preferred Server first, and if it is not reachable, it will detect and connect via the Server with the best uplink.

SERVER SIDE MOTION DETECTION IMPROVED

False positives detection introduced to increase accuracy of detected motion events (e.g., turning on/off lights or switching camera day/night mode are now likely to be ignored)

MACOS PERFORMANCE IMPROVED

Improved MacOS performance and introduced an experimental setting to limit frame rate and reduce CPU load (see Local Settings -> Advanced).

CLOUD CONNECTIVITY IMPROVED

Improved cloud connectivity on certain network environments.

ADDED THE ABILITY TO PIN THE TIMELINE IN FULLSCREEN MODE

• When the Timeline is pinned it will remain fixed on the screen.
• If the Timeline is pinned in fullscreen mode and the user leaves fullscreen it will be pinned for all cameras on the layout when the user returns to fullscreen mode.

2-WAY AUDIO API

Allows third-party web clients to send audio (from client microphone) to and get audio from cameras.

ADDED TIME ZONE OPTION FOR VIRTUAL CAMERAS

Time Zone can now be specified for virtual cameras. If “Time Zone” is set to “Auto”, then the time zone is defined by metadata or UTC if there’s no time zone specified in the file. If set to “Client”, the Time Zone is defined by the desktop client.

ADDITIONAL ACTION PARAMETER PLACEHOLDERS FOR THE "DO HTTP REQUEST" ACTION

Placeholders can be added to the HTTP POST request body to be automatically replaced by the corresponding values from Analytics Event parameters. This feature is only applicable to Analytics and Generic Events. Placeholders syntax:

• {event.cameraId} – replaced by the camera ID (e.g., })
• {event.cameraName} – replaced by the camera name (e.g., PND-9080R)
• {event.eventType} – replaced by the event type (e.g., nx.stub.objectInTheArea or nx.stub.lineCrossing)
• {event.eventName} – replaced by the event name (e.g., Object in the area or Line crossing)
• {event.caption} – replaced by the caption (e.g., “Line crossing – impulse event (caption)”)
• {event.description} – replaced by the description (e.g., “Line crossing – impulse event (description)”).

DATABASE BACKUPS ARE NOW CATEGORIZED INTO THE FOLLOWING TYPES

• Created after system merge
• Created after updates
• Initiated via API
• Scheduled