Struggling with Asus ZenWiFi BE30000 aka 3 node BQ16 Pro bundle

[skypx]

Thanks that's really helpful - do you think it would be possible to also add an AiMESH capabile router XT12 or Xt 8 in AIMesh node...to a network with AP's?

I have no idea, sorry. I just have the 3 bq16 pros with a router and 2 APs.

 

[garysteel]

I have no idea, sorry. I just have the 3 bq16 pros with a router and 2 APs.

NO worries, I'll AP my system...leave it to prove itself and then play and let you know if I do

 

[jzchen]

Thanks that's really helpful - do you think it would be possible to also add an AiMESH capabile router XT12 or Xt 8 in AIMesh node...to a network with AP's?

My primary router is a DECO BE95, (AT&T Gateway in IP Passthrough). 100% my GT-BE98 Pro is in Access Point Mode with AiMesh and can add nodes. You'd have to choose which AP to mesh with, and you'd lose mesh to the other AP.

 

[garysteel]

I have no idea, sorry. I just have the 3 bq16 pros with a router and 2 APs.

Hi.. on my way home to delete the bq16 node in aimesh then reset to ap …does the following sound right
1. Disable node
2. Reboot reset node and log onto it via 192.168.50.1
3. Select op mode as access point
4. auto ip
5. Main ssid will be copied so its the same as main router
Reboot
Or is there something else todo and do i still have to add it as aimesh but as ap or will it naturally settle itself into my 192.168.0.1 setup.

Do i have to keep 5ghz-2 seperate for this or can i utilise all available bands?

Thanks

 

[skypx]

The bq16 pro that is setup as a node needs to be connected to the internet and then reset via the reset button on the bottom of the device (Press and hold for 10 seconds). So, in other words, you need to go through the normal setup process like it's going to be used as a router, and then when asked how the device is going to be used select Access Point Mode. If you simply reset it, it will remain the node config when it restarts.

 

[garysteel]

The bq16 pro that is setup as a node needs to be connected to the internet and then reset via the reset button on the bottom of the device (Press and hold for 10 seconds). So, in other words, you need to go through the normal setup process like it's going to be used as a router, and then when asked how the device is going to be used select Access Point Mode. If you simply reset it, it will remain the node config when it restarts.

thanks for this.......all done 2nd BQ16 now in AP mode, wifi 7 diabled as well as MLO unitil i get an all good consistent sign from Mrs....having to re-idenitify all connect devices is painful for sure....is there anything else to do...I assume i leave like this and not try to setup AiMesh to too !!! i don't think so but just in case i'm being a tad stoopid

 

[skypx]

thanks for this.......all done 2nd BQ16 now in AP mode, wifi 7 diabled as well as MLO unitil i get an all good consistent sign from Mrs....having to re-idenitify all connect devices is painful for sure....is there anything else to do...I assume i leave like this and not try to setup AiMesh to too !!! i don't think so but just in case i'm being a tad stoopid

You’re welcome. FYI disabling WiFi 7 and MLO makes no difference for IOS devices, based on my testing. Just remember whatever changes you make on the router (SSIDs) you need to do the same on the AP. This will ensure roaming works the way it should.

 

[garysteel]

You’re welcome. FYI disabling WiFi 7 and MLO makes no difference for IOS devices, based on my testing. Just remember whatever changes you make on the router (SSIDs) you need to do the same on the AP. This will ensure roaming works the way it should.

Yes… but it buggers up my sonos, dyson fan , legacy stuff… as they hate the wpa3 aspect of 7. MLO off due to its rep… if wifi works now consistently i can build up to better exploitation of the 16’s capability.

 

[skypx]

Yes… but it buggers up my sonos, dyson fan , legacy stuff… as they hate the wpa3 aspect of 7. MLO off due to its rep… maybe line i says if wifi works now consistently i can build up to better exploitation of the 16’s capability

I hear you, same issue here with our sonos . After this experience I can’t wait to find something that works so I can rid our lives of crappy asus devices.

 

[garysteel]

