Frustration with RT-BE88U and SmartDevices

[phillyaj]

After realizing my RT-AX86U couldn't handle my 2.5G WAN service, I decided to upgrade to the RT-BE88U. It handles the multi-gig service just fine and the upgraded processor is nice, however, I have been increasingly frustrated with the Smart Devices (IoT). Currently the only way I'm dealing is a nightly reboot of the BE-88U

My setup is an BE-88U as my main router, with 2 x AC68Us as AiMesh Nodes. I have numerous IoT devices (mostly 2.4Ghz), including Echos, plugs, switches, cameras, etc.. For some reason, numerous devices disconnect and don't stay connected. Here's what I tried...

**Previously I had my AX86U setup with separate 2.4 and 5 Ghz networks, with my IoT devices using the 2.4Ghz network.

- Initially I had MLO enabled, which doesn't allow for separation of the 5Ghz and 2.4Ghz SSID's. I reset some of the devices, connecting to the new network. Some devices work, some did not.
- I setup a dedicated IoT (2.4Ghz) network with very mixed results again. Some worked, some didn't....and the Mesh Nodes cannot deal with this separate network.

- Turned off MLO and went back to separate 2.4 and 5Ghz networks. I noticed that the "Guest Network Pro" now had a combined (2.4 and 5Ghz) network setup (the same SSID as my 2.4Ghz network??) that is listed as "Default IoT Network)...which was odd..but OK. Figured this work...Nope... Same thing. Very inconsistent and not stable.
- Deleted the Default IOT and setup a 2.4Ghz IOT network....Nope same disconnect and instability.
-Added the default IoT network (Combined 2.4 and 5Ghz) network back again....Still unstable.

***Intermission: Thinking it might be my AiMesh nodes (All of with used to work just fine previously), decided to power them off and/or reboot them during various tests. Same results.

- One thing I did notice is that although the WiFi turns off/On when you make changes, rebooting the router seems to make things better....for a while..

- Frustrated, last night I decided to do NIGHTLY (3AM) reboots and seeing how that works.

***This morning, I decided to turn off WiFI 7 Mode on both 2.4 and 5Ghz radios to see if that helps.

I did notice a SYSLOG entry that may or may not be related. Haven't researched it yet to see what that's all about.

Nov 25 08:40:36 kernel: CPU: 1 PID: 15780 Comm: dcd Tainted: P O 4.19.275 #1
Nov 25 08:40:36 kernel: Hardware name: Broadcom-v8A (DT)
Nov 25 08:40:36 kernel: pstate: 200f0010 (nzCv q A32 LE aif)
Nov 25 08:40:36 kernel: pc : 00000000f751c558
Nov 25 08:40:36 kernel: lr : 0000000080808080
Nov 25 08:40:36 kernel: sp : 00000000ff8df260
Nov 25 08:40:36 kernel: x12: 0000000000000000
Nov 25 08:40:36 kernel: x11: 0000000000000000 x10: 0000000000000008
Nov 25 08:40:36 kernel: x9 : 00000000000a73d0 x8 : 00000000f63fd008
Nov 25 08:40:36 kernel: x7 : 00000000000a78b6 x6 : 0000000000000000
Nov 25 08:40:36 kernel: x5 : 0000000000000007 x4 : 00000000fefefeff
Nov 25 08:40:36 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Nov 25 08:40:36 kernel: x1 : 0000000000000107 x0 : 0000000000000000

Doing testing with a houseful of people is challenging, as everything you do (Adjustments, Add/Remove Guest networks) restarts the WiFi radios...and a Reboot is probably the best strategy. I REALLY want the BE-88U to work as SOLID as my AX-86U did!!!

 

[Jbennett360]

Can you try the basics without the mesh devices attached?

Turn off MLO and Wi-Fi 7
Separate the bands.
Connect to 2.4ghz

See if that works.

If it does

Then maybe try an IOT network.

Start simple and see if the basics work.

Your AC68U's are EOL and are WiFi 5 devices.

 

[helo1976]

After realizing my RT-AX86U couldn't handle my 2.5G WAN service, I decided to upgrade to the RT-BE88U. It handles the multi-gig service just fine and the upgraded processor is nice, however, I have been increasingly frustrated with the Smart Devices (IoT). Currently the only way I'm dealing is a nightly reboot of the BE-88U

