Please don’t ‘reset speakers’ again, without talking directly to Sonos Support , all you’re doing is erasing the information they’d use to help figure out what was going on. 

I’d suggest a temporary Ethernet cable between the Beam and your router. Then, I would recommend that you submit a system diagnostic, with the Beam showing up in the controller, and calling Sonos Support to discuss it.

There may be information included in the diagnostic that will help Sonos pinpoint the issue and help you find a solution.

When you speak directly to the Support staff, they have tools at their disposal that will allow them to give you advice specific to your network and Sonos system.

Out of the blue there all back

hopes it stays this way.

NOT!!!!!

it dissapeared again,

Sounds like a multicasting ‘device discovery’ issue. Ensure all Sonos software and firmware updates have been installed - check both the mobile device App Store and iodates in the Sonos App too. Also see below…

SSDP (the UPnP simple service discovery protocol) and/or mDNS is used to initially discover the Sonos players and is done via multicast packets sent between the controller App and the Sonos players.

Both the Sonos players and controllers must share the same network subnet. However if the Sonos devices are connecting to multiple access points, then I suggest that they be set to the same SSID, WiFi channel and channel-width. This is for optimum performance particularly in groups and for some reason with some (not all) mesh-based WiFi systems, it appears some will work okay with Sonos, but others may not, particularly if the satellites/AP’s are perhaps auto-selecting their own WiFi channels. I’ve seen some people report issues with Google ‘nest’ mesh WiFi, for example, although others will occasionally say it works for their ‘small’ Sonos setup.

What is certainly not supported though by Sonos, are wireless range extenders, as some can mangle device MAC addresses and EoP (powerline) adapters.. so if you are using those type of wireless access points, to extend the wireless network coverage, then that may cause such intermittent device discovery issues by the Sonos Controller App.

Reserving the IP addresses in the routers DHCP reservation table can often help with device discovery, so consider making your Sonos IP addresses static. The router user-manual will normally assist you to do that in most cases.

Just to add aswell, it can sometimes be Apps/software running on the mobile ‘controller’ device that interfere with ‘device discovery’ Examples to perhaps consider are…

• VPN Client 
• Firewall software
• Antivirus software
• WiFi Calling/Dial assist
• Private network address (MAC address spoofing)
• Mobile data enabled for the Sonos App  

So consider disabling these features, even temporarily, just to see if that may fix your device ‘discovery’ issue.

Thank you for your reply, I Will try to change from mesh system to direct router wifi.

only thing I am wondering is that it always worked fine on the mesh system. It just since last week that it started to give problems.

thats Why i can’t believe the Mesh is the problem.

but ok, you Will now for sure if you have tried, so i Will give it an attempt 

It may well not be the WiFi mesh, I use a mesh system myself - what mesh system are you using?

ASUS zenwifi ax mini

As far as I’m aware ASUS ‘mesh’ systems are usually okay with Sonos - not that I’ve used ASUS myself, but as a temporary measure there’s no harm perhaps seeing how things work out for you if you temporarily power off the mesh satellite hubs and run all on the router only. It will at least rule out the mesh setup if your problems still continue.

Yes, I think its ok to give it a try. 
but it certainly is a strange situation, especially cause a lot of people are complaning with the same issues. And if i’m right it all started with the app update

People of course only complain though when they encounter an issue. Rarely do people say anything when things are working okay. 

According to Sonos the majority of users are not experiencing the problem. See the information and table shown in this link:

https://support.sonos.com/en-us/article/the-new-sonos-app-and-future-feature-updates

Also I’m not seeing the issue here, (see attached), so it’s likely something local that’s causing the discovery issue in your case.. but I can only add it’s worth maybe exploring these things anyway and see if you can perhaps get to the root cause.

​@Eric77nl,

If not seen already, maybe checkout some of the things mentioned in this earlier community link too, such as disabling ‘Airtime Fairness’, changing channel-width etc.

And it’s certainly possible that Asus sent out an update to your mesh router that changed things.