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

Here’s my experience with the Asus XT8’s and the most recent firmware including the beta.  

With the Beta, when I launched the Sonos app, all my speakers showed up. This was a change from firmware versions 26044 through 41793, as when I'd launch the app with those installed, only a few of my speakers would appear.

I thought I was good to go, but then I tried to play a song from one of the streaming services (Apple Music), and while the songs in the playlist showed up and were added to the queue, nothing would play, and I constantly received the error "cannot connect to Apple Music". Interestingly though, I could play local media on my network.

I reverted back to firmware version 25790 and everything is working as it should.  Seems like Asus is close to getting it right and hopefully once the final version of the latest beta is out everything will be fixed.

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.

Hi, can you confirm that streaming services are also working without issue?  On the beta firmware for my XT8 (9.0.0.4.386.41994) all my speakers showed back up but I was not able to stream.  I could play music from my local library but no streaming services, ex. Apple Music or Sonos Radio.

Thanks, for going the extra mile on the reset, hopefully, it’s the fix we need!

I can confirm what Naveed.Ahmad originally posted that firmware version 3.0.0.4.386_41793 does work with my Sonos system after performing a factory reset as outlined HERE. This includes all streaming services and speakers.  I’m WiFi-only and have everything from amps to subs, playbase, beam, move, play 5,3,1’s.  

Thanks, Naveed.Ahmad for going through the factory reset!

Hi,

I think I’d like to chance the upgrade to 41793 based on @Naveed.Ahmad & @sean-a-thon success.

I’ve taken a look at the factory reset instructions in the link, but there does not appear to be any advice on FR 2 nodes.

What method did you use?  e.g do satellite node first on a XT8 etc 

Thanks

@Minimos, I initiated factory reset from my ASUS app on my Android mobile.
@sean-a-thon, Yes music is playing fine on the speakers too. I use Amazon Music service.

Sadly though, the Asus node disconnection problem reappeared. It would start blinking blue light and would not connect back again until I turn the node off and on again. The signal strength between the primary router and secondary node is otherwise great. I am beginning to think that investing in Asus router was a bad idea. It has given me enough grief. I ended up connecting the two routers via Ethernet cable, and repurposed the otherwise dedicated 160MHz backhaul for regular WiFi use.

@Naveed.Ahmad 

Thanks for the info.

To be a Guinea pig as well I’ve made the jump.  I had tons of trouble getting my Satellite node back online after the upgrade.  Eventually did a factory reset, removed the main node, plugged in the Satellite to flash matching firmware, factory reset again and the node got picked up.

So far so good, but you noting drop out again concerns me, I’ll see how it goes and report back in a few days. One thing worth trying is making sure the Wireless Settings are not left on 5GHZ-2 in the UI.  My 2nd node dropped after I changed some settings couldn’t figure out why, altering the view back to 2.4/5Ghz-1 solved the issue.

Also, I am pleased to report my Xbox Live issue is also resolved,  I had to change the NAT to Full Cone in the WAN setting (this is a new option not see on 25790).  It defaulted to Symmetric on install, and it had the same issues as 26044, but changing this resolved the issue.  I think even though it was not shown in 27590 Full Cone NAT was the default.

I have the XT8 and have been having loads of problems with my Sonos system, I have today installed the 3.0.0.4.386.41793 update, not brave enough for the beta version at present, i just let the XT8 do its own update, and since it did the Sonos are all online for the first time in weeks, alexa works fine too and i can access music from my plex server on them. Will see how it goes over the coming days.

Hi

Here's an update.

The Beam worked perfectly including Alexa until I added the Satellite, did not notice it had stopped working until I tried to change the volume and it did not respond (was testing all my other IOT devices worked with the new firmware)

Noticed that the DHCP assignments showed as static.  Anyway plugging back in an ethernet cable to the Beam solved the issues again.

I was digging around this forum and and found:-

The update was only an hour old, so I made the changes suggested to multi cast on the LAN, it did something as instantly all the DHCP assignments  for my Sonos devices changed to DHCP from static.  I thought this was the golden goose, unfortunately switching it back to wireless only brought back the issue of not being able to use Alexa or alter volume on the Beam over WIFI.

Just so we can get some consistency, My Beam has 2 SL ones as surrounds, I also have 4 other Play:1 in the house and a legacy Play:5, All bar the 5 are on S2.

QOS is currently on in the router.

Has anyone had success with an XT8 and a Satellite node?  I am conscious maybe some people reporting success age different setups, and getting to know how each is different may allow us as a group to find a solution

Thanks

Minimos

YES!!!! 3hrs on with support they couldn’t help. 5min search thru the community posts and BAM! Fixed!! Thank you!