› UKTH forums › 🛜 Wireless Routers & Modems › ASUS & Wireless › ASUS ZenWiFi AX Whole Home Tri-Band Mesh WiFi 6 System Not sure if this is the right place to ask…. I am thinking of upgrading my Google Mesh wifi to the above. Has anyone used this and does it... › Reply To: ASUS ZenWiFi AX Whole Home Tri-Band Mesh WiFi 6 System Not sure if this is the right place to ask…. I am thinking of upgrading my Google Mesh wifi to the above. Has anyone used this and does it…
Ok so this morning the node went “offline” again with the constant blinking blue LED. There was nothing in the logs showing “radar”.
Therefore I started the process of downgrading the firmware on the router and node to 386.49873 and do a factory reset on both.
I did the router first, downgrade, factory reset, then setup. I then unplugged it and moved onto the node. It was quite difficult to connect to the node, as the blue LED kept flashing after startup, even after factory resetting a few times. I eventually was able to connect over ethernet to flash the older firmware, let it reboot and did a factory reset. The blue led flashing came back (on the older firmware!), and seemed to periodically restart itself. I did another factory reset and turned on the primary router. Eventually the node started up connected up to the mesh network itself. I though I would have to trigger this or at least hint that this is how I wanted it to operate, but it just joined the mesh network itself which was a bit strange, no? Hopefully there is no underlying hardware issue with the node.
Anyway both have been running for a few hours. Router and node are still in same locations in the house. I haven’t moved them closer to each other yet. The are still connected via the 5GHZ-2 backhaul. The signal hovers between -62 to -69dBm (Great) and -70 to -72dBm (Good). I was able to achieve 501.87Mbps download and 51.22Mbps upload over wifi while connected to the node (verified I was connected to the node via the app). This is on a Virgin Media 500Mb/50Mb account. Hopefully the issues were only caused by the 388.21099 firmware. I guess time will tell.
You need to login in order to vote
