NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Anyone using Ring Doorbell Pro and Spotlight cams with Orbi RBK50?
I'm considering buying an Orbi RBK50 (AC3000 tri-band) for use w my Ring video doorbell pro and spotlight cams. I see people having issues with the Ring devices trying to connect to the wrong ban...
alokeprasad wrote:I'm considering buying an Orbi RBK50 (AC3000 tri-band) for use w my Ring video doorbell pro and spotlight cams.
I see people having issues with the Ring devices trying to connect to the wrong band (5 GHz instead of 2.4 GHz) and failing.
Is anyone here using Ring devices with the Orbi system? People post all the time about success with Ring products, which makes the situation hard to understand. The people who post about problems are not imagining them.
Any tips/tricks in doing that successfully? I searched here and found old posts describing using Telnet and changing Orbi settings. Is that needed with the latest Orbi firmware? Splitting 2.4G and 5G bands should not be necessary. Plug, the newest RIng doorbells support both 2.4G and 5G bands.
Ideally, no tricks would be needed and the Orbi would automatically use the 2.4 Ghz bands w the Ring devices. Does it?
The issue is not Orbi "using" bands. There seem to be two common problems (1) completing the device set up, and (2) opening a camera for "Live View".
You are entirely right to be aprehensive.
Thx. for the reply. My Ring devices don't support 5Ghz.:smileysad:
I'm hoping for some success stories with Ring and Orbi. I have been using Netgear routers, unmanaged switches, and even old ReadyNAS (from Infrant days) for decades. So I can set these up and update the firmwares etc.
Has anyone done that recently? Did the Ring devices connect and function? Did they stay connected?
If not, how did you make things work?
IMO, Netgear should have a "advanced" setting that allows users to assign the frequencies to select devices that are finicky about connections. But I cannot depend on that happening.
A Fix: https://community.netgear.com/t5/Orbi/Best-Performance-for-Ring-Devices-Orbi-Config-Settings/m-p/1768448#M64620
https://community.netgear.com/t5/Orbi/Need-some-help-with-Orbi-and-Ring-Doorbell-2/m-p/1671059/highlight/false#M46565
https://community.netgear.com/t5/Orbi/Ring-Doorbell-2-and-Orbi/m-p/1685149/highlight/true#M49058
https://community.netgear.com/t5/Orbi/Orbi-and-Ring-products-issues/m-p/1709487/highlight/true#M52996Thanks. Good post to bookmark for use, if needed.
The posts are 1-2 years old. I was hoping that newer firmwares (on Orbi and Ring) would have addressed the problems.
Hoping to hear from people using these devices currently, and if they need to set the parameters as decribed in your links.
Aloke
alokeprasad wrote:Thx. for the reply. My Ring devices don't support 5Ghz.:smileysad:
...
IMO, Netgear should have a "advanced" setting that allows users to assign the frequencies to select devices that are finicky about connections. But I cannot depend on that happening.
Where ever you expect a 2.4 GHz client to connect to...
It's 100% on the client to which SSID (as configured), to which BSSID (so which radio and satellite), does connect to. Anything else (leaving alone that the existence of 5 GHz BSSIDs are irrelevant for a 2.4 GHz client) is of the control of the Orbi system anyway...
Praying the Ring WiFi clients are Mesh aware, so they can - wonder of technologies - dynamically and seamlessly change to a better BSSID does show up on air offering a better connectivity for the same SSID, e.g. because you install an additional satellite.
A wireless client needs connectivity - not a hard coded connection. This is what Mesh systems are made for.
There is a lot of false information around also here in the community... this does lead to ugly (sorry) questions like yours.
Maybe the Orbi could use 3 SSID's: "Orbi 2.4" for 2.4 GHz and "Orbi 5" for 5 GHz for fixed and finicky clients (like the R9000 does) and "Orbi" for mesh-aware roaming clients that can switch to the strongest frequencies at their location.
Not sure if this is technically possible, but it would make it easier to use older and ill-behaved client devices with mesh routers.
