Factory Resetting soft bricks Router requiring it to be booted via recovery button and firmware reflashed via TFTP

Upgrading from V9.2.5.1.13.1 to V9.2.5.1.17 gave a warning I was upgrading to an old version

Clicking Orbi Logo in left corner should take you to root Admin console (ex. 10.0.0.1)

Clicking Parental Controls from Home should take you to Parental Controls Settings ( ex http://10.0.0.1/parental_basic.htm )

Rename "Security" tile on Home to "Netgear Armor"

Clicking "Security" tile on Home page should take you somewhere to enable/disable Armor which is absent from the firmware right now



Remove advertisement for mobile app from sidebar

On Attached Devices screen make the IP of connected satellites clickable to spawn a new browser window or tab of the satellite



On Attached Devices screen show the connection type (10/100/1000) for wired devices or % of signal for wireless devices (ex 20%/50%/80%)



Ability to either receive notification of VOXEL firmware updates via the Admin UI (similar to how Orbi does for official) and/or Allow updating to VOXEL firmware via the online update mechanism.



So far so good I'm really happy with the experience so far. For reference, here is a random real world indicator of the value add I stumbled upon this morning.



The WIFI map of my house as produced by Roomba robot vacuum from last week.



https://i.imgur.com/6TUNoJ2.png



Here is the same WIFI map from this morning after upgrading to VOXEL yesterday.



https://i.imgur.com/BHbp52L.png



Thanks again!

Hi Voxel.Thank you for your efforts and your continued contribution to the community. I'm relatively new to flashing custom firmware to the Orbi (literally just found out about it days ago) so let me share some feedback from my experience.I initially upgraded from stock 2.5.1.16 to 9.2.5.1.13.1. I manually updated each satellite individually and then the router. This process was smooth and painless.I thought it would be a good idea to factory reset at this point, but that led to the router soft bricking (reboot with pulsing white) requiring me to TFTP stock firmware back onto it, factory resetting from stock and then flashing 9.2.5.1.13.1. All was great after that.The next morning I woke up to find that 9.2.5.1.17 was released (wow, you work so hard having already incorporated the stock 2.5.1.16 changes into it)I went to do a manual update of the satellites and routers (individually as before) and was prompted that the firmware I was loading was an older version (9.2.5.1.13.1 -> 9.2.5.1.17), not sure why the mix match, but I agreed that was ok and it proceeded without issue.I explored a bit and came up with the following observations and suggestions: