If they brick my devices, I will only be half upset.
If they brick my devices, I will only be half upset.
Pretty crappy default configuration on Sonos' part (using old default cost values), if you ask me.
Instructions I followed which solved everything: https://bsteiner.info/articles/disabling-sonos-wifi
Sonos's spanning tree implementation is problematic (and anachronistic: last I looked, it was using classic STP not RSTP). In a similar situation I've watched them flap away merrily, spitting constant topology change BPDUs at each other through both interfaces. It's not a pretty sight.
They seem to me to be totally in denial about it, judging by their forums. Lots of blame-the-customer and blame-someone-else's-device, and very little (or no) technical documentation. I think they are a speaker manufacturer first, a streaming audio interface second, and a networking company a very distant third.
I've had one tiny but annoying bug: Occasionally a podcast will show 0:00 to 0:00 on the scrubber and nothing -- not rebooting the whole system and my phone -- will fix it. It can be frustrating to be unable to scrub to the 40 minute mark on a podcast where I've already listened to half of it.