RT-BE88U and RT-AX59U AiMesh Network on Latest FW

[Szadzik]

Hi All,

I enjoyed stable connectivity using RT-BE88U as my AiMesh router and RT-AX59U as a node for quite a while and recently updated the BE88U to the latest 3.0.0.6.102_37094 FW on BE88U. Since then, AiMesh does not work.

BE88U does not see the AX59U as an available node.

Steps I tried:
-WPS-reset the AX59U multiple times
- Upgraded to the latest FW
- WPS-reset the BE88U
- Flashed the latest FW again manually (3.0.0.4.388_33405)and WPS-reset again.
To no avail.

Ethernet pairing steps:
- Paired them up using Ethernet and they connected and synced up
- Changed the setting to prefer 5GHz as bakhaul for the mesh network
- Rebooted AX59U
- BE88U shows AX59U as offline.
- AX59U's LED is white, as if connected
- Used the option to reboot the mesh network in the Android app and both routers rebooted
- Connected via LAN to AX59U and it provides Internet connectivity, though BE88U does not show the client connected to AX via Ethernet in its interface. EDIT: On the main screen when I view the devices connected it shows the client connected via Ethernet to the AX59U as connected via Ethernet, the AX59U still shows as not connected.

Any idea how to fix this mess apart from running an Ethernet cable from BE to AX, which is not an option for me?

 

[Tech9]

Most likely related to this note on RT-BE88U firmware release:

"Please be advised that due to an architecture upgrade in AiMesh, we highly discourage downgrading to earlier firmware versions as it may result in connectivity problems. If you experience any difficulties, we suggest resetting the AiMesh router to its default settings and re-establishing the mesh connection."

You may have to wait for RT-AX59U firmware release catching up with the changes.

 

[Szadzik]

I saw the notice, yes, and it only states I should not be downgrading, and that is fine.

The interesting thing is, that every single time I reboot the BE from web interface it goes into the 'x% Updating' phase from 0% to 100% and only then reboots, as if ever time it was rebooted it had to go through the process of applying firwamre change.s

 

[Szadzik]

Just found my old RP-AX56 and decided to test adding it as a node to BE88U and to my surprise it was found and added without any issues. This points me in the direction of the AX59U as the source of the issue.

Any pointers on how to troubleshoot the AX59U are welcome. I will reflash it, and reset.

EDIT: AX59U is now visible to BE88 when searching for new nodes, but will not complete the process of adding it as a node

EDIT2: AX59U became visible only because of AX56 being a node and the two communicate, while AX59 still does not communicate with BE88.
Adding the node while it communicates through another node does not work.

EDIT3: Synced the AX59U to the BE88U via Ethernet and then moved it close to the RP-AX56 to see if it could use the AX56 as backhaul connection, and again the AX59U is shown as disconnected in BE88U's GUI, but the LED is whitel as if all was fine
Almost ready to give up, but in the meantime emailed Asus support to see what they say.


EDIT4:
Setup steps:
RP-AX56 connected as a node through WiFi.
RT-AX59U connected as a node through Ethernet and set up to use BE88u as the Preferred WiFi Uplink AP

Test 1:
RP-AX56 turned off
RT-AX59U disconnected from Ethernet

Result 1:
RT-AX59U not working as a node.

Test 2:
RP-AX56 turned on and sitting between BE88U and RT-AX59U
Sitting not far away from RP-AX56

Result 2:
Both RP-AX56 and RT-AX59U working as nodes.
Asus Router app showing the two nodes connecting from BE88u
BE88U web GUI showing RP-AX566 feeding the RT-AX59U, or at least looking that way. Screenshot attached.


For now I am leaving it as it is. Will be looking to get a huge drill to drill from ground floor to 1st floor and get an Ethernet cable running from BE88U directly to RT-AX59U.