Struggling with Asus ZenWiFi BE30000 aka 3 node BQ16 Pro bundle

[skypx]

Will post if I make the change - and thanks for the update. This is one long journey thats for sure.

I have switched the APs back to nodes, I’m really hoping for the best, but we’ll see how it goes.

 

[NovaPrime]

Alright its been multiple weeks at this point i am happy to report my issues have been solved with the latest update. dnsmasq is no longer throwing up resolve errors. wife also hasnt complained once that her macbook or iphone have dropped connection. i also havent personally noticed any issues. Asus finally fixed it so hopefully others can also report back the same. one other thing after this latest update i no longer to have auto reboot every other night. thanks everyone for the help and reports on this one.

 

[JohnNadeau]

Alright its been multiple weeks at this point i am happy to report my issues have been solved with the latest update

Good to know! Thanks for the update @NovaPrime !

 

[NovaPrime]

And.. we just hit 10 days with no issues. I am finally happy with this purchase.

 

[garysteel]

I have switched the APs back to nodes, I’m really hoping for the best, but we’ll see how it goes.

I'm also back in AiMesh Mode (BQ16s) only 2.5 days though but so far so good, I've held off adding my XT8's into the mix until I have at least a week on no issues, but so far so good.

 

[skypx]

I'm also back in AiMesh Mode (BQ16s) only 2.5 days though but so far so good, I've held off adding my XT8's into the mix until I have at least a week on no issues, but so far so good.

Today is my 6th day with no disconnections so far.

 

[garysteel]

Today is my 6th day with no disconnections so far.

I wonder what the specific issue was that affected just apple devices??

 

[skypx]

I wonder what the specific issue was that affected just apple devices??

For us it wasn’t just IOS devices. I switched back to node mode on firmware version 3.0.0.6.102_36869 and our Bose soundbar disconnected while watching tv. So yeah, no idea why.

 

[Momo80]

I found out that I have to exclude the 2.4ghz band from my main network even though I have a separate Iot Network set up. i.e main network only has 5 & 6ghz bands.

Disconnects stops occurring once I do so. Enabling the 2.4ghz band in my main network causes the devices in my iot network to disconnect.

 

[skypx]

And.. we just hit 10 days with no issues. I am finally happy with this purchase.

Hello, I’m assuming your BQ16 Pros and still working as intended. 2 quick questions, do you have MLO enabled and are the nodes connected to the network wirelessly or wired? Thanks

 

[NovaPrime]

Hello, I’m assuming your BQ16 Pros and still working as intended. 2 quick questions, do you have MLO enabled and are the nodes connected to the network wirelessly or wired? Thanks

Wireless mesh and mlo is enabled for backhaul for the nodes.

 

[NovaPrime]

Wireless mesh and mlo is enabled for backhaul for the nodes.

@skypx here is what it looks like in the app.

 

[skypx]

@NovaPrime Nice!

 

[linutic]

Hey folks - I found this forum a few weeks ago when troubleshooting some issues with my previous Asus mesh network, and based on threads here and the review on Dong Knows Tech, I decided to pull the trigger and buy the Asus ZenWifi BE30000 from BestBuy. The layout of my house makes running an ethernet backhaul extremely difficult, and given the ages of my kids I don't exactly have a couple of weeks free to get it done. Long story short, for me, wireless backhaul is the best option, and I was excited by the speed and reliability gains with Wifi 7 + MLO.

Since setting it up, I've been struggling with stability issues, wifi drops, unexpected reboots, and general frustration. I dug through these forums to find recommended settings for IOT (I have a lot of Wiz2 and Feit bulbs, as well as ring security accessories) to maximize compatibility.

I work in tech, but am not great at networking - but I've been hyperfixating on my wireless challenges for weeks.

