Sonos is playing but no sound from any source

The SonosNet does provide a stable connection, when wireless channels are appropriately setbecause you are experiencing wireless interference and you ought to do something about that. Further, how many devices do you group together at the same time?

Large groups - the largest group is 6 rooms, one of which is a stereo pair.

When I used Boost in the past, we could never solve the music skipping problem due to interference. That’s why I migrated Sonos to eero in the first place.

Your best hope for a stable system is to try the Boost again in this new situation, and then if necessary to work with Sonos Support  (if you can get through) and/or the Sonos staff and users on this forum, if there are issues. 

It is of course your right not to try this but an unstable setup is the only alternative. 

Hi @HarvE 

6 Rooms is a fairly large group - we’d recommend 2 devices hard-wired for a group that size. The choice of speaker that’s put in charge is also very important. If you had wired speakers, one of those would be best, or one closest to the Boost (once it’s connected).

As Eero mesh (and other meshes) don’t allow separation of bands, the only way to really fix the deauthorisation issue is to bypass Eero and use SonosNet instead - I, or Sonos Support, can certainly help with issues that occur then easier than we can fix deauthorisations.

I understand that this is probably very frustrating to hear as it’s the reason you got Eero, but the mesh will still help other devices and home coverage. Although it’s not ideal from our technical perspective, now that you have a mesh you may find that the best place to locate your boost isn’t by the router but wired to one of your mesh nodes, elsewhere. There are certainly more options now, with the mesh.

Someone on Reddit pointed me to an article at eero that says the same thing: use SonosNet for systems with more than three zones: 

Eero article

But you suggest plugging the Boost into a non-gateway Eero mesh node, right? In the article above, Eero says NOT to do that (yes, they capitalize NOT). 
 

Despite my venting yesterday (again, sorry), I am open to suggestions. I also have a callback with a Sonos support supervisor tomorrow.

@HarvE 

I suggest you do whatever works best for your enjoyment of your Sonos system - that’s the priority here. Ideally (and if you ask tech support they will say this), wire Sonos to the router or main Eero node (assuming you don’t have dual DHCP as discussed earlier) as mentioned in the Eero article. Simpler connections are usually better.

If that location has a particularly bad environment however (the router and the Eero hub are already transmitting WiFi and the Boost would add a third transmission. Add a WiFi-capable printer or a home automation hub to the mix and there’s four or more WiFi networks), then wiring to a node instead may be better, in your case. The router, Eero Hub and Boost (and a printer, etc.) would all like to have 1m space from each other and things just might get too crowded or impractical. Of course, even if your old router is still running the network, there’s no longer a need for it to transmit WiFi so you could disable this to improve matters.

But really, as you’re using large groups, I recommend you do both. Wire the Boost to the router/hub and a speaker to one of the nodes, or the other way round - whatever fits your setup the best.

Thanks. Willing to try (almost) anything at this point, except move to a new place.

@HarvE .When you have added the Boost and updated, check in About My System that every Sonos device except the Move has WM:0 next to it,  not WM:1. For speakers connected wirelessly WM:0 indicates that the speaker is connected to SonosNet.

You may need to reboot some speakers to achieve this.

You may also need to experiment with the SonosNet channel in Settings, System, Network. 

Just thought I would report back after working with a Sonos support supervisor earlier this week.

Apparently, during idle times, the devices are ungrouping, even though the app thinks they are grouped. When I start the system after this idle period, a low level message is not getting though to regroup. A fix is to ungroup and regroup in the app, but there may be a time lag of several minutes before it happens (again, despite the app behavior).

Also learned that, when using the Wi-Fi mesh, I should designate the Port as the group coordinator since it is operates at 5 GHz. I was following the protocol from trying to troubleshoot my older SonosNet - designating a closer Play 3 as the group coordinator but it operates at 2.4 GHz. 
 

Trying to reproduce the problem again empirically and generate diagnostics for further review. Trying to stick with eero since the SonosNet problems I had (audio gapping) were more chronic. 

The SonosNet is a dedicated MeshNet, where every node acts as extender to the mesh, so it makes sense to select the closest item to the Root Bridge as group coordinator. In WiFi mode there’s no such mesh, thus keep in mind that 5 GHz frequencies, while providing faster speeds at shorter range, barely penetrate walls.