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.
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.
Agree with most of what you've said, however a few things stand out as unrealistic or not quite right.
1. Yes, it is the 'smart' devices that are the primary cause of the issue. The reason is that chips to support 2.4ghz are cheaper than those for 5.0ghz or both, and 2.4 supports longer range (which is an issue that mesh systems don't really have, because that's what they're designed to fix). Yes, for the price of these things, they should support 5.0ghz too, but they generally don't. And, there have also been poor coding decisions made. My new garage door opener was able to figure it out painlessly, even though they don't support 5.0ghz.
The problem is, if I have pre-existing devices, I don't have the option of returning them when they can't connect. That would be just as expensive a retrofit as upgrading to a top end Orbi, or replacing my phone. So, blaming them doesn't help with creating a solution, and the fact is, the mesh system designers had to know that this was an issue, and that the people most likely to buy a mesh system are the same target market as people buying connected devices, so this should have been solved a long time ago, especially at Orbi's price point. Apple is a little too cute in how they do their programming, but they are the least at fault in this problem. Would be nice if there was a table showing the combinations that work, so it doesn't have to be trial and error.
2. Turning down the 5.0ghz radio can work, but it depends whether you can move the router far enough away from the thing you're trying to connect. This doesn't work for me, because even at 45ft distance from a video doorbell and smart lock, the signal on 5.0 is still strong enough that it is the preferred network. This is actually pretty annoying, because if you can attenuate the signal down to 25%, why not to 0%, or even 5 or 10%? This is the first solution that Netgear suggests, but they know it only works for some people.
3. All Orbies will work with IoT products, but importantly, not all IoT products work with Orbi. If you have the wrong ones in your home before installing mesh, there's not much you can do, since it's too late to return them.
bad_guy wrote:
Agree with most of what you've said, however a few things stand out as unrealistic or not quite right.
1. Yes, it is the 'smart' devices that are the primary cause of the issue. The reason is that chips to support 2.4ghz are cheaper than those for 5.0ghz or both, and 2.4 supports longer range (which is an issue that mesh systems don't really have, because that's what they're designed to fix). Yes, for the price of these things, they should support 5.0ghz too, but they generally don't. And, there have also been poor coding decisions made. My new garage door opener was able to figure it out painlessly, even though they don't support 5.0ghz.
The problem is, if I have pre-existing devices, I don't have the option of returning them when they can't connect. That would be just as expensive a retrofit as upgrading to a top end Orbi, or replacing my phone. So, blaming them doesn't help with creating a solution, and the fact is, the mesh system designers had to know that this was an issue, and that the people most likely to buy a mesh system are the same target market as people buying connected devices, so this should have been solved a long time ago, especially at Orbi's price point. Apple is a little too cute in how they do their programming, but they are the least at fault in this problem. Would be nice if there was a table showing the combinations that work, so it doesn't have to be trial and error.
A little troubleshooting on existing devices maybe all that needed. I've not had any problems with my existing devices getting connected or re-connected when I change out a router for something else. As long as I use the same SSID name and PW, I've not seen any issues. I have seen odd issues that effect some operation however that's not relating to getting connected.
2. Turning down the 5.0ghz radio can work, but it depends whether you can move the router far enough away from the thing you're trying to connect. This doesn't work for me, because even at 45ft distance from a video doorbell and smart lock, the signal on 5.0 is still strong enough that it is the preferred network. This is actually pretty annoying, because if you can attenuate the signal down to 25%, why not to 0%, or even 5 or 10%? This is the first solution that Netgear suggests, but they know it only works for some people.
if the IoT is 2.4Ghz then it will never see the 5Ghz radio so you don't have to distance the IoT device from the router. Just distance the SETUP mobile device with the IoT app from the router when you have turned down the 5Ghz transmit power.
3. All Orbies will work with IoT products, but importantly, not all IoT products work with Orbi. If you have the wrong ones in your home before installing mesh, there's not much you can do, since it's too late to return them.
From what others have posted and from my personal experiences and all the Orbi systems and other MESH systems I've tested, most IoT will work. Again, maybe some help and configuration maybe needed.
"A little troubleshooting on existing devices maybe all that needed. I've not had any problems with my existing devices getting connected or re-connected when I change out a router for something else. As long as I use the same SSID name and PW, I've not seen any issues. I have seen odd issues that effect some operation however that's not relating to getting connected."
I spent many hours troubleshooting with Netgear's support engineers. Some devices can be connected, others cannot. Luck of the draw depending on what you have installed in your home.
"f the IoT is 2.4Ghz then it will never see the 5Ghz radio so you don't have to distance the IoT device from the router. Just distance the SETUP mobile device with the IoT app from the router when you have turned down the 5Ghz transmit power."
The problem is not the device trying to connect on 5.0ghz, but that the phone and device must be on the same 2.4ghz network. Since I need to scan QR codes and talk to the devices via Bluetooth on my phone, the phone needs to be in close proximity to the device to do the setup on the app. Since I can't have sufficient distance from the router to the device that I'm trying to setup, the phone will always prefer 5.0ghz, because 25% power is still too much for the phone to be out of range, so it can't be forced onto the same network as the smart (borderline stupid actually) device. My phone does not have the "maximum compatibility" option in the Hotspot settings to force it to connect on the 2.4 band.
"From what others have posted and from my personal experiences and all the Orbi systems and other MESH systems I've tested, most IoT will work. Again, maybe some help and configuration maybe needed."
In my setup, there is no configuration possible that solves this, and I've stumped all of Netgear's engineers who've tried to help. Like I've said, some people may find the suggestions already provided will work, but not if you have the bad luck to have the wrong devices.
The irony is that the reason I went with a mesh system is that my older router had trouble reaching these devices, even with extenders, and I had noticeably weaker and slower connections on my computers as I moved around the house, but it was mostly what happened whenever we had one of our all-too-frequent power failures.
The extenders wouldn't reconnect properly, and so none of the devices that depended on them would work until everything was rebooted and manually reset. And that's not good if I have a video doorbell, and I don't know that it isn't working until there's someone pounding on the door, or my fingerprint door lock won't open the door because it can't connect to the iinternet.
Orbi bathes the whole house and most of the outdoors in strong consistent signal, and automatically resets itself after power issues, but can't connect to the devices that were the reason for buying it.
Agreed. I think that it comes down to some IoT and there SW is just sub standard. Though should be following standards, highly doubtful when you get all kinds of junk out there and very unknown development and testing practices, if any. 🤔
I think were done here though.
Enjoy. 😁