Just got the new ADC Doorbell Camera set up, very excited! Install would have been dead simple except that I did not have an existing doorbell wire and chime so had to add them.
Doorbell Camera is up and running and works with chimes, push notifications, and two way audio. No video at all though - “A low connection has been detected. We will reconnect to” (SIC).
I would be the first to point the finger at the network, but it is practically on top of the wifi access point, and I did a speed test immediately afterward that clocked in at 17Mb down/11Mb up. I would be happy to pick at the network more but not sure what diagnostics are available. What are next steps? I know this is a new product for all so understand his will be a process
11Mb up is somewhat atypical for us, but we rarely drop below 6Mb; I’m pretty confident of the bandwidth. As an additional datapoint, I was able to log in to ADC and see the doorbell was reporting 100% wifi signal strength.
I’ve been researching in the meantime and since Skybell HD is a 2.4GHz only device, they suggest that when 5GHz wifi is available it might help to create a segregated 2.4GHz SSID. I’ve done this but am now having trouble switching SSIDs on the doorbell. I’ve removed it from my account and am trying to readd it, but the doorbell is stuck on solid yellow (which I think means booting). Currently researching on how to reset but any suggestions appreciated.
Ok, I was able to reboot by removing power to the doorbell, and was able to successfully re-add it using the dedicated 2.4GHz SSID. Unfortunately, same result. Tried having the iPhone on the same SSID as well, no difference. Will keep looking into it but that was my best idea so far. Firmware version is 1072 if that makes a difference.
We’re a little non standard in that regard. We have a Ubiquity Unifi AP AC Lite (https://www.ubnt.com/unifi/unifi-ap-ac-lite/) as a dedicated access point, and the router is a Netgear MBR1515. Wifi is disabled in the router.
Alright, go ahead and reconnect it to your network as you would normally and I’ll take a look at some of the diagnostics in the back-end. I’m wondering if you might have ports being blocked.
I tried just now, but it won’t pick up the SSID from the router
On the third try I DID get it to connect to the Netgear 2.4GHz SSID. Unfortunately, same result. I guess the good news is we can rule out the Ubiquity being the problem.
I will see if I can put the doorbell in the DMZ and report back.
Enabling DMZ seemed to make it stop working completely. Now I’ve never used DMZ on this router, and if it were working properly DMZ shouldn’t make it stop working, so it seems like something’s not right there. If we can figure out any specific ports to forward I’m happy to try that.
For now it is back to “normal” state, two way audio but no video - hoping you might see something on the backend. Thanks!
After I disabled DMZ and wifi on the router, which required a reboot of the router, the doorbell would no longer connect. On rebooting the doorbell it went back into setup mode and I had to re-add it. No big deal unless I have to re-add the doorbell overtime the router bounces. It is back in the “audio but no video” mode now.
Strangely the wireless link quality was indeed showing as poor earlier, but it looks like it is reporting high now. Can you try the bell now and let us know?
I am guessing it was reporting low when I was testing on the direct router wifi (as opposed to the access point). Right now it’s reporting 97% and still exhibiting the same behavior.
By default, when the doorbell button is pressed a recording of the event will be saved and can be viewed under the saved clips page. Do you see any clips saved?
I’m wondering if an issue with the feed connecting to your mobile device might be at play. Have you tested from a different device?
Thanks Jason. No saved clips are showing up in the account. In additional to record on ring, I also turned on record on motion, but no clips either way.
We could try port forwarding to see if that allows video to be shown.
Standard ports that are needed are 80, 21, 123. Then 40925 and 41925. My guess is it would be the last two causing the issue if this was the problem. If you forward those to the Doorbell IP, any change?
Just wanted to add that I did have this exact problem on a Skybell I set up from a while ago. They kept saying it was my wifi connection (even though my own network logs indicated otherwise.) They finally gave in when they asked me to move it closer. I moved my router outdoors and it was still an issue. They sent me a replacement unit and it finally worked.
Might be the case of a bad unit. Now that was a Skybell 2.0 I had. Switched over to Ring as I had more customer service issues with them. But I might switch back since the alarm.com integration is with Skybell.