There appears to be (to me) an oddity, which is likely to be expected but if my Iphone connects via the access point node and I'm looking at the main router login, the iphone shows connected as if via wired connection via the main router and reports on the node as via Wifi...I suppose this make logical sense and I am so used to a single mind (AiMESH) managing and showing all connections.

As they're BQ16's UK with 2.4, 5-1,5-2 & 6 but even connected via AP mode it still reserves my 5Ghz-2 band. SHould I leave as is or do something to make it part of the love round th house?

Regards ALL

 

[skypx]

There appears to be (to me) an oddity, which is likely to be expected but if my Iphone connects via the access point node and I'm looking at the main router login, the iphone shows connected as if via wired connection via the main router and reports on the node as via Wifi...I suppose this make logical sense and I am so used to a single mind (AiMESH) managing and showing all connections.

As they're BQ16's UK with 2.4, 5-1,5-2 & 6 but even connected via AP mode it still reserves my 5Ghz-2 band. SHould I leave as is or do something to make it part of the love round th house?

Regards ALL

Yes all wireless devices connected to the AP will appear as wired on the router and asus app. Also the only other wireless network available on the AP is the kids network, I use this as our guest network. The bq16 pro only has 1 5Ghz band and 2 6Ghz bands. 6-2 is reserved as well, not sure why, maybe it’s by design?

 

[bkayrac]

Yes all wireless devices connected to the AP will appear as wired on the router and asus app. Also the only other wireless network available on the AP is the kids network, I use this as our guest network. The bq16 pro only has 1 5Ghz band and 2 6Ghz bands. 6-2 is reserved as well, not sure why, maybe it’s by design?

I can connect to every band on bq16 pro's. 6-2, 6-1, 2.4, 5. Perhaps you don't have it enabled in the network settings for that wifi network? If I remember right, it was by default not checked

 

[bkayrac]

My settings for the main network, and my PC currently on 6-2

 

[garysteel]

View attachment 62836View attachment 62837

My settings for the main network, and my PC currently on 6-2

It maybe due the fact that I had originally had it in AiMesh mode the deleted the node and reconnected to the master via AP mode so its reserved the 2nd backhaul wifi band (in my case the 5Ghz-1 for us its the 6Ghz-2) so perhaps I should just enable as I hope that I do not need to separately connect my old XT8 or Xt12 to cover the garden ...Thank you

 

[bkayrac]

It maybe due the fact that I had originally had it in AiMesh mode the deleted the node and reconnected to the master via AP mode so its reserved the 2nd backhaul wifi band (in my case the 5Ghz-1 for us its the 6Ghz-2) so perhaps I should just enable as I hope that I do not need to separately connect my old XT8 or Xt12 to cover the garden ...Thank you

Yeah, mine is working alright. One thing i've noticed is make sure whenever you modify any of the network settings that drop the connection. Wait until everything is back up, and then do a full reboot of everything. It seems to fix the odd issues that are seen after changing settings.

Pain in the butt, but

 

[skypx]

View attachment 62836View attachment 62837

My settings for the main network, and my PC currently on 6-2

I have the same setup except for the 2.4Ghz band, and based on the asus app, all wireless devices would only connect to the 6-1/5Ghz bands. I also do the reboot after changes.

 

[A011528]

Well sadly some problems have emerged and I've only just noticed (since I took on another 2 BQ16's (total 4)) as i was traveling, so I've only just noticed on my return.

• Sonos devices are no longer visible in the Sonos App (but they are working i can hear them )
• I'm now getting the intermittent drop out again, on IOS devices , but its now hitting Win / Unix also (feels like intermittent DNS) .
  

I've found these two articles ref Sonos and an App update they made that moves away from SSDP (UPnP) to mDNS Here and Here i fear I'm about to go down another rabbit hole, has anyone looked at this ?... i read that some have solved this by enabling the IOT SSID and connecting their Sonos equipment to this - can anyone confirm a fix or another path ? as that doesn't feel like a solution

On the Internet drop-outs im calling this "DNS" as that is what it feels like, I've read to remove the devices from mesh and them as AP's instead are there any other steps that have helped anyone ?

 

