My ring devices showed up on my phone "setup" screen and I saw their address range was NOT in my subnet. So I set them for STATIC and put them into my subnet address range. This seemed to make them detectable. But the Ring setup said it couldn't connect to the "Internet". So I went back and reset the two devices (doorbell) & (ringer) to DHCP. Further attempts failed and I was just about ready to give up and I noticed that it probably wanted me to scan the QR code on the ring doorbell not the package. That did it! Setup proceeded pretty much as normal from that point. However because I host websites I have a pretty secure firewall/router and ports must be opened manually... not like the consumer grade stuff most people own. So I had to set both WAN>LAN and LAN>WAN ports open. Then everything got happy. The devices found the Internet and disappeared from my "setup" on the phone. Ring didn't do a very good job of install instruction for anything out of the ordinary. I use Linux so used nmap -Pn to search for the IP addresses I set up. All 1000 scanned ports on 192.xxx.xxx.241 are filtered. So security seems tight enough... Suggest you take a photo of the QR code on the back of the doorbell and back of the ring speaker plugin thing... and try again.. If you can't get it working see if those two items show up on your phone wifi setup screen... if so find out what your address range is and set them to static as mentioned above... you need to give them an address outside the DNCP range or it will always reset if power is lost...
... View more
I'm with you... The addresses given to the doorbell and ringer are 192.168.240.34 I saw that both had the same IP address. Not too sure of how they're going to connect to my subnet since I'm on a 192.168.15.0/24 network. And they used 192.168.240.1 for a DNS? How they get there I couldn't guess, unless the doorbell has network translation protocol. Nice idea they had here, poorly done unfortunately.
... View more