When viewing a camera or multiple cameras in Focus View in the mobile app and you go to exit the view you will get a White X that will not go away. You have to close the app to get this to correct it’s self.
When this happens, the logs are showing an uncaught exception because the camera doesn’t support digital PTZ.
Update Exacq Mobile 3 to version 21.09 and if they can not there is a work around.
Work Around
Enable the PTZ on the client- under the cameras. This was confirmed as work around. If it is disabled then “Enable” checkbox should be checked.
Release notes: 10/04/2021 v21.09.0 * Bug Fix – Fixed focus view not exiting on some cameras
If you use the same video input, one with digital PTZ enable and zoomed in and the other with Digital PTZ disabled, the saved view will not display as intended when searching that view on the Search Cameras page.
A useful feature of exacqVision Client is to automatically switch to a view that highlights an event in progress. This can be configured two slightly different ways in exacqVision Client:
If you want the view to change to an event and stay on that event until the operator acknowledges it, or if you want the client to stay on that event for a specific number of seconds, configure Event Monitoring using a default view and the Event Monitoring List.
If you want the view to change to an event and stay on that event until the event ends, and if all cameras are on the same server, configure Event Monitoring using Source Groups. (NOTE: All cameras must be on the same server for this type of automation because it depends on a Source Group event that runs on the server.)
<br>
Configuration Steps
Each of these methods are explained in the following sections.
Configuring Event Monitoring using a Default View and the Event Monitoring List
Save the view that you want to display by default when no event is triggering.
Save each view that you want to display full screen when a trigger is activated.
Create a new Event Monitoring profile.
Give the Profile a name.
Select Show Event Monitor List.
Change the type to View.
Set first Client Action to Event Type Default.
Set Action Type to Switch View.
Set Action Target to your default view.
Click Apply.
11. Click New to add a Client Action.
12. Select your Event Type.
13. Select your Event Source.
14. Set Action Type to Switch View.
15. Select the associated view to display when this trigger is activated.
16. Deselect Confirm and select a timeout period if you want the view to persist for a specific period of time. Alternatively, select Confirm if you want to force the operator to acknowledge the event before returning to the default view.
17. Repeat steps 11-16 for each trigger/view combination.
18. Click Apply.
19. On the Live page, click Views.
20. Double-click the new Event Monitor.
Now your Default view is displayed until a trigger is activated; at this time, the trigger’s associated view is displayed. You can resize and move the Event Monitor List if desired.
<br>
Configuring Event Monitoring using a Source Group
In the Live view, save the view that you want to display by default when no event is triggering.
Save each view that you want to display when a trigger is activated.
Create a new Event Monitoring profile.
Give the Profile a name.
Change the type to View.
Create client actions for each event:
Select an Event Type.
Select an Event Source.
Set Action Type as Switch View.
Select the associated view to display when this trigger is activated.
Select New and repeat these steps for each trigger/view combination.
Create the client action for the default view:
On the Event Monitoring page, select New and select Source Group as the Event Type.
Select the server that contains all the cameras and views in the system drop-down list.
Click New.
Name the group.
Click New and select the appropriate event type.
Select one of the cameras associated with the event.
Select When Not Alarmed.
Repeat these steps for each camera associated with an event.
Click OK to finish creating the Source Group.
Click Switch View as the Action Type.
Select the default view created previously.
Click Apply.
NOTE: There is a known issue with using Source Groups in Event Monitoring. For the Source Group to function, an Event Linking action using the same Source Group must be created on the server. See this article for additional information.
On the Live page, click Views.
Double-click the new Event Monitoring profile created previously.
Now your Default view is displayed until a trigger is activated; at that time, the trigger’s associated view is displayed until it ends or another event starts. The Event Monitoring list is not required to be open.
NOTE: When the initial view loads, no camera is displayed until the first event occurs. Then the view will switch to the event and then back to the default view.
Views and Groups are stored on the the relevant ExacqVision servers. For example, if you create a view named “East Side Entrances” that has Camera A from Server 1 and Camera B from Server 2, the group ID and name are stored on both Server 1 and Server 2. Also, Camera A’s membership in “East Side Entrances” is stored on Server 1 and Camera B’s membership in “East Side Entrances” is stored on Server 2.
Thus, if the integrator connects his Client at home to Server 1, he sees a group named “East Side Entrances” containing Camera A without any need for configuration or file transfer. If he then connects to Server 2, Camera B is also seen in “East Side Entrances”.
Views and Groups are similar in that both of them are logical groups cameras based on more than just the server they are connected to. The major difference is that a View also defines a layout of the cameras onscreen. Because it specifies a layout, the maximum number of cameras in a View is limited to the maximum number of cameras that can be shown onscreen at once, whereas a Group does not have that restriction.