ZenWifi XT8 (1-19-21) Firmware Update Causes Sonos System to Stop Working

  • 24 January 2021
  • 40 replies
  • 5924 views
Show first post
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.

40 replies

M

Hi,

 

I posted a similar thread over at XT8 Potential 3.0.0.4.386_26044 Issue | SmallNetBuilder Forums (snbforums.com).

 

I did not get total failure of the Sonos, but the Beam kept dropping off the network, wiring it in seems to have fixed the issue.  FYI  The Beam has 2 x One SL as surrounds and was using on of those devices to create the Sonos Network.

 

All worked perfectly on 25790.

 

Can you post details of how you rolled back please?  I believe it will be manual process, so some steps especially around order for both nodes would be much appreciated

 

Thanks

 

Minimos

 

 

N
Userlevel 5
Badge +9

I was having an issue even before the new firmware whereby my XT8 would drop my wired Sonos Boost and as all my units are on SonosNet everything would also drop off the network. Immediately power cycling the Boost would bring the whole system back up. Doing nothing eventually the Boost would re connect and back up would come the rest of the system using their reserved IP addresses. This would happen maybe once a day or every other day. I could understand a WiFi connected device dropping off but not a wired connection.

busy trying to edit the queue
M

Its certainly a weird one.  Are you on 25790, and have you done a factory reset the last time you did a firmware upgrade?  Over at SNB if you don’t do a factory reset each firmware change they call it a dirty flash and has caused issues for users.

I’ve rolled back now (did the Node first then the router), issues are gone.

I also had issues with 2 Xbox Ones not allowing access to some online games, going back to 25790 has fixed that issue as well.

 

S

factory resetting the router worked for me

M

I’d actually chalked all this up to a Sonos problem rather than correlating it with the firmware upgrade on my three-node Asus ZenWifi AX XT8 network, and spent a while faffing around trying to see if binding the Sonos devices to different nodes helped, but then found this thread.

Decided to do a hard factory reset on the mesh wifi nodes before trying the downgrade, and touch wood it looks like it’s resolved all the annoying unreliability issues, but QoS still causes issues if I turn it on. 

This is with a Sonos Five, One, and Roam.

M

Actually, it looks like I spoke too soon. Still flaking out and getting sporadic Sonos errors.

A

@conceptk Thanks for the post. Did the 41793 update and Sonos stopped working. Knew it was the firmware update because that was the ONLY thing that changed in my environment. Glad you posted the steps to revert back! Was about to do factory reset on router… 

N
Userlevel 2

Check if Quality of Service (QoS) feature is enabled in the router. My system started working seamlessly when I disabled QoS feature. With QoS enabled, I couldn’t add a new speaker to the system, couldn’t play music on speakers, speakers keep on dropping, etc.

C
Userlevel 1

The QoS feature was not enabled and I had the issues.

W

So I guess my big question is why does stuff run on 2.4Ghz?  Don’t tell me you tried to keep the cost down by using 2.4Ghz instead of 5Ghz.  I tried to get stuff running yesterday on the XT8 system.  Had nothing but problems. I downgraded to 25790 and not dice still no connections.  Everything happens except connect to 2.4Ghz.

Y

I went on Asus chat yesterday to let them know of these issues. They opened a case and then sent me instructions to rename the router, change the password to a generic one, run a system log and then send it to them. My system is working under 25790 right now and I am not going down that path. Since you are not have any success maybe reach out to Asus directly - they may be able to help you. 

Y

Followed your steps and all seems to be running now (2 hours in) on 41793. Took a long while for router to find second node after reset but now working. Hopefully for future upgrades we don’t have to set up our network from scratch each time. Will keep you posted. Thanks sean-a-thon!

S

Just tried it out and it works for me. Will report if it still works after few hours. 

Y

One day and still working well for me!

N
Userlevel 2

@conceptk - Disappointedly, I later learned that disabling QoS did not fully resolve the connection issues. I also resorted to workaround of connecting one speaker via ethernet cable and the rest started using “SonosNet” network that the hardwired speaker creates.

Terms & ConditionsCookie settings