thank you @Giacomo Papa I now don’t feel so alone or stupid for not being able to make the App work effectively. I’m sure there are many more in a similar situation who aren’t bothering with the ‘community’ and will eventually drop Sonos as their speaker of choice but do so silently, possibly not even a whimper. I guess that Sonos aren’t really that bothered, they must have bigger fish to fry. Once I find a suitable alternative to Sonos I’ll switch, give away the speakers as Bluetooth option to others. Can only be a matter of time…. I’ll be patient. @Corry P cc’d for reference.
To be honest, I agree with John B, this probably has little to do with the app directly, but the associated speaker software updates seem to have screwed the whole thing up. My concern is if Sonos get to a point of not supporting the older kit and then they are worthless ornaments and have zero secondhand value. I tend to spend a lot on music equipment with the view of keeping it for a long period (had my main hifi speakers for 20 years etc). I don’t want to have to replace all of my Sonos system for a while yet!
thank you @Giacomo Papa I now don’t feel so alone or stupid for not being able to make the App work effectively. I’m sure there are many more in a similar situation who aren’t bothering with the ‘community’ and will eventually drop Sonos as their speaker of choice but do so silently, possibly not even a whimper. I guess that Sonos aren’t really that bothered, they must have bigger fish to fry. Once I find a suitable alternative to Sonos I’ll switch, give away the speakers as Bluetooth option to others. Can only be a matter of time…. I’ll be patient. @Corry P cc’d for reference.
@Turtles . I am sorry to have created such a poor impression of my character and intentions. As you don’t know me, or anything about me, I am not personally troubled by what you think.
Let me be clear: I am not claiming that the app update is fine. It has certainly created a good deal of frustration, particularly in lost functionality anf unfamiliar navigation. But my observation in the past is that when there hasn’t been a recent update, people come on here and say (in effect) “my system has gone wrong”. When there has been a recent update, they say “the update has wrecked my system”.
As @Corry P says, I do come on here with the intention of helping. My feeling here was, and remains, that you shouldn’t assume that the app (or the system software) is to blame for your dropped speaker problems. If you wait for Sonos to solve these through software changes, you could be in for a long wait.
I am not saying that your network is faulty. But sonos places greater demands on a network than most applications. The fact that your smart TV etc works doesn’t really prove much. Sonos requires multiple devices - speakers and controllers - to maintain almost constant contact. Everybody’s network and wireless environment is different, and a setting here or there can lead Sonos and the network to fall out with each other. It may take some digging to work out what needs to be done, but it’s nearly always resolvable. A system reboot is just an initial thing to try before further troubleshooting. There is no point in multiple reboots. All that proves is that the real issue has not been addressed.
So to sum up: the frustrations with the app update are genuine and in many cases well-founded. But not every aspect of every system problem since the app update is caused by the app update.
I really am trying to help. I am sorry if I have given any other impression.
thank you @Giacomo Papa I now don’t feel so alone or stupid for not being able to make the App work effectively. I’m sure there are many more in a similar situation who aren’t bothering with the ‘community’ and will eventually drop Sonos as their speaker of choice but do so silently, possibly not even a whimper. I guess that Sonos aren’t really that bothered, they must have bigger fish to fry. Once I find a suitable alternative to Sonos I’ll switch, give away the speakers as Bluetooth option to others. Can only be a matter of time…. I’ll be patient. @Corry P cc’d for reference.
@Turtles . I am sorry to have created such a poor impression of my character and intentions. As you don’t know me, or anything about me, I am not personally troubled by what you think.
Let me be clear: I am not claiming that the app update is fine. It has certainly created a good deal of frustration, particularly in lost functionality anf unfamiliar navigation. But my observation in the past is that when there hasn’t been a recent update, people come on here and say (in effect) “my system has gone wrong”. When there has been a recent update, they say “the update has wrecked my system”.
As @Corry P says, I do come on here with the intention of helping. My feeling here was, and remains, that you shouldn’t assume that the app (or the system software) is to blame for your dropped speaker problems. If you wait for Sonos to solve these through software changes, you good be in for a long wait.
I am not saying that your network is faulty. But sonos places greater demands on a network than most applications. The fact that your smart TV etc works doesn’t really prove much. Sonos requires multiple devices - speakers and controllers - to maintain almost constant contact. Everybody’s network and wireless environment is different, and a setting here or there can lead Sonos and the network to fall out with each other. It may take some digging to work out what needs to be done, but it’s nearly always resolvable. A system reboot is just an initial thing to try before further troubleshooting. There is no point in multiple reboots. All that proves is that the real issue has not been addressed.
So to sum up: the frustrations with the app update are genuine and it many cases well-founded. But not every aspect of every system problem since the app update is caused by the app update.
I really am trying to help. I am sorry if I have given any other impression.
Your comments and suggestions are very helpful. I recognise that Sonos has high demands on network etc, but isn’t one of the benefits of the Sonos system that it in effect creates its own mesh? Surely one of the key features of such a system, and one that attracted me before I bought into it, is that it works effortlessly and is simple to set up and maintain?
That, I think, use to be the case. But now, for whatever reason, with a good, stable and stronger wifi network than I have had before, it seems to have gone from something that a child could set up to something that needs an IT guy on speed dial.
but isn’t one of the benefits of the Sonos system that it in effect creates its own mesh? Surely one of the key features of such a system, and one that attracted me before I bought into it, is that it works effortlessly and is simple to set up and maintain?
That isn’t really true (as you go on to say) for many users any more, particularly not for newer users. SonosNet only runs if you wire at least one Sonos device to your network. Sonos’ most recent speakers, like the Era100 and Era300, don’t have an Ethernet port, and are not capable of connecting to SonosNet if it is running. I think this leaves Sonos more vulnerable to the vagaries of different mesh systems. SonosNet was a mesh system way ahead of its time, when domestic mesh networks were unheard of, and most users’ networks were incapable of supporting Sonos. Sonos appear to think SonosNet has had its day, and it most definitely isn’t a selling point anymore.
That, I think, use to be the case. But now, for whatever reason, with a good, stable and stronger wifi network than I have had before, it seems to have gone from something that a child could set up to something that needs an IT guy on speed dial.
I suspect (but am not sure) that for most users setup is now actually more straightforward. But when things go wrong, either at setup or later, there is more complexity to deal with??? Then you add in the app update…...
Hi @Turtles
There were people coming here with various issues long before the new app came out, and I see no reason whatsoever for that to have suddenly stopped - if things work for one person, but not for an other, it’s easy to make the assumption that there is a reason for that. Often, that reason is local.
Given that we now know that the firmware on all your speakers match, we can rule that out as being the reason for your issues with grouping. Therefore, I do in fact come to the conclusion that the issue is due to local factors (it’s the only other reason I’ve ever heard of for the problem you describe). I recommend you get in touch with our technical support team who have tools at their disposal that will allow them to give you advice specific to your Sonos system and what it reports.
It could, however, be as simple as rebooting your router by switching it off for at least 30 seconds - I recommend that you do this several times a year, and before calling in.
I hope this helps.
Hi @Corry P
i will contact tech support when I return from work commitments. It totally bizarre that the system doesn’t work consistently and really does make me think that the Sonos system is not fit for purpose. Btw talk of Mesh and other clever tech stuff referenced by @John B seems to be such high level expertise that it is overwhelming.
Still no news on the fixes for the App….
but isn’t one of the benefits of the Sonos system that it in effect creates its own mesh? Surely one of the key features of such a system, and one that attracted me before I bought into it, is that it works effortlessly and is simple to set up and maintain?
That isn’t really true (as you go on to say) for many users any more, particularly not for newer users. SonosNet only runs if you wire at least one Sonos device to your network. Sonos’ most recent speakers, like the Era100 and Era300, don’t have an Ethernet port, and are not capable of connecting to SonosNet if it is running. I think this leaves Sonos more vulnerable to the vagaries of different mesh systems. SonosNet was a mesh system way ahead of its time, when domestic mesh networks were unheard of, and most users’ networks were incapable of supporting Sonos. Sonos appear to think SonosNet has had its day, and it most definitely isn’t a selling point anymore.
John,
This may not be true now, but when I bought my kit, it was high on my list of priorities. As I have a Connect attached through Ethernet, I am still using this approach. Maybe I should try resetting all up on my network mesh rather than Sonosnet and see how that works.
but as I say, it should be child’s play to set up, it use to be, but isn’t anymore.
@Giacomo Papa . I would never encourage anyone to abandon SonosNet. Using SonosNet has actually been an effective fix I have recommended in many topics on this forum. I was just pointing out that Sonos are gradually withdrawing it as an option for users with newer gear. . For many existing users it will be the best choice for many years to come.
But I think we have now gone rather off-topic.
@John B @Giacomo Papa
what is Sonos Net
What Does it cost?
@John B @Giacomo Papa
what is Sonos Net
What Does it cost?
Hi. I realty don’t think SonosNet is relevant to your issues, but I’m happy to answer your question. The Sonos system is capable of setting up its own wireless network. It is created automatically when any Sonos device is connected by Ethernet to a router. It was essential when Sonos launched because most home WiFi networks were incapable of supposing the communications required by Sonos to keep music playing in sync in several rooms. It is a “mesh” type of network, which just means that every device is capable of acting as a “repeater”, passing on the signal tp more disytant units.
Could you tell us more about your setup please? What Sonos gear do you have? What router>