Contributor I

Asus ZenWiFi AX rotuer QoS feature doesn't work with Sonos

Forum|Forum|5 years ago
January 27, 2021
34 replies
15125 views

If you have one of those Asus routers which support Quality of Service (QoS) feature to prioritize different kind of traffic (Streaming, Work from Home, etc.), this may be helpful to you. When I enabled this feature I had lot of issues with connecting to various Sonos speakers, or playing music on them, or adding a new speaker to the system, etc. Once I disabled QoS feature in the router, everything worked seamlessly.

I have ASUS ZenWiFi AX6600 (XT8) router.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

Pinned Reply By Naveed.Ahmad

Problem Solved: I am glad to announce that all my Sonos speakers are now working fine with Asus Zen WiFi XT8 router. Here is what I did.

Asus released a new firmware 3.0.0.4.386_41793, but against all my hopes that did not fix it either. I then did a Factory Reset on the router. Set my WiFi’s name and password the same as before. And all my devices including all my Sonos speakers are connecting fine and playing music fine with WiFi.

I no longer need to connect one of the speakers through Ethernet cable to make the rest connect through SononNet network as the workaround.

Hope this solves the problem for all of you guys.

PS. I thought about doing a factory reset because my secondary node kept on disconnecting and flashing green light after the firmware version 41793. Factory reset solved that problem too.

Show previous replies

M

Minimos

Lyricist III

Ok last update from me, hopefully will help others in a similar position who have not been lucky enough for a factory reset to resolve issues.

I disabled the Play:5 on S1 to see if that was interfering, rebooted all devices and it made no difference.

I then re-enabled the multicast LAN option, the Beam started working again with Alexa voice commands and responding to volume control from the app.

However, I could not play a music service to the Beam, I either get non Sonos product found or can’t add to queue error messages. This is the same for local sources and remote like Deezer, Sonos Radio etc

All the other Sonos devices in the house can stream music from services, and be grouped etc.

Adding in the Play:5 back into the mix did not break anything else, so I can rule the mix and match of Sonos software out as the problem.

I think, I’ve narrowed it down to the new firmware not being able to handle a system configured with surround speakers.

I’m leaving the cable in for now as it all works as it should, I’m lucky that my Beam is near a switch in the entertainment system, but its really annoying that I am so close to having it back as it was on 25790

D

Docadams91b

Lyricist I

I have Asus ZenWiFi AX…. got it up and working, then connected Arc, Sub, and surrounds. All worked great. Then made the mistake of updating firmware to 3.0.0.4.386_41793. Probably 5 mins later system wasn’t able to be detected. Quick internet search got me to this forum. Reset back to factory reset… and works perfectly (all wifi). Not really too excited to start messing with things again at this time. But there’s something about that update it doesn’t like.

B

Blue Xerxes

Lyricist I

Problem Solved: I am glad to announce that all my Sonos speakers are now working fine with Asus Zen WiFi XT8 router. Here is what I did.

Asus released a new firmware 3.0.0.4.386_41793, but against all my hopes that did not fix it either. I then did a Factory Reset on the router. Set my WiFi’s name and password the same as before. And all my devices including all my Sonos speakers are connecting fine and playing music fine with WiFi.

I no longer need to connect one of the speakers through Ethernet cable to make the rest connect through SononNet network as the workaround.

Hope this solves the problem for all of you guys.

PS. I thought about doing a factory reset because my secondary node kept on disconnecting and flashing green light after the firmware version 41793. Factory reset solved that problem too.

Just remember that a factory reset wouldn’t help if you’ve already updated your router (it has already written over your “out of the box” firmware). What you need to do is to downgrade to an older version of the firmware. For example, it seems that version 25790 is the last working one without any troubles for Sonos speakers. Find all the Asus firmwares here:

https://www.asus.com/Networking-IoT-Servers/Whole-Home-Mesh-WiFi-System/ZenWiFi-WiFi-Systems/ASUS-ZenWiFi-AX-XT8-/HelpDesk_BIOS/

B

BrianR77

Lyricist I

I have also been running firmware 3.0.0.4.386_41793 and was having disconnect issues on only 2 of my 5 speakers. I was working with Sonos support for about a week trying various things to resolve. Yesterday I did a factory reset and so far the disconnect issues have not reoccurred.

G

Gloriousdead

Contributor I

After having upgraded my XT8’s (1 router + 2 nodes) to latest firmwared 3.0.0.4.386_4179 I encountered the exact same problems you all seem to be having. I did try the factory reset, both via UI and via the WPS-button but with no joy. I then decided to downgrade back to version 25790 and now it’s all FINALLY working again (and I don’t think I lost too many settings going from latest fw to 25790). For me it seems the only way was to downgrade again, and hey, with this thing now working, I do think the XT8 is otherwise a great system so I really hope ASUS work this issue out for the next release of firmware version!!!

O

Orlanzo_1

Contributor I

I have firmware version ...41793 installed on both the router and satellites. Disabling QOS resoled the issue for me.

Fortunately, I can return my old Sonos Bridge to the recycle bin as I don’t have an ethernet port convenient to my speaker locations.

P

pompeygreg

Trending Lyricist I

Factory reset seems to have resolved the issue for me. Thanks guys, it had been driving me insane!

W

Whatswong

Lyricist I

This worked for me. ymmv.
Environment: 2 AX8 + AC68U (1 AX8 in router mode). QoS and AirTime Fairness not enabled, IGMP snooping enabled (default settings out of box). Malicious Site blocking enabled. IPS and IDP\Blocking not enabled. AX firmware(fw) at version 41793 and AC68U at 41634. Everything was fine. Upgrade to beta fw 41994 (due to dnsmasq vulnerabilities) and Sonos wouldnt stay connected for more than 5 sec. Downgraded back to AX firmware(fw) at version 41793 and AC68U at 41634. Rebooted all 3 units even thought the instruction did not ask for all 3 units reboot after fw downgrade. Asus fw downgrade by itself did not fix the issue. Did not do factory reset.

Resolution:

Power off all sonos and connect ethernet cable from router to 1 sonos. Power on 1 speaker and configure speaker using Sonos app. Change the connection from wireless to wired. power cycle the Sonos. Connect via app again with cable connected and change to wireless. Leave cable connected and start a music stream. While music is running, disconnect the ethernet cable. Music would stop and should reconnect within 5-10 sec. If not, manually restart music stream. Rinse and Repeat for other Sonos. I do not have any Sonos devices hardwired to router. Good luck.

W

Whatswong

Lyricist I

followup. What stabilized the sonos setup was to bind the Sonos to one of the XT8 as i dont move the speakers. No drops since. Also upgraded the routers to the latest firmware 3.0.0.4.386.42095 w/o any drops.

B

BAPEN

Lyricist I

If you have one of those Asus routers which support Quality of Service (QoS) feature to prioritize different kind of traffic (Streaming, Work from Home, etc.), this may be helpful to you. When I enabled this feature I had lot of issues with connecting to various Sonos speakers, or playing music on them, or adding a new speaker to the system, etc. Once I disabled QoS feature in the router, everything worked seamlessly.

I have ASUS ZenWiFi AX6600 (XT8) router.

THANK YOU!! I knew there was no good reason the Sonos were not working with our new XT8!! It was driving me bonkers that it worked sometimes but mostly didn’t! Problem solved IMMEDIATELY upon turning off QoS!!

Show more replies

Sign up

Login to the community