My setup is an BE-88U as my main router, with 2 x AC68Us as AiMesh Nodes. I have numerous IoT devices (mostly 2.4Ghz), including Echos, plugs, switches, cameras, etc.. For some reason, numerous devices disconnect and don't stay connected. Here's what I tried...

**Previously I had my AX86U setup with separate 2.4 and 5 Ghz networks, with my IoT devices using the 2.4Ghz network.

- Initially I had MLO enabled, which doesn't allow for separation of the 5Ghz and 2.4Ghz SSID's. I reset some of the devices, connecting to the new network. Some devices work, some did not.
- I setup a dedicated IoT (2.4Ghz) network with very mixed results again. Some worked, some didn't....and the Mesh Nodes cannot deal with this separate network.

- Turned off MLO and went back to separate 2.4 and 5Ghz networks. I noticed that the "Guest Network Pro" now had a combined (2.4 and 5Ghz) network setup (the same SSID as my 2.4Ghz network??) that is listed as "Default IoT Network)...which was odd..but OK. Figured this work...Nope... Same thing. Very inconsistent and not stable.
- Deleted the Default IOT and setup a 2.4Ghz IOT network....Nope same disconnect and instability.
-Added the default IoT network (Combined 2.4 and 5Ghz) network back again....Still unstable.

***Intermission: Thinking it might be my AiMesh nodes (All of with used to work just fine previously), decided to power them off and/or reboot them during various tests. Same results.

- One thing I did notice is that although the WiFi turns off/On when you make changes, rebooting the router seems to make things better....for a while..

- Frustrated, last night I decided to do NIGHTLY (3AM) reboots and seeing how that works.

***This morning, I decided to turn off WiFI 7 Mode on both 2.4 and 5Ghz radios to see if that helps.

I did notice a SYSLOG entry that may or may not be related. Haven't researched it yet to see what that's all about.

Nov 25 08:40:36 kernel: CPU: 1 PID: 15780 Comm: dcd Tainted: P O 4.19.275 #1
Nov 25 08:40:36 kernel: Hardware name: Broadcom-v8A (DT)
Nov 25 08:40:36 kernel: pstate: 200f0010 (nzCv q A32 LE aif)
Nov 25 08:40:36 kernel: pc : 00000000f751c558
Nov 25 08:40:36 kernel: lr : 0000000080808080
Nov 25 08:40:36 kernel: sp : 00000000ff8df260
Nov 25 08:40:36 kernel: x12: 0000000000000000
Nov 25 08:40:36 kernel: x11: 0000000000000000 x10: 0000000000000008
Nov 25 08:40:36 kernel: x9 : 00000000000a73d0 x8 : 00000000f63fd008
Nov 25 08:40:36 kernel: x7 : 00000000000a78b6 x6 : 0000000000000000
Nov 25 08:40:36 kernel: x5 : 0000000000000007 x4 : 00000000fefefeff
Nov 25 08:40:36 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Nov 25 08:40:36 kernel: x1 : 0000000000000107 x0 : 0000000000000000

Doing testing with a houseful of people is challenging, as everything you do (Adjustments, Add/Remove Guest networks) restarts the WiFi radios...and a Reboot is probably the best strategy. I REALLY want the BE-88U to work as SOLID as my AX-86U did!!!

Yes, same problem here, it is not you

I've quit trying to use MLO/Wifi7. It just is very frustrating. I came from a combination of AX88 with AX55 AiMesh nodes and upgraded to BE88 with 4 TUF-AX3000's and recognize everything you mention in your post. Long story short, I have submitted a Asus support case, no response. I just hope that it will be resolved in a future firmware upgrade, but it is also very dissapointing how very few firmware versions are being released for this model.

 

[Jbennett360]

Yes, same problem here, it is not you

I've quit trying to use MLO/Wifi7. It just is very frustrating. I came from a combination of AX88 with AX55 AiMesh nodes and upgraded to BE88 with 4 TUF-AX3000's and recognize everything you mention in your post. Long story short, I have submitted a Asus support case, no response. I just hope that it will be resolved in a future firmware upgrade, but it is also very dissapointing how very few firmware versions are being released for this model.

