Can't connect AGAIN!

But the PLAY:1 was designed before Bluetooth became a ‘thing’ with Sonos. There just isn’t any Bluetooth electronics inside it. You could certainly get a Roam, which does accept a Bluetooth signal, and then ‘group’ the two rooms together.

On the other hand, you clearly have some sort of network issue going on. Often, I’d suggest wifi interference , but in this case, I suspect a more likely culprit is an issue with your router handing the Sonos a duplicate IP address. Try unplugging all Sonos devices from power, and then reboot your router. Give the router two minutes to come back up before plugging back in your Sonos. Note that this issue is irrespective of Wi-Fi or wired systems. And if it does resolve your issue, I’d heartily recommend looking at your router’s manual to set up reserved IP addresses in the DHCP table. 

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  
 

Manuals can be downloaded from the internet. If you post what router you own here, someone will probably post a link to the manual.

Thanks.  Yes, I’m aware I can google and download a manual, but really?  Every other device in my home works just fine (Laptop, printer, Nest thermostat, Google Home, smart lights, smart TV, etc).  When I was on the phone with support we even directly wired it with an ethernet cable and it still didn’t work.  They are escalating the issue, but I’m getting close to just throwing the thing off the roof and getting another speaker that does Bluetooth (and it won’t be from Sonos, that’s for sure).  I’m just extremely frustrated and have spent HOURS on this.

They say I will be contacted by email to schedule a time for someone to help me.  (more hours, clearly).

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.

Yep, Sonos is a crap system if you need to do all of this just to turn your speaker back on!

And perhaps oddly, I’ve been using my Sonos speakers for well over 10 years, without issue. 

Is it really?  What if you only have it do it once?

I’d think Sonos should spend the time to identify just what is going on with DHCP addressing and come up with a fix that doesn’t need static/reserved IP addresses. Like other recent bugs getting an actual test case that fails regularly in the lab where it can be debugged isn’t easy.

Until then just set the IPs and move on. It is five minutes, once, and you'll spend double that every time the glitch bites recovering from it.

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.