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...
<<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:<<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.