Here's my rough timeline:
- Tried initial setup through app, created Wifi 7 network with MLO that had the same SSID as my previous mesh wifi network - my previous mesh setup was an XT8 system, also with 2 nodes.
- Nothing could connect, I setup additional networks, still struggled - so I did a hard factory reset
- Started fresh - again, Wifi 7 network with MLO, using original SSID, setup separate 2.4ghz only IoT network, manually reset every device to connect to IOT network with new SSID (OldNetworkName_Lights)
- Still getting random reboots on main router and nodes, nodes losing connectivity, lights randomly dropping connections even when network is otherwise up
- Read here that DHCP can get hairy with so many devices, so went through and manually assigned all IOT devices a static ip
- Still having issues, tried recommended config for 2.4ghz network (see attached screenshot)
- While sitting here tonight, my router rebooted again for an unknown reason, and lights still aren't working

Does anyone have any recommendations? I can provide more info as needed, sharing screenshots of config / networks with SSID blurred

First, system log:

Jul  3 20:40:42 rc_service: ntp 5217:notify_rc restart_diskmon
Jul  3 20:40:42 disk_monitor: Finish
Jul  3 20:40:42 disk monitor: be idle
Jul  3 20:40:42 wlceventd: wlceventd_proc_event(685): wl3.1: Auth C8:69:CD:7F:8F:21, status: Successful (0), rssi:-58
Jul  3 20:40:42 kernel: SBF: dhd3: INIT [c8:69:cd:7f:8f:21] ID 65535 BFW 65535 THRSH 2048
Jul  3 20:40:42 wlceventd: wlceventd_proc_event(722): wl3.1: Assoc C8:69:CD:7F:8F:21, status: Successful (0), rssi:-58
Jul  3 20:40:42 wan_up: Restart DDNS
Jul  3 20:40:43 dhcp client: bound 24.143.53.187/255.255.255.0 via 24.143.53.1 for 86400 seconds.
Jul  3 20:40:43 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind CC:50:E3:1F:E1:E1, status: 0, reason: Unspecified reason (1), rssi:0
Jul  3 20:40:43 wlceventd: wlceventd_proc_event(685): wl3.1: Auth CC:50:E3:1F:E1:E1, status: Successful (0), rssi:-62
Jul  3 20:40:43 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind A8:51:AB:CB:CC:CF, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:-69
Jul  3 20:40:43 kernel: WLC_SCB_DEAUTHORIZE error (-30)
Jul  3 20:40:43 wlceventd: wlceventd_proc_event(662): wl3.1: Disassoc A8:51:AB:CB:CC:CF, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-69
Jul  3 20:40:44 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind 5C:CF:7F:75:6D:46, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Jul  3 20:40:44 wlceventd: wlceventd_proc_event(685): wl3.1: Auth 5C:CF:7F:75:6D:46, status: Successful (0), rssi:0
Jul  3 20:40:44 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind A8:51:AB:CB:CC:CF, status: 0, reason: Unspecified reason (1), rssi:0
Jul  3 20:40:44 wlceventd: wlceventd_proc_event(685): wl3.1: Auth A8:51:AB:CB:CC:CF, status: Successful (0), rssi:0
Jul  3 20:40:44 crond[3833]: time disparity of 266499 minutes detected
Jul  3 20:40:44 kernel: SBF: dhd3: INIT [a8:51:ab:cb:cc:cf] ID 65535 BFW 65535 THRSH 2048
Jul  3 20:40:44 wlceventd: wlceventd_proc_event(722): wl3.1: Assoc A8:51:AB:CB:CC:CF, status: Successful (0), rssi:-69
Jul  3 20:40:44 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind C4:82:E1:A8:45:A6, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:-64
Jul  3 20:40:44 wlceventd: wlceventd_proc_event(662): wl3.1: Disassoc C4:82:E1:A8:45:A6, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-64
Jul  3 20:40:44 kernel: WLC_SCB_DEAUTHORIZE error (-30)
Jul  3 20:40:44 wlceventd: wlceventd_proc_event(685): wl3.1: Auth C4:82:E1:A8:65:3B, status: Successful (0), rssi:-61
Jul  3 20:40:44 kernel: SBF: dhd3: INIT [c4:82:e1:a8:65:3b] ID 65535 BFW 65535 THRSH 2048
Jul  3 20:40:44 wlceventd: wlceventd_proc_event(722): wl3.1: Assoc C4:82:E1:A8:65:3B, status: Successful (0), rssi:-61
Jul  3 20:40:45 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind C4:82:E1:42:3F:54, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:-51
Jul  3 20:40:45 wlceventd: wlceventd_proc_event(662): wl3.1: Disassoc C4:82:E1:42:3F:54, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-51
Jul  3 20:40:45 kernel: WLC_SCB_DEAUTHORIZE error (-30)
Jul  3 20:40:45 wlceventd: wlceventd_proc_event(645): wl3.2: Deauth_ind 10:D5:61:55:0F:60, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Jul  3 20:40:45 wlceventd: wlceventd_proc_event(662): wl3.2: Disassoc 10:D5:61:55:0F:60, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jul  3 20:40:45 wlceventd: wlceventd_proc_event(645): wl3.2: Deauth_ind 10:D5:61:78:14:88, status: 0, reason: Unspecified reason (1), rssi:0
Jul  3 20:40:45 wlceventd: wlceventd_proc_event(685): wl3.2: Auth 10:D5:61:78:14:88, status: Successful (0), rssi:0
Jul  3 20:40:45 wlceventd: wlceventd_proc_event(685): wl3.2: Auth 10:D5:61:55:0F:60, status: Successful (0), rssi:0
Jul  3 20:40:45 kernel: SBF: dhd3: INIT [10:d5:61:78:14:88] ID 65535 BFW 65535 THRSH 2048
Jul  3 20:40:45 wlceventd: wlceventd_proc_event(722): wl3.2: Assoc 10:D5:61:78:14:88, status: Successful (0), rssi:-60
Jul  3 20:40:45 kernel: SBF: dhd3: INIT [10:d5:61:55:0f:60] ID 65535 BFW 65535 THRSH 2048
Jul  3 20:40:45 wlceventd: wlceventd_proc_event(722): wl3.2: Assoc 10:D5:61:55:0F:60, status: Successful (0), rssi:-76
Jul  3 20:40:46 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind 50:DC:E7:2A:B6:5C, status: 0, reason: Unspecified reason (1), rssi:0
Jul  3 20:40:46 wlceventd: wlceventd_proc_event(685): wl3.1: Auth 50:DC:E7:2A:B6:5C, status: Successful (0), rssi:0
Jul  3 20:40:46 kernel: SBF: dhd3: INIT [50:dc:e7:2a:b6:5c] ID 65535 BFW 65535 THRSH 2048
Jul  3 20:40:46 wlceventd: wlceventd_proc_event(722): wl3.1: Assoc 50:DC:E7:2A:B6:5C, status: Successful (0), rssi:-43
Jul  3 20:40:47 kernel: SBF: dhd3: INIT [c4:38:75:98:ca:22] ID 65535 BFW 65535 THRSH 2048
Jul  3 20:40:47 wlceventd: wlceventd_proc_event(722): wl3.1: Assoc C4:38:75:98:CA:22, status: Successful (0), rssi:-49
Jul  3 20:40:47 kernel: SBF: dhd3: INIT [10:7c:61:6d:f6:31] ID 65535 BFW 65535 THRSH 2048
Jul  3 20:40:47 wlceventd: wlceventd_proc_event(722): wl3: Assoc 10:7C:61:6D:F6:31, status: Successful (0), rssi:-48
Jul  3 20:40:47 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind CC:50:E3:1F:E1:E1, status: 0, reason: Unspecified reason (1), rssi:0
Jul  3 20:40:47 wlceventd: wlceventd_proc_event(685): wl3.1: Auth CC:50:E3:1F:E1:E1, status: Successful (0), rssi:0
Jul  3 20:40:47 kernel: wfd_registerdevice Successfully registered dev wds3.0.1 ifidx 3 wfd_idx 3
Jul  3 20:40:47 kernel: Register interface [wds3.0.1]  MAC: 10:7c:61:6d:ea:90
Jul  3 20:40:47 kernel: SBF: dhd3: INIT [10:7c:61:6d:f6:31] ID 65535 BFW 65535 THRSH 2048
Jul  3 20:40:48 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind 5C:CF:7F:75:6D:46, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Jul  3 20:40:48 wlceventd: wlceventd_proc_event(685): wl3.1: Auth 5C:CF:7F:75:6D:46, status: Successful (0), rssi:0
Jul  3 20:40:48 wlceventd: wlceventd_proc_event(685): wl3: Auth 10:7C:61:6D:E6:11, status: Successful (0), rssi:-39
Jul  3 20:40:48 wlceventd: wlceventd_proc_event(645): wl3: Deauth_ind 10:7C:61:6D:E6:11, status: 0, reason: Previous authentication no longer valid (2), rssi:-39
Jul  3 20:40:48 kernel: WLC_SCB_DEAUTHORIZE error (-30)

 

