NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Installing Apps/Devices that cannot connect on 5g when trying to use Orbi and Pixel Phones
Scenario: 1. Orbi Mesh network installed where we cannot manually differentiate (i.e., name SSID separately our 2g and 5g) network bands because the mesh supposedly handles this in the background...
TButcher wrote:Scenario:
1. Orbi Mesh network installed where we cannot manually differentiate (i.e., name SSID separately our 2g and 5g) network bands because the mesh supposedly handles this in the background.
2. Google Pixel Phones where you cannot switch off of 5g networks if one is around manually either because it ALSO does this for you wanting to find the best/fastest network.
3. The issue: Now you are trying to install an app/device that can ONLY "see" a 2g network band. Think, Amazon Alexas, Ring doorbells, and the like. So, your pixel can't find their "temporary" network because, of course, it's on your 5g band. You can't go into the Orbi and set anything up or disable the 5g band to force it to connect to 2g because, of course, that ability is also removed from you.
4. So, what to do? This is the issue many people are having I'm seeing. I'm about to actually scrap this network and go back to a "normal" router and hope that it covers my house. One that allows me to "see" separate bands and, therefore, connect apps that can only "see" 2g. Because I'm not getting rid of Pixel and Google WiFi just yet. Saves me too much money each month.
Anyone found a way around this yet?
There are a number of posts specifically about Ring Doorbells. What has worked for me with a number of devices that work only on 2.4G (Sonos One, variety of smart plugs) is this:
First, "give it a try". The majority of these devices get configured by broadcasting their own WiFi access point with an obvious name (SSID). The app or the user opens the smartphone WiFi manager and this goofy access point is connected to. Enter the Orbi WiFi SSID/password into the app. App sends them to the device. Device connects. Done.
Second, "shut off 5G broadcast". Unfortunately, some apps were written ineptly and simply won't work if the smartphone is connected to a 5G network. Go to the Orbi web interface, the Advanced Tab, Advanced Setup, Wireless Settings and uncheck the box "Enable SSID Broadcast " on the 5G network. On the smartphone wireless settings, "forget" the Orbi SSID. Then, in the settings, search for a WiFi network, "find" the Orbi, enter the password and connect. Check on the Orbi "Attached Devices" that the phone is connected at 2.4G (The Orbi is slow to update device connections. I concluded "it didn't work!", when I simply had not waited for the Orbi to update the display.) Open the device setup app. Do the setup. When the device is working, go back and check the box "Enable SSID Broadcast" for 5G.
These two steps have worked reliably for me (and a lot of other people). Most of the time, ignoring the warnings "MUST HAVE 2.4G" and clicking "Continue" just works.
If there is a specific device which cannot be connected to Orbi, please describe it.
<<First, "give it a try". The majority of these devices get configured by broadcasting their own WiFi access point with an obvious name (SSID). The app or the user opens the smartphone WiFi manager and this goofy access point is connected to. Enter the Orbi WiFi SSID/password into the app. App sends them to the device. Device connects. Done.>>
Yes, this is often the case. The trouble is, it will not stay connect to this "device specific" WiFi access point. If I try to give it my Orbi WiFi SSID/password, it tells me the password is incorrect (even though I know I have not changed it).
I have not tried your second solution, however. I will try that when I get home. I'm on work travel until tomorrow and will do so (disabling the 5 to force everyone to 2).
The strange thing to me is some devices seemingly of the same "genre" will connect and some will not; case in point, some Amazon echos. Perhaps it is a generation thing.
TButcher wrote:Yes, this is often the case. The trouble is, it will not stay connect to this "device specific" WiFi access point. If I try to give it my Orbi WiFi SSID/password, it tells me the password is incorrect (even though I know I have not changed it).
I have not tried your second solution, however. I will try that when I get home. I'm on work travel until tomorrow and will do so (disabling the 5 to force everyone to 2). I should clarify. Telling Orbi to stop broadcasting SSID will not affect any device that is connected at 5G. That is why the phone has to be told specifically to "forget" the Orbi SSID and then search again for WiFi. The phone will connect to the only access point that is broadcasting SSID: the 2.4G one. Once the Orbi begins broadcasting SSID on 5G again, the phone will switch when it decides the 5G connection is better.
The strange thing to me is some devices seemingly of the same "genre" will connect and some will not; case in point, some Amazon echos. Perhaps it is a generation thing. It would be helpful to identify specific devices which are difficult to connect. If it meets my criterion (under $25), I usually purchase one to see what happens on my Orbi. Otherwise, some people who watch the forum have experience with many (many) devices.
TButcher wrote:
I have not tried your second solution, however. I will try that when I get home. I'm on work travel until tomorrow and will do so (disabling the 5 to force everyone to 2).
This tactic, disabling the broadcast of the 5 GHz SSID, seems to work in most cases. Indeed, I can't recall any instances where it failed. Maybe I wasn't paying enough attention.
It is surprising how many people insist that it is impossible to set up IoT gadgets without separating 2.4 GHz and 5 Ghz. They bang on without even bothering to try this well known strategy for getting things to work.
So they turn up here with complicated scenarios that have nothing to do with the real world. The pity is that Netgear has failed to come up with a KnowledgeBase article that explains what to do.
Oh, and if anyone does encounter a reluctant device, tell the people who made the IoT device that they need to get their act together: also tell people here so that plemans can buy some new toys. Netgear is not the only maker of Mesh stuff and Orbis are not the only Netgear devices that combine SSIDs.
Finally, when trying anew device, search this community for it. You might be surprised to learn that it has already cropped up here, along with advice on how to get it to work.
I can confirm the disabling of the 5G SSID broadcast is still working on v2.5.1.8. I watched a wifi analyzer as I disabled it and the SSID name and signal dropped then after a few seconds the signal came back, however the SSID was not displayed over the signal. Once I re-enabled the 5G SSID name broadcast, the signal disappeared then came back and also the SSID Name was displayed over the signal.
TButcher wrote:<<First, "give it a try". The majority of these devices get configured by broadcasting their own WiFi access point with an obvious name (SSID). The app or the user opens the smartphone WiFi manager and this goofy access point is connected to. Enter the Orbi WiFi SSID/password into the app. App sends them to the device. Device connects. Done.>>
Yes, this is often the case. The trouble is, it will not stay connect to this "device specific" WiFi access point. If I try to give it my Orbi WiFi SSID/password, it tells me the password is incorrect (even though I know I have not changed it).
That's not the process CrimpOn has described above. The temporary AP is done on the IoT (sometimes it's also a Bluetooth connection), the SSID is taken from the or selected from a list, the security key is typed in or again taken from the mobile wireless config - everything is pushed to the IoT which is supposed to connect to that network. Of course, the IoT AP is no longer active after that (except it does come back if it can't connect to the "real" wireless network. Here again, if the IoJ stuff does not associate with the access point, it's unlikely a problem with a 802.11n/802.11ac system like these Orbi.
There can be some specific interoperability issues when it comes to the Wi-Fi 6 system like the Orbi AX because of some added protocol features - however the majority of these proofed to be again WiFi client issues.
The worst IoT stuff are these "designs" which will only connect to a certain SSID (or ESSID) if the BSSID (the radio MAC) is the same - there all tricks won't help much.
