exactly why I stay away from these forums … a bunch of trolls bashing folks that aren’t like them.
just so you know, I hired tech geeks to address my wireless/network issues eons ago and it runs seamlessly. … and I’ve gone thro multiple network/router changes/upgrades … I’m smart enough to know when I’ve passed the limits of my technical competence and hire experts.
I only judge products based on performance per the promises of sales people.
So … rather than sit and slag folks on boards, take the time to read what they actually say … and recognize that the rest of the world is not like your simple little bubble
… and btw … I faithfully go through the steps that sonos prescribes to resolve connectivity issues from simple off and on to full reset to complete restart. Until you sit in my house with my system, and understand my circumstance, i believe it would be prudent for you to either withhold comment or seek ways to positively engage …
to confirm, yes, this is why I haven’t engaged in this forum for years … seldom do you get constructive help or insights … just comments from people seeking ways to make themselves feel better at someone else’ expense
Yep, Sonos is a crap system if you need to do all of this just to turn your speaker back on!
Is it really? What if you only have it do it once?
Yes, I know this doesn’t have Bluetooth. I just spent over an hour on the phone with customer support, and we could not resolve it, but that was basically what he was saying as well.
Setting up “reserved IP addresses in the DHCP table. “ is beyond my knowledge/capabilities. nor do I think I have a manual for my router somewhere.
But thanks for replying
This may sound overly simplistic, but I had the same issue and after rebooting my router, speakers and Sonos Boost to no avail, I pressed the button at the top of each of my Play 1 speakers for several seconds (the button with the stop/play symbol) and all of my Play 1s sprang to life.
I have one Play 5 and 4 Play 1s. I transmit music from my iTunes app via Airplay. When I click on Airplay, only the room with the Play 5 appears. I click on that room and then open the Sonos 2 app which shows all of the rooms where I have any Sonos speakers. I then simply check off the rooms with the Play 1s where I want to transmit music and I’m good to go.
I agree completely with the complaints here. It should not be this challenging to fix every time. These speakers are not cheap. I have a Sonos One, it worked for a year and then connection issues and it will not work at all now. That’s not good enough. I have tried everything that Sonos recommends without any joy. I work from home without issues and any other systems running through my Wi-fi cause no problems at all. Some of the responses here are ridiculous in saying that Sonos should be void of complaint because the speaker is old or the app is new or the Wi-fi is the problem. It is pretty clear that Sonos is the common denominator here and these ‘fixes’ should not be needed at the price it cost to buy the speaker. I’ll never buy Sonos again.
Came here looking for help with issues I’ve had with my play:1 for the whole time I’ve had it which is pretty much 4 or so years I’m guessing. I really feel like it’s an issue with the product at this point. It constantly drops out and I have tried a load of stuff, I too am a network engineer with 10 years enterprise experience and my home network is solid, unifi APs and wired network access throughout, in fact I have a Sonos:5 as well that has no issues what so ever. If something is still messing up when it’s on a physical wired connection then it’s a pretty big indicator there’s something amiss on the client side.
For me it’s not connecting to the speaker that’s the issue but the app itself - not great!!! 
There comes a point where its time to accept the fact that Sonus Play 1 is no longer in the design and test plans. I reached it. All to hard and inconsistent results.
Agreed here. Speaker becomes unusable.
The “solution” might be that you need to learn something new.
At one point I had SONOS issues much more severe than you are reporting. After I learned a few new (to me) things, I was able to fix my environment and it has been smooth sailing since. That was in 2005. If I had been having constant, unresolvable issues along the way, I would not be here.
If you will not share any details about your home network and are unwilling to learn, we cannot help. You mentioned that you have updated your network along the way. I suggest that you again hire an expert. Hopefully the person that you hire has been keeping up with technology.
“Hire an expert” aka it’s cheaper to buy a different speaker
Yep, Sonos is a crap system if you need to do all of this just to turn your speaker back on!
Agreed here. Everyone is saying this is an easy fix. If you need to fuss with your fundamental wireless system to get it to work, this is a BUG with Sonos. Mine is just not recognizing. I get it—it’s old and prob needs a software update. But a Bluetooth speaker is just an easy solution versus all this bullshit everyone is recommending.
There comes a point where its time to accept the fact that Sonus Play 1 is no longer in the design and test plans. I reached it. All to hard and inconsistent results.
Sonos is certainly a more robust user of your network than any of those other devices you listed, complicated by the fact that each and every time there is a software update, the speakers reboot, and ask your router for a new IP address. While you wait, you could at least temporarily fix the issue by following the process I outlined earlier. It just boils down to how robust the software in your router is. Often, if a router can get into this ‘confused’ state once, it can do so again. Assigning reserved IPs helps forestall that.
And perhaps oddly, I’ve been using my Sonos speakers for well over 10 years, without issue.
Some further context. The Play is connected to the network (it plays when I press the Play button on the speaker itself) but the app can’t find it!
yup … just what I was saying … and if you were listening, you would have seen my comment that I hired the skills to ensure my network was robust and capable of handling the sonos system …
did I reach out to sonos to seek help in resolving my issues? absolutely
Were you in my home evaluating either … I think not … so kindly withhold your opinion of what I’m doing wrong until you have all of the relevant information
spare me the platitudes
I expect you will take further shots at me to fuel your ego and make yourselves feel important at my expense but I won’t partake in any more of this waste of time
It’s the “Trump approach” … if you yell louder, longer you think you’ve won, when actually all you’ve done is proven your insecurity in the world not seeing it your way … the last man standing in these debates is seldom right … the objective is to find a solution
Please give the steps to see it works for me. Appreciated.
As said the steps are router dependent but if you open your router’s web page and look for DHCP Settings it may have an internal help page or a link to the on-line help page that will walk you through it.
Pretty much what you do is put in the Sonos MAC address and the IP address you want it to use. Then power down everything and then bring it back up using the new addresses.
4 replies, each a rant about the product or about the posters. I see not one indication, not even a hint, that the poster is requesting our help. The fixes for this kind of stuff, as my statement about the technical aspect indicated, are not a big stretch. Matter of fact, I've walked self-described technical illiterates through the steps many times, as have others.
But does the poster want to try these fixes? It would appear not. They'd rather slag on the product, make threats to dump it, and criticize the forum and the posters within. Instead of possibly get a stable, working system, they appear to prefer staying put in their assessment. Que sera sera.
One i am not a techie and the play 3 is old. I have had the same problem through out its life. I really dont care whos fault it is. What is a dhcp readable address and can it be done simply. Please give the steps to see it works for me. Appreciated.
If I can interpret your post properly, I suspect a fairly easy solution to your network issue is setting up reserved IP addresses in your router for your Sonos (and frankly, I’d do it for everything on your network).
You can do a short term fix a bit more easily by unplugging all your Sonos devices from power, then reboot your router. Wait two minutes before plugging back in your Sonos. But a router that has ‘failed’ in this manner once will be likely to do so again. Reserving IP addresses helps guard against this network behavior.
Yesterday music heaven Today …..nothing ……has there been a recent upgrade/downgrade do I have to restart the whole world? Do I have to unplug my whole house AGAIN WTF what is happening must you guys fk around all the time now IT wont connect all it will do is make the beeping microphone noise then says it’s not on my network I CAN 100% guarantee it is. Why why why why are you a real company or do you make expensive speakers that last as long as you don’t DO A SYSTEM UPGRADE FFFFSSSSS how do I get around this do I have to move house AGAIN or something similar.
Just to clarify, @phishmeister, you just have a single Play:1 if I read your post correctly? That’s quite an old device, with more limited network capability than more modern Sonos devices. Is this a recent acquisition for you or have you had it (and your connection problems) for a while?
Every single device (about 30) is on a static IP and set aside in its own range separate from my DHCP.
Interesting. Does this include Sonos devices?
It would be hard for Sonos to send any (non existent in current designs) commands to fix the IP issues experienced in a router. I suppose they might figure out some obscure way to recognize that they’ve been assigned a duplicate IP, and ask for a fresh one, but it would still be up to the router to hand out a ‘valid’ IP address, something that it has already failed at.
And perhaps oddly, I’ve been using my Sonos speakers for well over 10 years, without issue.
Not helping Bruce...
If it was just a duplicate IP it would be easy for Sonos to do a fix, the Linux base they use includes the arping command with the “-D” option to detect that. The proper response to finding a duplicate is another arping command with the “-w” option to update others on the LAN, then issuing another DHCP request by the Sonos.
From my many hours of testing, network monitoring and router-DHCP log reading I did not see any issues with the addresses handed out by my DHCP server or in the Sonos requests sent to it. I tested several routers as well as a bare DHCP server with the same result.
Access to the internal Sonos data would probably show the issue but we can’t get that. I’d lean to Sonos using an older version of the DHCP client, doing something slightly out of the usual in a configuration file, or a boot timing issue where Sonos and the DHCP server get out of sync.
If the objective really was to find a solution, you would've asked for one instead of hurling insults. Me? I'll go help someone who actually wants help. Nothing to see here.
