Logical Rules/Rule Time Management/ Schedule Trigger Rule

https://support.networkoptix.com/hc/en-us/community/posts/360039337674-Logical-functions?input_string=Logical%20Rules

This was previously posted 6 years ago by a deleted account. In the hopes of getting fresh eyes on the idea, I'm re-submitting it as a feature request. I apologize if this this frowned upon, but a +1 vote on a 6-year old topic seems as if it wouldn't have done much to revive the topic.

This particular request hits two key items that I would say are both great ideas in their own rights, but also work very well together.

#1. Some form of logical rule
- Rule #1 triggers
- Rule #2, only triggers if Rule #1 is triggered

Example:
- Rule #1: Line crossing event takes place on Camera A, PTZ preset action takes place on Camera B
- Rule #2: If Rule #1 is triggered as an event, API call to Camera B is sent by Spectrum to automatically trigger a camera-native function.

Without a form of logical rule in place, it becomes much more difficult to get these two functions to work in tandem.

#2. Time delay/Management on the Rule
(beneficial on a logical rule, but also helpful for rules in general)

- Rule #1 triggers
- Rule #2, only triggers if Rule #1 is triggered, with an additional parameter to delay the trigger (x) seconds/minutes

Example:
- Rule #1: Line crossing event takes place on Camera A, PTZ preset action takes place on Camera B
- Rule #2: If Rule #1 is triggered as an event, after a 2 second delay, API call to Camera B is sent by Spectrum to automatically trigger a camera-native function.

This could help prevent scenarios where the two rules create communicative conflict (such as rule #2 overriding rule #1 before it completes, or rule #2 failing because rule #1 is still being processed). If a logical rule, it could also have its own schedule independent of the parent rule (Rule #1 only Mon-Fri, Rule #2 has its own schedule in relation to what's available from Rule #1)

#3. Scheduled Trigger
Additionally, having a “schedule event rule” with the option to schedule an automatic trigger based on specified times would also be extremely helpful.

Example:

WHEN EVENT: Reoccurring Schedule Trigger

By Specific Date/Time

Server Time Used: Auto (can specify by server in merged environments)

Time: (Option to add multiple times between 00:00:00 and 23:59:59)

Days: (Mon-Sun)

Months: (Jan-Dec)

(Optional) Expiration [Disables Rule]: (Specific time/date in the future to disable the rule)

or

By General Timeframes

Time frame: Once every day/7 days(Weekly)/ 14 days (Bi-Weekly)/30 days (Monthly)
Start of first trigger (Customer specifies date and time)

EVENT ACTION: Any action the customer needs to be performed on a regular basis;
- API calls to send screenshots
- Triggering audio on Speakers ("We are closing in 5 minutes")
- Monitoring server status
- Semi-automated PTZ controls (Preset 1 in the morning, Preset 2 in the evening)

Over the years, I've had countless customers asking for these functions, or having configurations where these functions would have made the integration/configuration much simpler. Considering the current status of Nx Witness and the vast amounts of changes from 6 years ago, I think functions like this are more important than ever. With new integrations being added all the time, this would greatly improve the quality of life of our customers.

Andrew Sharrem

Authorized Reseller

June 17, 2026 21:13

Hi Rhaphiel,
Nx Powertoys is a simple integration that supports many (if not all) of your feature requests.

Timer event injection
Advanced Schedules
ARM / DISARM rules as a group

In combination you can have some very advanced rule logic.
Although in Beta while Nx API v4 is still evolving, it is stable for production use.
It supports VMS versions 5.1.4.38717 +

Regards,
Andy

Rhaphiel Molinar

June 18, 2026 15:34

Good Morning Andrew,

Thank you for the information, I had no idea this even existed. However, I did notice something that was a little concerning:

Given the current status of the software, with this being a pre-requisite, I could foresee issues with utilizing this in the future.

Additionally, I'm simply one of the support agents for one of the iterations of the Nx Witness platform. While I would like to be able to try this and share with of our customers, I lack the authority to implement its usage in any official way.

June 18, 2026 22:54

Hi Rhaphiel,

The latest Nx Powertoys uses the appropriate API and authentication method for old and new API. Digest Auth is not required to log into NxPT, Only a Local admin / Poweruser credential is required.

Soft Trigger actions (HTTP(s) Request actions in Nx v6.0 and below require Digest Auth to work. Soft Triggers take no action without it.

NxPT supports Bearer Token.
Soft Triggers created in Nx v6.1+ use the newer API call that does not use Digest auth.

Regards,

Andy.

Logical Rules/Rule Time Management/ Schedule Trigger Rule

Comments

Didn't find what you were looking for?