Have you tried the latest firmware that was released yesterday?

Release - ASUS RT-BE88U Firmware version 3.0.0.6.102_37094 (25 Nov. 2024)

ASUS RT-BE88U Firmware version 3.0.0.6.102_37094 Version 3.0.0.6.102_37094 65.82 MB 2024/11/24 Please unzip the firmware file, and then verify the checksum. SHA256: 5678e951eaff889f1e84cd1ad8799aa1afe7913393a9d538e20cc17976a12d16 *Please be advised that due to an architecture upgrade in AiMesh...

www.snbforums.com

 

[phillyaj]

After realizing my RT-AX86U couldn't handle my 2.5G WAN service, I decided to upgrade to the RT-BE88U. It handles the multi-gig service just fine and the upgraded processor is nice, however, I have been increasingly frustrated with the Smart Devices (IoT). Currently the only way I'm dealing is a nightly reboot of the BE-88U

My setup is an BE-88U as my main router, with 2 x AC68Us as AiMesh Nodes. I have numerous IoT devices (mostly 2.4Ghz), including Echos, plugs, switches, cameras, etc.. For some reason, numerous devices disconnect and don't stay connected. Here's what I tried...

**Previously I had my AX86U setup with separate 2.4 and 5 Ghz networks, with my IoT devices using the 2.4Ghz network.

- Initially I had MLO enabled, which doesn't allow for separation of the 5Ghz and 2.4Ghz SSID's. I reset some of the devices, connecting to the new network. Some devices work, some did not.
- I setup a dedicated IoT (2.4Ghz) network with very mixed results again. Some worked, some didn't....and the Mesh Nodes cannot deal with this separate network.

- Turned off MLO and went back to separate 2.4 and 5Ghz networks. I noticed that the "Guest Network Pro" now had a combined (2.4 and 5Ghz) network setup (the same SSID as my 2.4Ghz network??) that is listed as "Default IoT Network)...which was odd..but OK. Figured this work...Nope... Same thing. Very inconsistent and not stable.
- Deleted the Default IOT and setup a 2.4Ghz IOT network....Nope same disconnect and instability.
-Added the default IoT network (Combined 2.4 and 5Ghz) network back again....Still unstable.

***Intermission: Thinking it might be my AiMesh nodes (All of with used to work just fine previously), decided to power them off and/or reboot them during various tests. Same results.

- One thing I did notice is that although the WiFi turns off/On when you make changes, rebooting the router seems to make things better....for a while..

- Frustrated, last night I decided to do NIGHTLY (3AM) reboots and seeing how that works.

***This morning, I decided to turn off WiFI 7 Mode on both 2.4 and 5Ghz radios to see if that helps.

I did notice a SYSLOG entry that may or may not be related. Haven't researched it yet to see what that's all about.

Nov 25 08:40:36 kernel: CPU: 1 PID: 15780 Comm: dcd Tainted: P O 4.19.275 #1
Nov 25 08:40:36 kernel: Hardware name: Broadcom-v8A (DT)
Nov 25 08:40:36 kernel: pstate: 200f0010 (nzCv q A32 LE aif)
Nov 25 08:40:36 kernel: pc : 00000000f751c558
Nov 25 08:40:36 kernel: lr : 0000000080808080
Nov 25 08:40:36 kernel: sp : 00000000ff8df260
Nov 25 08:40:36 kernel: x12: 0000000000000000
Nov 25 08:40:36 kernel: x11: 0000000000000000 x10: 0000000000000008
Nov 25 08:40:36 kernel: x9 : 00000000000a73d0 x8 : 00000000f63fd008
Nov 25 08:40:36 kernel: x7 : 00000000000a78b6 x6 : 0000000000000000
Nov 25 08:40:36 kernel: x5 : 0000000000000007 x4 : 00000000fefefeff
Nov 25 08:40:36 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Nov 25 08:40:36 kernel: x1 : 0000000000000107 x0 : 0000000000000000

Doing testing with a houseful of people is challenging, as everything you do (Adjustments, Add/Remove Guest networks) restarts the WiFi radios...and a Reboot is probably the best strategy. I REALLY want the BE-88U to work as SOLID as my AX-86U did!!!