[skypx]

@linutic Can you take it back to the store for a refund?

 

[garysteel]

I'm also back in AiMesh Mode (BQ16s) only 2.5 days though but so far so good, I've held off adding my XT8's into the mix until I have at least a week on no issues, but so far so good.

Again no issues, with x2 BQ16s 1 master and 1 AiMesh wired backhaul, now going for adding XT12 in AiMesh wireless node. Will be looking to see if this upsets the current balance and working then see how that performs from the shed (supporting wifi in the garden)

 

[kraken206]

Switched my main BQ16 Pro to router with AI Mesh and wireless MSO backhaul -- and decommissioned my old Asus RT-AC86U router/mesh.

So far so good and thanks for the updates -- glad this appears to be resolved!

 

[kraken206]

All devices working well including Apple and Sonos.

For Sonos was having problems with grouped audio (5 rooms) and lag but split out the front haul to separate 2.4/5/6 GHz SSIDs (on the same main network) and put all Sonos devices on that separate 2.4 GHz SSID:
- set to 20 MHz width only (less interference/more distance)
- disabled Wifi7 (just in case for older Sonos Play 1)
- bound all of the Sonos speakers to the parent router node (may not matter but they were there already).
- set manual/static DHCP reservations (MAC/IP) for all Sonos speakers — note Sonos desktop app “about my system” has serial numbers that include MAC (replace '-' with ':') and IP so it’s easy to populate the manual DCHP reservations with that esp. since bind MAC/IP toggle button in AI Mesh page wasn’t showing up for wireless devices - use LAN/DHCP manual settings for this.
- also note the backhaul MLO excludes 2.4 GHz so 2.4 GHz is entirely for Sonos speakers (main network) plus any IOT network devices that are using 2.4 GHz.

Key for Sonos S2+ is to enable multicast (not default) and ensure IGMP snooping is enabled (default). After this playing all Sonos speakers grouped together has been flawless.

Also for Sonos, if you have a single Sonos speaker wired to Ethernet it will enable SonosNet for all Sonos speakers which is the old Sonos mesh network that gets created alongside the Asus mesh. Found this out by hardwiring my Arc thinking it would help (nope).

To ditch SonosNet (old Sonos mesh network):
- ensured no Sonos speakers were hardwired via Ethernet
- created a new Sonos System
- ensured all the speakers were connected via Asus 2.4 SSID (see config above) on main network

So glad I ditched SonosNet esp. now that BQ16 Pros are stable.

more info here for folks with Sonos:

Common fixes on a home network for mDNS (new Sonos App/device protocol)
by u/LegitimateDocument88 in sonos