[bkayrac]

Well sadly some problems have emerged and I've only just noticed (since I took on another 2 BQ16's (total 4)) as i was traveling, so I've only just noticed on my return.

• Sonos devices are no longer visible in the Sonos App (but they are working i can hear them )
• I'm now getting the intermittent drop out again, on IOS devices , but its now hitting Win / Unix also (feels like intermittent DNS) .

I've found these two articles ref Sonos and an App update they made that moves away from SSDP (UPnP) to mDNS Here and Here i fear I'm about to go down another rabbit hole, has anyone looked at this ?... i read that some have solved this by enabling the IOT SSID and connecting their Sonos equipment to this - can anyone confirm a fix or another path ? as that doesn't feel like a solution

On the Internet drop-outs im calling this "DNS" as that is what it feels like, I've read to remove the devices from mesh and them as AP's instead are there any other steps that have helped anyone ?

I’ve narrowed down some of the issues to DNS issues as well, if I use quad9s dns, it often messes up shortly after, or a bit after. Using the dns supplied by my isp is sometimes finicky.

I finally settled on cloud flares, and haven’t seen any issues in about 1.5 days now. It’s possible it’s all unrelated but, I’m keeping an eye on it.

 

[Bandito]

Well sadly some problems have emerged and I've only just noticed (since I took on another 2 BQ16's (total 4)) as i was traveling, so I've only just noticed on my return.

• Sonos devices are no longer visible in the Sonos App (but they are working i can hear them )
• I'm now getting the intermittent drop out again, on IOS devices , but its now hitting Win / Unix also (feels like intermittent DNS) .

I've found these two articles ref Sonos and an App update they made that moves away from SSDP (UPnP) to mDNS Here and Here i fear I'm about to go down another rabbit hole, has anyone looked at this ?... i read that some have solved this by enabling the IOT SSID and connecting their Sonos equipment to this - can anyone confirm a fix or another path ? as that doesn't feel like a solution

On the Internet drop-outs im calling this "DNS" as that is what it feels like, I've read to remove the devices from mesh and them as AP's instead are there any other steps that have helped anyone ?

I was experiencing an issue with a SONOS Arc that would simply not connect to my main WiFi 7 network. While this was happening, I remembered a little Internet clock that I had that quit working when I upgraded the network to the BQ16 Pros (two, in my case), so I decided to set up the IoT network for the clock. I initially had a bunch of problems with the IoT network, but they resolved when I set it up for 2.4 and 5 GHz and had it create an entirely separate subnet for the IoT network. Doing that got the clock connecting and working again.

So, back to the SONOS Arc, since it wouldn’t connect to the main WiFi 7 network, I decided to try the IoT network with it and, low and behold, it worked just fine there, so I moved the sub and surrounds over and the SONOS system worked great with the exception that I couldn’t AirPlay to the speakers unless I also change the source’s network to the IoT network. Not ideal, but at least the speakers were all up and running. Then, this last Saturday, I was playing around with the speakers and there was a software update, so I let everything update and then quit playing around with them as I had a Level 3 support call for the Arc arranged for Monday. In that call, we tried several things and looked through some log files, but didn’t really find a smoking gun as to why the Arc wouldn’t connect to the main network. We tried moving the Arc to the main network through the app, but got a failure message, so I connected the Arc to the network via a cable and let it sit for a while. With one of the other support techs, we tried this previously, but once the network cable was disconnected, the Arc still would not connect to the WiFi 7 main network. However, after I finished the support call and disconnected the Arc and prepared to put it back on the IoT network, it magically restarted and joined the main network! So, all I can think is that something in the latest update fixed whatever issue I was having. Now I have two rooms of SONOS speakers all on the main network and everything is working as designed.

With all of that said, if you select the checkbox for keeping the same subnet on your IoT network, you should be able to connect your SONOS system to the IoT network, and since they are all pulling similar addresses from the same DHCP server, you should still be able to AirPlay to them from your devices on the main network. I was going to verify this as a next step in my troubleshooting journey, but wound up not needing to do so once the Arc connected to the main network.