So Here's an update. A few days in....and everything seems to be stable.. I'm still seeing the kernel error in the syslog (See original post). IOT devices are staying connected throughout the day. Here's where I'm at:

- MLO <OFF>
- SmartConnect <OFF> ***FYI...Turning on MLO will force SmartConnect to be ON
- Separate 2.4Ghz and 5Ghz networks.
- Wifi 7 Mode <DISABLED> for 2.4Ghz Band (under Wireless - Professional) **I Thought I disabled Wifi 7 for both 2.4 and 5Ghz, but apparently, I only did the 2.4 band. Not sure it matters.
- Default IOT network and 2nd IOT network setup in Guest Network. *I only setup 1 device to connect to the 2nd IOT network as a test*
- AIProtection <OFF>
- 2 AIMesh Nodes connected.
- Nightly Reboot @ 3AM.

Next Steps:
- Get back to Basics. (I'm pretty much there now. Might try removing the two IOT networks and see if the IOT devices still can connect to the default 2.4Ghz network ok)
- After EVERY change, Reboot the router.
- Disable nightly reboots -
-Wait a few days and see if everything is still stable.
- Setup a dedicated IOT 2.4Ghz network - REBOOT ROUTER
- Wait a few days to confirm test devices setup on default IOT network are staying connected..
- Enable Wifi 7 Mode on 2.4Ghz Network - REBOOT Router.
- Wait a few days
**Not sure If I should enable MLO or not. IF I do, I need to re-connect ALL my 2.4Ghz devices to the dedicated IOT network..

Also considering what to do with the kernel error. Might open a ticket with ASUS, or wait to see if a FW update comes out.

I may also see if I can trade-in my AC68U's at Best Buy and pick up the AX3000's (Wifi 6) as AiMesh nodes. IF Best Buy will take them, they give you a 15% discount.

I guess we will see how much I can get done. As I said, with a houseful of people, rebooting the primary router is challenging, unless I want to get up very early or stay up very late..

Happy Holidays to all

 

[phillyaj]

Have you tried the latest firmware that was released yesterday?

Release - ASUS RT-BE88U Firmware version 3.0.0.6.102_37094 (25 Nov. 2024)

ASUS RT-BE88U Firmware version 3.0.0.6.102_37094 Version 3.0.0.6.102_37094 65.82 MB 2024/11/24 Please unzip the firmware file, and then verify the checksum. SHA256: 5678e951eaff889f1e84cd1ad8799aa1afe7913393a9d538e20cc17976a12d16 *Please be advised that due to an architecture upgrade in AiMesh...

www.snbforums.com

I haven't...but I might give that a try. I am running Asuswrt-Merlin FW (3006.102.2_2).

 

[Jbennett360]

I haven't...but I might give that a try. I am running Asuswrt-Merlin FW (3006.102.2_2).

So you're running BETA firmware...

The RT-BE88U development is currently based off an old 102_33xxx codebase, with a number of changes in this release that haven't been properly integrated into Asuswrt-Merlin yet.

 

[phillyaj]

So you're running BETA firmware...

The RT-BE88U development is currently based off an old 102_33xxx codebase, with a number of changes in this release that haven't been properly integrated into Asuswrt-Merlin yet.

Guess I should have been Clearer....I AM running the ASUSWRT-MERLIN FW for the BE88U. I'll try out the ASUS "Official" FW. Don't see anything in the Release Notes to give me hope., but I guess we will see.

 

[Jbennett360]

So you're running BETA firmware...

Guess I should have been Clearer....I AM running the ASUSWRT-MERLIN FW for the BE88U. I'll try out the ASUS "Official" FW. Don't see anything in the Release Notes to give me hope., but I guess we will see.

I'd personally stick to stock on 3006.

 

[Dakar]

I ran through a very similar process, RT-AC86U to RT-BE88U and the thing that fixed it for me was to change WPA2/WPA3 to just old fashioned WPA2, it also disabled WiFi7 in the process but all my devices have connected back and speeds are good again too.
Must be that some of the IOT devices didn't like the WPA2/WPA3 setting.

Just to add, running latest Merlin too.

 

[Treadler]

I ran through a very similar process, RT-AC86U to RT-BE88U and the thing that fixed it for me was to change WPA2/WPA3 to just old fashioned WPA2, it also disabled WiFi7 in the process but all my devices have connected back and speeds are good again too.
Must be that some of the IOT devices didn't like the WPA2/WPA3 setting.

Just to add, running latest Merlin too.

Yes, this.
I use a ‘no frills’ guest network for IoT stuff, WPA2, no Wifi 7.
Just works….

 

[phillyaj]

I ran through a very similar process, RT-AC86U to RT-BE88U and the thing that fixed it for me was to change WPA2/WPA3 to just old fashioned WPA2, it also disabled WiFi7 in the process but all my devices have connected back and speeds are good again too.
Must be that some of the IOT devices didn't like the WPA2/WPA3 setting.

Just to add, running latest Merlin too.

So did you just make your IoT network WPA2, or did you switch your main 2.4Ghz network to WPA2? Seems like there is multiple ways to go here. I'm thinking of setting up a dedicated IOT network, on a separate subnet for my IoT devices...then the fun task of re-connecting them all. Not sure how I want to progress yet..

 

[Tech9]

Which IoT device supports WPA3 anyway?

 

[Dakar]

So did you just make your IoT network WPA2, or did you switch your main 2.4Ghz network to WPA2? Seems like there is multiple ways to go here. I'm thinking of setting up a dedicated IOT network, on a separate subnet for my IoT devices...then the fun task of re-connecting them all. Not sure how I want to progress yet..

Yeah I went with main network to WPA2 to test and low and behold it worked.
Its a weekend job now to go and reset/reconnect all the older devices (mostly IOT) to a new IOT network with just the WPA2 and then re-enable WPA2/WPA3 on the main again and get Wifi7 back up and running.

 

[Tech9]

WPA2/WPA3

WPA3 makes sense if you have WPA3 only network. Otherwise not really more secure.

 

[Krism]

I'm struggling with exact the same issues on RT_BE88U running Merlin 3006.102_2. Also have the kernel errors. After some wifi setting changes I always have to reboot because wifi is not working anymore.
IOT devices issues also happening. I created a second IOT guest network but it never broadcasts. I cannot delete the default IOT guest network (don't have a delete button).

When I have some spare time (and nobody at home) I'm going back to the new stock FW and see of things are better.

 

[Treadler]

I'm struggling with exact the same issues on RT_BE88U running Merlin 3006.102_2. Also have the kernel errors. After some wifi setting changes I always have to reboot because wifi is not working anymore.
IOT devices issues also happening. I created a second IOT guest network but it never broadcasts. I cannot delete the default IOT guest network (don't have a delete button).

When I have some spare time (and nobody at home) I'm going back to the new stock FW and see of things are better.

My non default guest network/s stopped advertising/broadcasting. A lot of wasted time trying to figure out why IoT devices stopped working.
Spent a happy morning putting them onto the default network………

This is with factory firmware, 37094.

 

[Krism]

My non default guest network/s stopped advertising/broadcasting. A lot of wasted time trying to figure out why IoT devices stopped working.
Spent a happy morning putting them onto the default network………

This is with factory firmware, 37094.

That's not good news.
Did you do a factory reset?

 

[Treadler]

That's not good news.
Did you do a factory reset?

No.
Did a quick install of Merlin, just to make sure it wasn’t a ‘factory only’ problem, then reverted to stock & revamped my IoT stuff. All good now.

[Edit] see message #20 below.

 

[Treadler]

I'm struggling with exact the same issues on RT_BE88U running Merlin 3006.102_2. Also have the kernel errors. After some wifi setting changes I always have to reboot because wifi is not working anymore.
IOT devices issues also happening. I created a second IOT guest network but it never broadcasts. I cannot delete the default IOT guest network (don't have a delete button).

When I have some spare time (and nobody at home) I'm going back to the new stock FW and see of things are better.

FWIW, I deleted my non default guest networks, & recreated them. Same SSID, passcodes etc. They are now broadcasting/advertising. Maybe I should’ve thought of doing that yesterday, sigh…….