NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
How to connect 2.4GHZ Devices
I just bought few smart plugs. But they only connect to 2.4 Ghz. How do i add them to my home network as they will not show up in App on my phone for a setup. I have a good coverage in my house so mo...
Kcobra1 wrote:I just bought few smart plugs. But they only connect to 2.4 Ghz. How do i add them to my home network as they will not show up in App on my phone for a setup. I have a good coverage in my house so most of the time phone is on 5Ghz.
While the smartphone apps for many (most?) Internet of Things (IoT) devices are able to deal with "mesh" WiFi networks, there are some which are poorly written and simply fail to work when the smartphone is connected at 5G. What has worked for many people (including me) is this:
- Access the Orbi web interface (http://orbilogin.net) using the admin credentials user "admin" and the Orbi router password (not the WiFi password)
- Navigate to the Advanced Tab, Advanced Settings, Wireless Settings
- Uncheck the box "Broadcast SSID on 5G Channel"
This will not affect any devices which are currently attached to the Orbi at 5G. - On the smartphone settings, "forget" the Orbi WiFi
- Search for WiFi networks and select the Orbi WiFi
- Enter the WiF password and connect
- At this point, open the IoT app and go through the steps
- After the device is connected, reverse the steps
Check the box "Broadcast SSID"
"Forget Orbi WiFi"
Search for and connect.
This sounds like a lot of work, but doesn't take very long.
p.s. "Poorly written" may seem harsh, but GEEZ. My TP-Link, Belkin, Eufy, Teckin (and other) smart plugs connected immediately. I have only had one that required the above steps. For one plug, I simply ignored the warnings "MUST connect to w.4G" and kept hitting "Continue" until it worked. "TAKE THAT!", I said.
bad_guy wrote:
What kind of phone do you have, and if iPhone, is it less than 2 years old?
If you have an iPhone 11 or earlier, there is no solution, other than replacing your Orbi system with the pro version. The consumer Orbi can't separate the 2.4 and 5.0 bands, unless you have the 960 series.
This is misguided and erroneous. Many many people have successfully installed their IoT things with new iPhones. Unfortunately, Apple does seem to like to make things difficult, with measures like "random macs", but careful attention to detail get around that.
There is no need for separate SSIDs for 2.4 GHz and 5 GHz.
How to go about this has been explained here many times and depends on the end users circumstances as well as the devices involved.
Those devices are at the heart of the problem. Too many of them come from makers who just don't know what they are doing.
A good way to look for help is to search this place fr the model of the device you want to set up.
So the choices are:
1. get a new phone
2. upgrade your consumer-version Orbi to top of the line 960 series (a LOT more money)
3. trade your consumer Orbi for a pro version which has more features and controls (e.g. SXK80 - AX6000)
That is rubbish and is best ignored by anyone who wants to setup their IoT devices.
Sorry, but you are incorrect. It is neither misguided nor erroneous.
The solution given does not apply to everyone, and does critically depend on which versions of Orbi and iPhone you have as well as the brands of 'smart' devices you have. (I don't know enough about Android to say anything about that.)
I did just have to replace my garage door opener, and the new model pairs with my phone and network via wifi, and though it says that it doesn't support a 5G connection, it had no trouble connecting. However, pre-existing locks, video doorbells and lights cannot. New iPhones (12 or later) can be set as described, but a still relatively new iPhone 11 cannot. If you have a very old iPhone, and it has Hotspot functionality, then it might work.
Many people will find one of these workarounds works, but many will not, and I, probably like most people that arrive here, simply can't afford to replace everything that I spent a lot of money for because Orbi made bad design decisions.
You also conveniently ignore my update to this post which provides more detail and qualifies the answer.
As well, everything I've said has been verified by Netgear engineers. If you have the wrong gear, it can't be done without spending a ton replacing your stuff. There is not a universal solution to this problem, and we shouldn't be letting Netgear off the hook for taking away functionality that people need, and only adding it back to their most (extraordinarily) expensive consumer products.
bad_guy wrote:
Sorry, but you are incorrect. It is neither misguided nor erroneous.
You are free to believe what you like. My worry is that people will read your messages and take them as the gospel truth.
I know that you are beyond convincing, my reply was intended as a health warning for other people.
They have been warned.
There is no need to be offensive, and it's not about "what I believe".
I have said just the opposite to what you imply. There is no gospel truth, no one size fits all solution. It depends on the combination of things that you have, or what you can afford to do about the problem. For some people, this can be made to work. For others, it doesn't (unless you can afford to replace all the miscreant 'smart devices', or get a new iPhone, or change the Orbi system you are using).
The important thing, rather than being prescriptive, is that people understand why the problem exists, and what to try. I pay for Pro Support from Netgear, and have spent many hours on the phone with a number of different engineers, and have tried all of these things. At the end of it, they advise that there is no solution if you have certain combinations of equipment, other than to replace it.
So, it's not me that needs convincing. I suggest that if you feel differently, you talk to Netgear support team and engineers. They will tell you that this problem is the reason functionality was added back to the 960 series (top end consumer Orbi, 6E support) that was taken out of the models below that.
Orbi AC systems was not designed or intended to have the options to separate SSIDs. During this early phase, IoT mfrs were up and coming and starting to be present on the market. However, these IoT mfrs are mostly responsible for how there devices interact with Smart Connect featured systems with 1 SSID that connects both 2.4 and 5Ghz signals into one SSID broadcast. This feature started back in 2012. Also the fact that both frequencies are on the SAME network. Where the problem is, is that the IoT mfrs don't understand or fail to implement both frequency networks with in the setup software for there device when installed on a dual band supporting mobile phone or pad. And not maybe realizing that most of these devices prefer the 5Ghz signal over 2.4Ghz. The problem is that there setup software is designed only on the 2.4Ghz in mind and thus the software only looks for the 2.4Ghz signal. if these IoT mfrs would support BOTH frequencies with in there setup software and allow the software and mobile device to be supported on ether frequency since they are on the same network system, would no longer have problems with setting up new IoT devices on Smart Connect featured router systems. You don't need a 9 series Orbi.
I recently ran into this as well. Two new smart bulbs I bought. Would not connect with my Android pad to my Smart Connect enabled router at the time. I had to disable it to get the IoT connected. Now for Orbi, we can't do that. So couple of suggestions are available that will help users that don't have a 9 series system and you don't have to buy or change out anything.
1. Turn off all RBS and change the RBRs 5Ghz transmit power to 25% leaving the 2.4Ghz power at 100%. Walk the setup mobile device out away from the RBR to ensure the device gets connected to the 2.4Ghz radio signal. May need to disable and re-enabled the radio on the device a couple of times. After it connects, should allow the setup process to begin and then be completed. After all is setup, revert the 5Ghz power change and turn back ON the RBS.
2. Something I've done and continue to use as I have resources. Setup a 2nd router, something that is easily configurable for 2.4Ghz. You can even connect it behind the Orbi system as a 2nd router. Just temporary. Use this router with Wi-Fi channels set to different from the Orbi system. Use the same SSID name and password on the 2nd router as the Orbi system. Sit close to this 2nd router with your setup and IoT devices. Use this 2nd router to get the IoT device connected. Once it's connected and up and running, just turn OFF this 2nd router. This will force the IoT to auto migrate to the Orbi Wi-Fi signal and should auto connect with out any issues. I've done this many times when I bring on a new router system to test. I'll set up the new router and get it all configured using same SSID name and PW. When I go to put it in place, I leave the out going router system ON, just not connected to anything, long enough to get the new router in coming turned on and connected. Once the new router is up and running, I turned OFF the out going router and all wifi devices auto migrate and connect to then new router. "Easy peasy lemon squeezy."
Overall, its the new or initial setup for IoT that's the problem. Most users do know or are aware of Orbi and IoT issues by now. It's not new. Been around for a while. For new users, and with some help and using the suggestions and information posted by others, all Orbi systems will work with IoT devices. Just needs some help to get it going where needed.
FURRYe38 wrote:
2. Something I've done and continue to use as I have resources. Setup a 2nd router, something that is easily configurable for 2.4Ghz. You can even connect it behind the Orbi system as a 2nd router. Just temporary.
Would it also work to have that second router in AP mode – or an extender – with a separate SSID and then to use that for the setup process?
That might be easier for some people to set up and configure and might be a useful function for a redundant router.
