22-02-2022 09:54 PM
Hi All,
I am having a nightmare trying to connect my ring doorbell (2nd gen) to my new ee mobile broadband home 3 router.
I’ve been on the phone to both ee and ring and unsurprisingly both have tried passing the buck on to one another….
Anyhow…
i have tried everything!
- 2.4ghz connection
-staying off channel 12-13
-no special cases on my SSID
-guest network
-lowered all my content restrictions
and probably a whole lot more through a hardcore Google search.
it did connect for 24 hours after about an hour of trying to connect but the next day it kicked me off and hasn’t let me back on since.
I’ve been looking at setting up static ip addresses and port forwarding however I’m not 100% sure how to do this correctly but it does sound like the router is blocking it somehow and I need to change a setting somewhere.
Anyone else had this problem and solved it?
I’ve also connected the doorbell to my main home wifi (on now tv) and it connected straight up so it’s definitely not a faulty doorbell
if anyone is able to walk me through port setting etc it would be hugely appreciated!
Thanks!
Solved! See the answer below or view the solution in context.
23-02-2022 08:16 AM
@Jon_K When I first got it out of the box it took about an hour to connect to my mobile broadband router and I think I achieved this by switching channels (or it was a pure coincidence)
however now it won’t connect at all. The ring doorbell connects with my phone during set up but after I try connect it to wifi which is the next step it fails to connect and a white light flashes on the left side of the doorbell light saying set up failed. I can’t get any further than this on my ee mobile broadband router.
when I take the doorbell home it connect up with it seconds to my home broadband (now tv) so I know it’s not the doorbell.
I read something about public ip addresses and security cameras but I’m not that knowledgeable do you have any insight to this that could be the cause?
23-02-2022 08:30 AM
Hi @Caseyt59.
Have you tried changing the channels again?
Do you need it to be connected to both your home broadband and mobile broadband?
Jon
23-02-2022 08:33 AM
@Jon_K yes I’ve tried every channel about 20 times now.
honestly think it is something a bit more technical than the usual stuff to try I have exhausted every option aside from the port forwarding/public IP address stuff as I’m not fully up to speed on it.
is there anyone on the ee team who could help with this or has experience?
seems like there’s been a few issues reported on here but nobody has managed to solve it?
23-02-2022 08:36 AM
Thanks @Caseyt59.
I think the best thing to do in this case would be to call and speak with our Tech Gurus.
They are our advanced technical team and will be able to try additional troubleshooting steps with you.
If they're unable to resolve this on a call, they will raise an investigation ticket to look into the problem further.
Jon
23-02-2022 10:55 AM
Ring Doorbells don't require any port forwarding. They aren't running any servers.
23-02-2022 11:18 AM
@XRaySpeX thanks I think I did read this response from you previously.
I’ve been on the phone to both ee and ring today. 100% a connection issue and an tech guru said via the service representative that basically you’re lucky if you get a connection because the IP address on the doorbell can be taken by another devices and it may be months or years before it switches back does any of that make any sense?
is there any work around setting static ip addresses etc?
Thanks!
Casey
23-02-2022 11:56 AM
Not really, for consumers as the network sets the DHCP time out, and not the device.
You could look at an ISP such as AAISP who provide sims with a Static IP, or set up your broadband and use a dynamic DNS service, and use a host name rather than an IP
23-02-2022 12:19 PM - edited 23-02-2022 12:19 PM
@MozzaSec Thank you!
are you able to offer some support in doing this please?
or point me in the right direction 🙂
23-02-2022 12:40 PM
That technician is talking a load of codswallop. You don't need a public static IP, which EE doesn't do anyway. He's mixing up public IPs and your internal private LAN IP which you can fix in the DHCP.
23-02-2022 01:47 PM
Have to agree, it does sound like a load of rubbish from the EE Tech..
Internal DHCP / DNS you manage via your internal setup
EE DHCP/DNS you dont manage, and also EE networks will do something called (g)NAT.
If the EE router is giving an internal IP (i.e 10.1.1.1) and the device is seen by the router, then it should be able to talk out via the gateway aka the router.
Can you ping the doorbell internally?