Ever since you enjoyed prematurely releasing your piece of crap app in may. I ve had speakers dropping off, cant separate speakers from tv, connection issues. Speakers disappearing from system cant find system on and on and on. The foreign techs are hard to understand. I get got a major investment in this garbage.16 total speakers. Have made dozens off call to your help line . They know your products suck and they may fix an issue but it always comes vack . Wish i could start over with something else. Too late i m stuck. You shouldn’t have released the app till it was ready. Will never buy another product from sonos
Answered
the sonos system as a whole
Best answer by Ken_Griffiths
You’ve mentioned these things already in your previous posts and have other (question) threads on a same/similar topic here:
https://en.community.sonos.com/speakers-229128/is-it-just-me-6923292?postid=16825934#post16825934
It’s not clear what you’re asking in your question that you’ve posted here? If you perhaps want to provide some detail about your network & Sonos setup, then perhaps some suggestions can be made by other community users, but not sure why you just didn’t do that in your earlier thread that you started?
My own initial guess from some things you’ve mentioned, is you that ‘may’ perhaps have an intermittent SSDP/mDNS discovery issue across your local network. 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, the recommendations (from myself, at least) are that they be set to the same 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.
If your problems do persist however, then I can only suggest you reproduce the issue(s) seen and then immediately submit a Sonos system diagnostic report from within the Sonos App, note it’s reference and contact/chat with Sonos Support Staff once again via this LINK and see what the Staff can perhaps suggest to help you to resolve the ongoing matter.
You could also just wait and see how things go with any new Sonos upcoming software and firmware updates.
A more drastic and clearly costly option would be to try things with a different network setup and see if that may improve things, or to even sell-on your devices.
I guess there are occasions when some hardware environments may not be compatible with every product we own - it’s why Sonos and other manufacturers have hardware incompatibility lists. I can’t comment personally, as you’ve not detailed any of your hardware, or how you’ve got things setup around your Home.
So providing much more detail will really be key, that’s if you’re perhaps trying to glean some answers to any questions here?
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.
You’ve mentioned these things already in your previous posts and have other (question) threads on a same/similar topic here:
https://en.community.sonos.com/speakers-229128/is-it-just-me-6923292?postid=16825934#post16825934
It’s not clear what you’re asking in your question that you’ve posted here? If you perhaps want to provide some detail about your network & Sonos setup, then perhaps some suggestions can be made by other community users, but not sure why you just didn’t do that in your earlier thread that you started?
My own initial guess from some things you’ve mentioned, is you that ‘may’ perhaps have an intermittent SSDP/mDNS discovery issue across your local network. 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, the recommendations (from myself, at least) are that they be set to the same 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.
If your problems do persist however, then I can only suggest you reproduce the issue(s) seen and then immediately submit a Sonos system diagnostic report from within the Sonos App, note it’s reference and contact/chat with Sonos Support Staff once again via this LINK and see what the Staff can perhaps suggest to help you to resolve the ongoing matter.
You could also just wait and see how things go with any new Sonos upcoming software and firmware updates.
A more drastic and clearly costly option would be to try things with a different network setup and see if that may improve things, or to even sell-on your devices.
I guess there are occasions when some hardware environments may not be compatible with every product we own - it’s why Sonos and other manufacturers have hardware incompatibility lists. I can’t comment personally, as you’ve not detailed any of your hardware, or how you’ve got things setup around your Home.
So providing much more detail will really be key, that’s if you’re perhaps trying to glean some answers to any questions here?
First of all thats wayyy over my head and all that technical talk . Secondly before the new app had zero problems. Thats what i m blaming it on.
I guess nothing stands still these days in tech. terms. We all may sometimes have to change a few things to accommodate change. If you don’t know where to begin, then you’re probably best to seek advice yourself, whether that means going back to Sonos Support, or speaking to a friend, colleague, or relative, that may better understand these things, or seek professional assistance. If you don’t know what you’re doing, then it’s best to leave it to those that do.
phildirt3 wrote:
I have trouble understanding the foreign people that are the tech support. Pretty frustrating
Well I guess the same could perhaps be said of anyone that talks to you about things which are technical in any case - you might be better off seeking help from a local Sonos installer, or following one of the other options I outlined in my earlier post. I’m the same with my Gas boiler when that doesn’t work, I have to get someone in to sort it out too.
The responders who say the OP has mentioned this before shouldn’t be surprised. I’ve had these piece-of-crap speakers (two Sponos Ones and two Sonos Play:5s) for five years and I’ve never gotten them to consistently perform correctly. They unpair themselves without cause, they randomly stop playing from spotify without cause, and are overall impossible to manage. I symapthize with the OP and wish there was a solution available that would allow me to succcessfully use these speakers.
And
For what it’s worth, this is my hardware:
-
Play:5 (Gen 2): two of these stereo paired -- intended for use by my Samsung smart TV or my turntable (I manually change the plugs to switch between these two functions)
-
One (Gen 2) grouped with a One SL: One speaker is at one end of the house and the other speaker is at the other end of the house. I use these during the workday so I can hear the music in my office and when I walk to the other end of the house where the kitchen is. They sometimes pay in unison, sometimes not.
-
Just picked up a used Sonos Boost - I’m hoping that this might help the spontaneous play stoppages by offering a dedicated wifi signal. I don’t have a manual for it so I’m now hunting for info online so I can enable it.
My needs are simple...I just want speakers that work. Consistently. This shouldn’t be so difficult. Plug and Play, anyone? (And the Sonos site needs to stop suggesting that I upgrade my speakers, that’s too funny. Why on earth would I want to upgrade when I’ve got more money than I should have spent invested in speakers that I can’t use the way I’d like to use them.)
VLN wrote:
And
You have spoken about your Sonos system, but not mentioned anything about the network they are connected to, or how they are connected?
As you’re tech-savvy…
- What WiFi bands and channels are you using with Sonos?
- What’s the ‘width’ of those channels and why on earth are you about to slow things down by adding a "no longer manufactured” somewhat obsoleted Sonos Boost? - You most likely would have been far better to have used, or added a WiFi mesh setup/additional hub instead, depending on the current hardware you have in situ. Why revert to a slower 2.4Ghz Boost connection these days?
- What are the current Sonos device SNR levels?
What I can say is that any audio dropouts are not caused by the Sonos App - which is just a controller and can be closed fully once playback on a room/group has been started - so we’re either talking network issues here, or less-likely a local hardware issue with your devices.
Starting with the network setup and connection details here I think might be the best way to move forward.
Oh by the way you didn’t mention if you had spoken to Sonos Support over the five years and what the outcome there was with level-1 or 2 Staff etc?
Thanks for the reply
I haven't contacted Sonos support since they released the new app and I ended up with a bunch more problems. The last time I talked to them was a few years ago; it was regarding a different crazy problem. They couldn't fix that one.
I have a feeling that we're going to need to add some type of receiver or sound dock so I can run everything through that instead of relying on wifi. I just wish the Sonos app wasn't so buggy.
Why add a receiver or dock? I don’t even know of anything like that other than the old Boost and even more obsolete Bridge.
If you don’t want to run your Sonos on your home WiFi you can wire any Sonosnet capable Sonos that is a primary device/speaker (no Sub or surrounds) to your main router and it will establish a Sonosnet (close to WiFi but not exactly the same) on the channel you tell it to. This of course will require another clear WiFi channel and there are only 3 of them available.
Non-Sonosnet capable speakers (Eras and portables) can be wired with an external adapter or connect to the home’s WiFi.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.