The Scenario Series of videos addresses setup configurations for specific use cases.
In this video our scenario is that of a car dealership that wants to play an audible alert to people on the property after hours, as well as send a notification to staff members.
We walk through setting up AI Object Classification on three different cameras from Illustra IQ, Axis, and Hanwha, then show how to configure Event Linking different ways and two different methods for scheduling the action to occur.
Chapters
00:00 Intro & Review of Scenario
00:56 Axis C1310 Setup
02:32 Camera Configuration
02:59 Illustra
04:28 Axis
05:46 Hanwha
07:01 Event Linking
09:43 Notifications
10:46 Scheduling
14:16 Wrap-up
Unleash the power of webhooks using your ExacqVision software to control IoT devices, smart building controls, and more. ExacqVision allows users to implement soft triggers, camera associations, and automate issuing webhook commands on triggered events.
<br>
Axis P3247-LVE “Axis Object Analytics” not passing through the Exacq Mobile 3 app Analytic Rules. If seen please see AES-609. Escalate the case to be added to ticket.
Product
exacqVision Server: 23.06.1.0
exacqVision Web Service: 23.06.2.0
Steps to Reproduce
Set up the camera to allow analytics. Note we do not support line cross for axis cameras.
Once camera is set up navigate to the mobile app and connect to the NVR.
Once Connected navigate to the main menu.
Select Push Notifications
Select Analytics
You should see any analytic that cameras are sending.
Expected Results
We should be able to see the Analytics from the Axis cameras.
Actual Results
Analytics do not show up in the mobile app but do on the NVR’s Server when creating event linking and on the camera settings page.
The port drop down box will not allow you to change the port from SSL Port 465 to StartTLS Port 587. If selecting the StartTLS the port will not change to Port 587 which StartTLS uses.
Product
exacqVision Client 23.03.0.0
Steps to Reproduce
When setting up an Email profile in the Email notification the client will get stuck on SSL/TLS when trying to select STARTTLS on new setup. The behavior seen by selecting StartTLS is the port does not change the port number to Port 587 but instead lists Port 465.
Set up new email Server Configuration.
In Example above I added the Description of test, an address, and selected the Security drop down of StartTLS which was stuck at Port 465.
As seen, the port remains on 465 and should be port 587.
Expected Results
The port drop down menu should be able to select any of the three option we offer. Default port is 25, SSL/TLS port is 465, and StartTLS is port 587.
Actual Results
StartTLS option never selects Port 587.
Solution
This has been resolved update to exacqVision Client version 23.03.1.0 or higher.
Event Linking Time Triggers using custom days of the week are activating on the wrong day. They are triggering 1 day earlier so events set for Saturday are triggering on Friday and so on.
Tested Version
exacqVision Server 22.12 – 22.03
Steps To Reproduce
Create a new Event Linking action
Set Event Type to Time Trigger
Under Event Source select New
Configure a time trigger
Give the trigger a name
Select a Start Time and End Time
Set Frequency to Custom
Select the current day of the week
Set Action Target to Notify
Expected Results
On the day and time specified in the Time Trigger
Event Links Status switches from off to on
An email is sent
Actual Results
Event links status stays off
An email is not received
Solution
Downgrade to exacqVision Server version 22.09
NOTE: Fix will be available in exacqVision Server version 23.06
Event Linking gives you the power to create automated actions based on your selected events. Sending email notifications when motion is detected, activate an alarm output when an input trigger is detected, automatically export a video clip when a button connected to an input is pressed, turn a PTZ camera to a preset point if motion is detect on another camera, and much more… a wide variety of combinations can be achieved.
You can configure an ExacqVision system to use Gmail SMTP Server to send an e-mail notification when an event occurs.
Product
ExacqVision Desktop Client
Solution
Google has announced starting May 30, 2022, They will no longer support the use of third-party apps or devices which ask you to sign in to your Google Account using only your username and password i.e “Less secure apps”. See the full statement at https://support.google.com/accounts/answer/6010255?hl=en
As a result you will need to enable Two-Factor Authentication and use an App Password instead. An App Password is a 16-digit passcode that gives an app or device permission to access your Google Account. App Passwords can only be used with accounts that have 2-Step Verification turned on.
In the ExacqVison Client navigate to the E-mail Message Profile tab (Configuration > YOURSERVER > Notification) and enter the following information selecting Apply when completed.
Profile Description: Enter a brief description of the email’s content From: Enter the email address of the person sending the email NOTE: The From address MUST match the Username used for the E-Mail Server To: Enter the email addresses of the recipient Subject: Enter a subject for the email Message: Type the email message
Test the Profile
Highlight the profile and click Test Profile
A popup window will appear, click OK when ready to proceed
Watch the profiles status, it will change from the initial “Awaiting Test Status”
To either Success (Date/Time) or Failure (Date/Time)
Troubleshooting notification e-mail server configuration settings when e-mail message profile tests fail.
Product
ExacqVision Client
Solution
If the profile test fails, review the exacqVision Verbose System Logs (Configuration > YOURSERVER > Systems Logs tab) for information about the cause. Pro Tip: Filter the displayed search results for entries relevant to notifications by typing “notifypi” in the filter box.
Here are some common causes including coresponding log entries.
Invalid E-mail Server Password
Invalid E-mail Server Username
Invalid E-mail Server Port
Invalid E-mail Server Security Type – STARTTLS
Invalid E-mail Server Security Type – Default
Invalid E-mail Server Outgoing Mail Server (SMTP) Address
If email notifications are not being received as expected check the Rule for any time-based restrictions such as “lasts for at least” or “lasted for at least”. Then verify the triggering event actually was activated for the specified amount of time.
For example, say we are using the following rule: If “Camera disconnected” lasts for at least, 300 seconds IN any group ON any server FOR any camera send email immediately to johndoe@email.com.
We can observe the camera drop in live view, but a notification is not received. By looking at the exacqVision Server logs we find the following sequence of events
2021-06-26 16:55:51 (GMT-0700) SamsungPI Warning ELEVATOR LOBBY: stream timeout.
2021-06-26 16:55:51 (GMT-0700) SamsungPI Verbose ELEVATOR LOBBY Context 0 is NOT connected.
2021-06-26 16:56:57 (GMT-0700) SamsungPI Verbose ELEVATOR LOBBY Context 0 is connected.
In this case, a notification WOULD NOT have been sent because the camera reconnected within 300 seconds. This would be true if any of the time related restrictions were used with a 300 second setting.
If a notification is desired for future events of this type the duration of the event i.e., 300 seconds would need to be lowered, or the time element could be removed and one of the following used instead “starts”, “stops” or “starts or stops”.