As far as the DNS issue goes, what I’ve typically experienced is that when the device first connects to the network, everything is okay for about a minute and then, while it stays connected to WiFi, the device gets no response from the router or an external DNS server. Disconnecting and reconnecting WiFi will either start the cycle again or after a few tries the connection to the router will remain stable. This problem seems to happen to me mostly when the mesh system has just been restarted and seems like it stabilizes and goes away with some uptime on the router. Though it can occasionally crop up again randomly.

While going through my configuration again for the umpteenth time yesterday, I found that I forgot to limit my IP address range so that my fixed IP address devices near the top of the range would be excluded. I don’t know yet if this will make any difference with the non-responsive router situation, but if I was having address conflicts who knows what havoc that could cause. I am cautiously optimistic that things will now be stable, but only some more time will tell.

I hope that some of this information may be of use to you, A011528.

Good luck on your journey.

 

[A011528]

I was experiencing an issue with a SONOS Arc that would simply not connect to my main WiFi 7 network. While this was happening, I remembered a little Internet clock that I had that quit working when I upgraded the network to the BQ16 Pros (two, in my case), so I decided to set up the IoT network for the clock. I initially had a bunch of problems with the IoT network, but they resolved when I set it up for 2.4 and 5 GHz and had it create an entirely separate subnet for the IoT network. Doing that got the clock connecting and working again.

So, back to the SONOS Arc, since it wouldn’t connect to the main WiFi 7 network, I decided to try the IoT network with it and, low and behold, it worked just fine there, so I moved the sub and surrounds over and the SONOS system worked great with the exception that I couldn’t AirPlay to the speakers unless I also change the source’s network to the IoT network. Not ideal, but at least the speakers were all up and running. Then, this last Saturday, I was playing around with the speakers and there was a software update, so I let everything update and then quit playing around with them as I had a Level 3 support call for the Arc arranged for Monday. In that call, we tried several things and looked through some log files, but didn’t really find a smoking gun as to why the Arc wouldn’t connect to the main network. We tried moving the Arc to the main network through the app, but got a failure message, so I connected the Arc to the network via a cable and let it sit for a while. With one of the other support techs, we tried this previously, but once the network cable was disconnected, the Arc still would not connect to the WiFi 7 main network. However, after I finished the support call and disconnected the Arc and prepared to put it back on the IoT network, it magically restarted and joined the main network! So, all I can think is that something in the latest update fixed whatever issue I was having. Now I have two rooms of SONOS speakers all on the main network and everything is working as designed.

With all of that said, if you select the checkbox for keeping the same subnet on your IoT network, you should be able to connect your SONOS system to the IoT network, and since they are all pulling similar addresses from the same DHCP server, you should still be able to AirPlay to them from your devices on the main network. I was going to verify this as a next step in my troubleshooting journey, but wound up not needing to do so once the Arc connected to the main network.

As far as the DNS issue goes, what I’ve typically experienced is that when the device first connects to the network, everything is okay for about a minute and then, while it stays connected to WiFi, the device gets no response from the router or an external DNS server. Disconnecting and reconnecting WiFi will either start the cycle again or after a few tries the connection to the router will remain stable. This problem seems to happen to me mostly when the mesh system has just been restarted and seems like it stabilizes and goes away with some uptime on the router. Though it can occasionally crop up again randomly.

While going through my configuration again for the umpteenth time yesterday, I found that I forgot to limit my IP address range so that my fixed IP address devices near the top of the range would be excluded. I don’t know yet if this will make any difference with the non-responsive router situation, but if I was having address conflicts who knows what havoc that could cause. I am cautiously optimistic that things will now be stable, but only some more time will tell.

I hope that some of this information may be of use to you, A011528.

Good luck on your journey.

OK Sonos issue solved! I pulled a temp long ethernet cable to the Arc then it became visible on the network and the App (no system updates) then I updated the WIFI and unplugged the ethernet and boom, it was on the WIFI and was able to reconnect the Sub. Solution temp network cable, update the WIFI and done (no need for the IOT network.

So Thank you!

now on to solve the "DNS"