Update 3.0.1 Connection Issue

[ragboy]

I can say for me, I could not get it to connect using windows 10, even completely disabling the firewall. When I downgraded to 2.5.1 it works fine.

[x-Timmey-x]

Hey Ryan,

i have installed the 2.5.1 Version and the webserver is starting.
The remote access is working without any problems.

Best regards
Tim

[mlines]

Not sure if this issue is related but with 3.01 I am unable to view cameras live or clips from the web browser, however I can do both just fine from the IOS app. When attempting to connect live the page constantly refreshes with no video. When attempting to view clips it says the format is not supported. Anyone else having this issue when running from a mac?

[mlines]

Here's an interesting observation/update to my last post. The homepage of the webserver which shows all the live video images displays them all live just fine. It is only when I click on an individual camera that it goes into the loop an does not display anything.

[ragboy]

Has this issue been resolved in any way? I have paid for the upgrade and still can't use 3.0.1. 2.5.1 works fine, but 3.0.1 just hangs at "starting..." Firewall is OFF.

[WfromL]

Updated today to 3.0.2
Unfortunately my connection problems are still the same: connection to Panasonic WV-SW175 is fine, connection to Panasonic BB-HCM531 fails after 10-30 minutes.
Downgraded to 2.51 which works fine with both cameras.

[gordon861]

Well that answers the question I was about to ask.

Currently running the 14 day trial and things were looking good until the system started just dropping the camera at odd times. So I was going to ask if it was fixed but it would appear not. When it first happened I assumed it might be the camera due to it dropping the fps in the dark and the software showing a warning note, but now it's also happening at random times during daylight too.

I'm only using cheap 2MP no-name Ebay cameras in ONVIF mode but they still show on the local network as live even when Sighthound says they aren't there. But it looks like this software isn't the one I was looking for, I will just have to keep looking and monitor this thread and maybe try another trial in a few months.

[WfromL]

I wouldn't give up on the software, I've been using Sighthound for years without any issues. I think it's really the best value for money you can get (and I have no ties with the company .
The isssues with version 3.01 are unfortunate, but try at least the 2.51 version before looking elsewhere.

[gordon861]

Hmm just checked and it looks like I can download the 2.5.1 version even as a trial user, I will give it a go at the weekend as I still have 7 days left of the trial.
Thanks

[Semper Vaporo]

Well that answers the question I was about to ask.

Currently running the 14 day trial and things were looking good until the system started just dropping the camera at odd times. So I was going to ask if it was fixed but it would appear not. When it first happened I assumed it might be the camera due to it dropping the fps in the dark and the software showing a warning note, but now it's also happening at random times during daylight too.

I'm only using cheap 2MP no-name Ebay cameras in ONVIF mode but they still show on the local network as live even when Sighthound says they aren't there. But it looks like this software isn't the one I was looking for, I will just have to keep looking and monitor this thread and maybe try another trial in a few months.

When the camera disconnects, does it reconnect in a few seconds or do you have to manually tell SH to turn it off and back on? Or do you have to terminate SH and restart it? Or do you have to physically cycle power on the camera? If you cycle power on the camera, do you also have to restart it in SH or will it just reconnect automatically.

I have 2 netcams (TrendNET and D-Link brands) and both exhibit random disconnects for a second or two at various times during the day and night... no real cause is apparent (such as scene brightness or activity in the scene, nor caused by a busy CPU or disk) but they do seem to come in clusters where they will occur often for an hour or so, and then don't occur again for several hours. Most are so short that SH doesn't seem to mind but sometimes they seem to stop talking long enough for SH to go through the disconnect/re-connect sequence. One (the TrendNET) has a very regular, 355 second (5 minute and 55 seconds) disconnect that usually lasts long enough (about 5 seconds) for SH to show a loss of connection and then reinitiate the connection.

When watching these cameras using a browser or some other program I can see the disconnect occur, but it manifests as the scene just freezing for 1 to 5 or 6 seconds. The other types of programs don't care if the video connection fails, they just keep showing the last full frame they received and keep requesting another; whereas any "surveillance system" needs to let the operator know that the disconnect occurred instead of just ignoring it.

I have not been able to determine why these "loss of response" events occur, but they are not dependent on the computer or software (I have had SH on 3 different brands of PC and can see the problem occur with other video software). I think the problem is in the cameras themselves, but I cannot determine why it happens and don't know how to "fix it". I guess SH could have a longer time-out on loss of signal to mask the loss to us users, but I am not convinced that would be a good idea, either!

Put a clock with a sweep second-hand in the scene far enough away that the hand is not detected as motion, but close enough to be able to see it clearly on screen. The watch the scene both in SH and in another program and you will detect that the clock's second-hand will freeze in the video at random times on both windows.