Sonos Connect Gen2 crashes, WM0, and other surprises

Hello,

I’ve already posted a few months back about my Sonos Connect which was giving me problems (see thread here), but I got some interesting updates I wanted to share since then.

Shortly after that thread I had to move to a new place, so I left the Connect in a box for a while, but I still wanted to give it a last chance. A few weeks later, I went ahead and opened it up to check the power supply output as a last ditch effort (was suspecting a PSU issue). Nothing wrong there, voltages were stable as it should.

Now the funny thing is, after putting it back together, it suddenly started working like a charm! Not a single crash for weeks on end. Got me really puzzled as to what happened since the only thing I thought I did was to check the voltages, nothing else.

Fast forward 6 months to a few days back, and it finally crashes again.

Now here’s some observations I could gather better this time:

• The Connect was set up on a new wifi since the “fix” (new home, new router, new wifi).
• The last thing I did before the crashes came back was to plug the new Sonos Beam to ethernet, which triggered a SonosNet to be created for the first time and all devices to be switched to WM0 (which I suspect is the issue here). Before that, all were strictly on Wifi.
• After unplugging the Beam from ethernet, the Connect stayed on WM0 (would crash all the time), even though all other devices joined back on WM1 (WM2 for the surrounds).
• Like last time, I just repeated the steps I did for the “fix”: open, check voltages, looks good, close. This time I went to the app to check the network: still on WM0, even though there’s not a single wired device in the house anymore. So I followed with a factory reset. Result: Connect is now on WM1 and working like a charm again.

So, this all made me wonder: are there known cases were SonosNet would cause such issues (compared to Wifi) ? Why does the Connect stay on WM0 when all the other devices switched back to WM1 after unplugging the Beam from the network ?

My current assumption is that the initial fix had nothing to do with the opening of the device at all (“you don’t say!”), but instead that it finally ended up on a new unknown network. When factory resetting, the WM0 didn’t “stick” as it was a whole new network, and thus it selected WM1 where it worked again. So there’s still an issue whenever it switches to WM0, but as long as it stays on WM1 it works perfectly.

Any ideas anyone ? I know this is a strange one. Couldn’t find similar symptoms anywhere on the web.

Cheers!