Remote site camera used to connect but now won't

[Brandon Brown]

Hi all,

I have a remote camera about 1000 yards from my house connected via Ubiquiti Nanobeams.  The connection works pretty well - reliably gets about 10-15mbs at the remote location, enough that the Amcrest app streams the camera reliably on demand.

Camect had no problem locating the camera, and reliably recorded/monitored it for a couple weeks.  At some point, the IP address of the camera changed - so I gave it a fixed IP and reconnect to Camect, and it worked great again.

Since then, I've had an odd issue:

1) The camera shows "connection dropped."

2) Camect detects a new camera at the same IP address, and says that also has "connection dropped."

3) Once or twice I've been able to fix this by enabling/disabling the "new" camera, which somehow has caused the OG camera in Camect to start working again.

4) Now I can't seem to get the camera connected at all via Camect - it stays with "connection dropped" or "unable to connect", despite the camera streaming fine on the Amcrest app.  

I realize the remote link will have some intermittent connectivity issues at times, but  Camect was able to reliably handle that for weeks.  Any ideas?

[Arup Mukherjee]

Have you tried rebooting the camera? 

If it's happening all the time, please try the RTSP url using VLC and see if that works. (The Amcrest app does not use RTSP, so having it stream is not a reliable indication that RTSP on the camera is fine.) 

If VLC also works fine, please use "Report Bug" from the hub settings of your hub to describe the situation and specify which camera is having the problem. 

[Brandon Brown]

VLC works.  

Here's a clarification on what's happening:  1) the camera feed goes down, says it can't connect.  2) when that happens, camect detects a "new" camera at the same IP address and creates a new camera in the hub; 3) when I disable the original camera, and insert the right credenatials into the "new" one, the "new" one starts working and the old one doesn't.

At first I thought this was an issue with the camera's IP address changing; but I've got it assigned a permanent IP now and it appears to still be using it.  

Biggest frustration with this is that this particular camera is being shared by my rural neighbors for security (it's looking at a shared private road gate) and I have to keep going in to user settings to assign them access to the "new" camera each time.

Sending the report bug in.  

Thanks as always, Arup.