V 5.0 Grid View problems

[willfly]

Upgrade to V 5.0 on mac mini went smoothly. New features and performance improvement is great.

However, the GRID view is not working as expected.

One specific camera will not connect with the GRID and shows a black space where the camera image should be. The original location for the problem camera is top left square in grid.

The black space moves with the camera location as set in GRID preferences. Changing row and column settings does not resolve. Changing other settings in GRID preferences has no affect on problem camera.

Separate issue: In GRID View, the cameras will indicate "Connecting", but never connect. Switching away from GRID view and back will resolve the Connecting issue, but not the missing camera issue.

I have tried to reconfigure cameras and reconnect. I've changed FPS and bit rate all without success.

All cameras appear normal in CAMERA view, and record according to rules.
Search mode functions as expected with all cameras.
All cameras connect as expected in iOS app.

5 cameras are same model, firmware and configuration
Ubiquiti G3 bullet
firmware 3.7.0
Standalone Mode
RTSP mode with force TCP
no RTSP authentication
30 FPS
6000 bps (other bps tried)

Mac mini
2.3 Ghz i7
16 GB RAM
macOS 10.12.5
4TB external USB drive for video location, 2.9GB free

[ryan]

Thanks for letting us know and for all of the details. To confirm a few things:

* It is always the same camera with a blank window, regardless of what order it is in the grid list? That is to say, it's not always the first camera in the list?
* That camera is displaying properly in the monitor view?
* Do you always see "connecting" on the first visit to the grid view after launching the UI and then never again? Or have you seen it return to this state again without closing the app? Or did you only see this once in general?

If possible can you submit a bug report from "Help->Report a Problem..." and include the name of the affected camera?

[willfly]

Ryan, thanks for the quick reply.

It is the same camera with blank window regardless of grid order. After further testing, the black square is replaced with a still frame from an adjacent camera grid square when moving the problem camera square. On one occasion, dragging the mouse and clicking over the problem camera BLACK square left a breadcrumb trail of white, cursor-sized boxes. Switching away from and back to GRID erased the white square anomaly, but did not solve the problem camera square.

The GRID problem camera displays properly in both monitor(CAMERAS) and SEARCH views. Rules execute properly.

I see "Connecting" when switching from monitor (CAMERAS) to GRID view. Most times, the cameras connect to each grid square (except the problem camera square). When they don't connect, I switch away from and back to GRID view.

I also discovered that using the mouse wheel will change the GRID view layout. This is a bit touchy. A small mouse wheel movement changes the GRID view layout quickly, too fast to be useful. Using the mouse to change the GRID view does not solve the problem camera square on the GRID.

I will attempt to submit a Report shortly. FYI, when I select "Check for updates" I get a message that the update server could not be reached. I am not running a 3rd party firewall. macOS firewall settings are default. The application CAN successfully show license information. I download the app manually to update.

[willfly]

Update:

Restarting the Sighthound application appears to resolve the GRID problem square/camera issue. HOWEVER, moving the camera location in the Sighthound Preferences, Grid settings, reintroduces the original problem. The problem camera shows "Connecting".

I successfully submitted a problem report from Help menu.

I have not rebooted the mac mini since app update.

[zxcslo]

Similar problem here. I have 6 cameras in the grid (3x2) and in this two days, some of them have 'frozen' a few times. Changing the view to Cameras and back to the grid doesn't solve the problem. Only Turn off Cameras, close the app and start the app again solves it.

[ryan]

Thanks to those who reported and helped test the fixes. We believe this issue has been resolved in version 5.0.1 which was posted today, if anyone experiences further trouble drop us a line.