Upgrading a RBR50 to RBE771

Sorry there is not. 

You'll need to enter in all from scratch. 

Thanks!  I didn't think so but never hurts to ask.  

One tiny piece of advice:  Power up the new RBE771 and configure it without defining the WiFi network name (SSID).  After those 60+ devices have been entered into the LAN Setup table, then you can power off the existing RBR50, connect the RBE771 to the ISP device (modem, ONT...) and set the WiFi credentials to exactly match those of the RBR50.

The reason is Netgear's implementation of DHCP.  We humans expect that reserving an IP address for a device in the LAN setup table means that the router will always assign that IP address to the device.  Alas, this is not so.  If the RBE771 begins broadcasting the WiFi network before the LAN setup table is created, then every device in the house will detect it and immediately sign in.  Having nothing in the LAN setup table, the router will randomly assign IP addresses to each device.  If the device is powered off and back on later, the router ARP table will already have that IP address and the device will be given that IP address again.  The only way to correct this is to power off the router (and disconnect every device in the house) and then power it back on again. and hope that no device in the house that is not in the LAN Setup table grabs one of those "reserved" IP addresses.

(in my opinion.....)

When the original Orbi product was released, customers quickly discovered that the smartphone applications for some Internet of Things (IoT) devices were poorly designed.  The actual devices had inexpensive WiFi chips which supported only 2.4G WiFi.  (a) they cost less, (b) IoT devices typically consume nearly zero bandwidth, and (c) 2.4G WiFi has greater "reach" than 5G WiFi.  While the vast majority could be connected to consumer WiFi without problems, some of the smartphone apps were just pathetic.  Many would detect that the smartphone was connected to the network at 5G and refuse to even look for the IoT device.  Others would carefully communicate the WiFi credentials and the 5G MAC address to the IoT device. (which it could not find because it only supported 2.4G)

The obvious solutions included:

• Let the user temporarily turn off the 5G radio. Connect the smartphone at 2.4G. Set up the IoT device.  Then turn 5G WiFi back on.
  Netgear steadfastly refused to consider this.
• Let the user temporarily assign a different WiFi SSID to the 5G radio, leaving the original SSID only on the 2.4G radio.  Set up the device. Then change the 5G SSID back to match.
  Netgear refused to do this.

Finally, after YEARS of consumers complaining, Netgear introduced this "IoT" network, which

• Has a different SSID than the primary network, and
• Allows both the 2.4G and 5G radios to be shut off temporariliy.

Duh!

The IoT network shares the same IP subnet as the primary network.  IoT Devices are not quarantined.  Personally, I see no pressing need to create an IoT network unless you have devices which have poorly written smartphone apps and are difficult to connect to the primary WiFi network.

HappyCat​ 

 I have run into the 2.4/5G problem on several  items before.  Fortunately I was able to finally get the items loaded. Unfortunately many apps are still poorly written. One of the reasons I choose Orbi is it still has a web interface. Many other have dropped theirs  and only use the phones now.

 I agree, a loT network is not worth the effort.   

 I have made the change to the RBE771 and overall it went well   Thanks HappyCat​ . Still working out a few bugs and typos. I have a couple of 2.4G WiFi ceiling fans that keep dropping plus a few other things but the updated Orbi has many nice changes & updates.

 One thing I have noticed is the web interface and Phone app are very different. The web is very easy to name items and arrange different looks.  The app has a mind of its own and gives random names to things and still is not very versatile. It won't let you change things such as  brand or model names .  

So after a week I still have issues with my Hunter ceiling fans. They have an app called simplyconnect (not so simple) and its was renamed Hunter Smart ( not smart either). Funny thing is as an extra perk? the app finds all your other loT items as well. The ONLY thing it can't find is its own ceiling fans!!

They recommend having the 2.4/5G together may cause an issue and to use WPA2 only and turn off WPA3.  Sooooo I created the loT WiFi with those off and still no joy!  I saw them for a moment with a 2.4G loT SSID and then nada.   On my old RBR50 they added fine despite the 2.4/5G on one SSID. Of course it didn't have WPA3 but that issue should be solved as well. I'm calling Hunter tomorrow but I'm sure they will just blame Apple, Orbi  or both.

 Any ideals??

If the new 770 system has exactly the same WiFi credentials (SSID, password) as the previous system, then the Hunter fans should have connected automatically to the new system.