RBRE960 (7.2.6.21) and 2.4ghz-only IoT and Sonos Playbar Gen 1

I fear there is too much fixation on frequency.  For example:

---

gumpgump wrote:

Another thing, the iPhone 15 Pro operates at 6ghz

---

While technically correct, this is not material.  The iPhone 15 Pro has this specification:

From Apple:

https://support.apple.com/kb/SP903?locale=en_US 

• Wi‑Fi 6E (802.11ax) with 2x2 MIMO⁹

From GSM Arena:

https://www.gsmarena.com/apple_iphone_15_pro-12557.php 

a/b/g/n/ac/6e, means that it supports 2.4G and 5G WiFi (dual band) including every WiFi standard from the very first (802.11a) through the most recent (802.11ax) and also supports the new WiFi6E (6Ghz frequency band).  This iPhone is supposed to communicate with any form of WiFi, from the oldest pre-2000 WiFi to the latest, which also is supported on the RBRE960 Orbi system.  i.e. if you enable the WiFi6E (6GHz) feature on this Orbi system, the iPhone should connect to it.

(See page 62 of the user manual:

https://www.downloads.netgear.com/files/GDC/RBKE963/RBRE960_RBSE960_UM_EN.pdf  )

The way the vast majority of Internet of Things (IoT) devices work is

• When it is waiting to be configured, the device (soundbar) broadcasts a WiFi signal with some goofy name (like maybe 'sonos-12345'.
• The app installed on the smartphone looks for a WiFi access point with that goofy name and connects to it.
• If the device is supposed to connect to the home WiFi (and nearly all of them do), the app communicates the WiFi credentials to the device, i.e. WiFi SSID and password.
• The device searches for a WiFi system with that SSID, asks to associate with it (fancy term for connect), supplies the required password, and is connected.
• From then on, if either the IoT device or the WiFi network is powered off, when power is restored the IoT device connects automatically.
• The smartphone can connect to the primary, IoT, or 6G network at any speed. Because they communicate through the network, there is no problem.

Some IoT devices have smartphone apps that are poorly written:

• Some of them detect that the smartphone is connected to WiFi at 5G and refuse to proceed. "MUST have 2.4G" they scream. Ironically, if they would just deliver the SSID/password to the IoT  device, it would find the WiFi network just fine.  But they are trying to be too helpful and will not proceed.
• Some of them appear to convey the hardware MAC address of the 5G WiFi access point to the IoT device.  Having only a 2.4G radio, it cannot find this access point.  Again, trying to be too helpful.
• Some are just s**t.  (I won't name the brand, but...) It took me almost 10 tries to get a window blind controller to work.  The setup failed over (and over, and over).  Did everything but light a candle. Finally, success.

So, what's the solution?  The most common tactic is to have the smartphone connected at 2.4G to the desired WiFi SSID. Complete the setup. After that, the smartphone can connect any way it pleases and everything will be good.

There are several ways to do this:

• Some users keep an old WiFi router (in a box or on a shelf) that can disable 5G.  Temporarily power off the Orbi. Connect the old router and set it to exactly the SSID/password used by the Orbi.  The smartphone will connect at 2.4G because that is all there is.  After the setup, remove the old router and power on the Orbi.
• Some users create a 2.4G WiFi Hot Spot on one cell phone with exactly the same SSID/password as the Orbi. Power off the Orbi. Go through the setup. etc. etc.
• Some of the newer AX routers now offer an IoT SSID that can disable 5G (including the 960).  Connect the smartphone to the 2.4G IoT SSID and go through the setup.

It would be really helpful to (a) have a link to the Sonos Soundbar setup instructions, and (b) have detailed information about exactly how the setup process fails.