I absolutely have this issue and have several tickets open with Sonos support after sending them 20+ diagnostics and reports of my device configurations and varying statuses.
2 Play 1s and 1 Play 5 and my Macs and iPhone intermittently drop/ lose these speakers and / or cannot use the group function any longer.
I’ve followed all the recommendations from Sonos support including sequential reboots, changing my network channel etc.
Essentially investing hours and hours of my time to try to resolve an issue that I also believe arose from that software update.
smells like a class action lawsuit to me unless Sonos acknowledges and fixes these issues.
in the meantime I’m telling all of my friends and family to avoid Sonos products like the plague, and that’s after 6 years of use and advocacy as they’ve always worked until this point.
The situation is simple Sonos team: fix this issue or lose users who are connected in tech and will absolutely put your failings on blast.
Be accountable and restore functionality to our expensive devices.
We are having the exact issues described above; we have one Sonos sound bar, 3 Sonos 1 - 2 are grouped with the sound bar to create surround sound in our living space with the TV. The 3rd Sonos 1 is in a different room. For the past two months, about every 2 or 3 days we lose the sound bar and the 2 Sonos 1 speakers that are grouped with it. Oddly we never lose the individual Sonos 1 that is in a separate room. Our solution is what has been described above; power everything off, reboot our routrer, power on, and reconnect. This is getting very old. Regardless of the sequence nothing works as a permanent solution. What did Sonos break in this latest update???
I am not very technical, can follow simple instructions, but I just want my surround sound back and my somewhat costly technology to work as promised - is that asking too much?
My system seems pretty stable, and has been for some time.
As far as your problems, if you’re looking for some help a bit more information would help. Which update? Are you running wired or wireless? Wifi or SonosNet? Have your neighbours changed wifi channel, causing interference in your system? Have you rebooted your router as well as all speakers?
Thank you, but I'm not looking for troubleshooting help. I have already isolated this to Sonos device connectivity to WiFi using IP packet analyzation with a sniffer. The data has proven there is no issue with the network, devices on the network or from any interference. The disconnect is being caused by the Sonos devices themselves…. locking up and needing a reboot to reconnect, which is indicative of a firmware or OS issue, which is exactly what was recently updated.
The system has never had an issue until this last system update, and nothing else has changed.
I’m looking to see if there are others experiencing this issue.
Do you have static reservations for your IP addresses? The most common cause of post-update problems is IP duplication.
Thank you, but I'm not looking for troubleshooting help. I have already isolated this to Sonos device connectivity to WiFi using IP packet analyzation with a sniffer. The data has proven there is no issue with the network, devices on the network or from any interference. The disconnect is being caused by the Sonos devices themselves…. locking up and needing a reboot to reconnect, which is indicative of a firmware or OS issue, which is exactly what was recently updated.
The system has never had an issue until this last system update, and nothing else has changed.
I’m looking to see if there are others experiencing this issue.
Actually, it is indicative of duplicate IP addresses, something we have seen thousands of times over the last 15 years. These happen when the router loses track of its IP allocation table due to a crash or a reboot, and starts handing out IP addresses that are already in use. The symptoms often show up after an update, because an update causes Sonos devices to reboot, and they all request a new address upon startup. So the sooner you stop insisting it is some widespread error in the Sonos firmware, the sooner we can get it fixed.
Reboot/power cycle the following, in this exact order, waiting till each comes up before moving to the next:
Router/modem
Switches/hubs
Wired Sonos devices
Wireless Sonos devices
PC/Laptops/streaming devices
Printer and other peripherals
You can also switch WiFi Off/On on your phones/tablets
After that, you can eliminate the problem entirely by going into your router setup and reserving IP addresses for all you Sonos devices.
I'm not insisting anything, I simply asked a question. Your answer… and arrogance… is not helpful…. I suggest you read in detail before you just repeat the same answers that everyone else does which have nothing to do with the question asked. Of course, everyone uses DHCP, right? And its the root of all issues…. wrong in this case. I don't use DHCP and never would…. if you really understood networking and security you would know that DORA doesn’t apply… even if you know what DORA meant… but you probably felt great in front of others that don’t know any better.
Yes, in 15 years, every issue was user configs and routers… never Sonos firmware or devices. Enjoy your little bubble and your lack of reading comprehension and technology skills.
Please close the thread.
@Craigster Sonos will never accept they have goofed up
something and are trying to insist it’s a networking issue when it’s not. There is a 57 page long post of users reporting dropouts since 14.6 update was introduced way back on 19th April 2022. Following this update, many users are having audio dropouts randomly and the only thing that helps is a reboot of all devices. With regards to DORA , Sonos team it stands for Discover, Offer, Request and Acknowledge. It’s a simple IP allocation technique used in a server client model when a client is requesting an IP. @Craigster you aren’t alone here, unfortunately we are at the mercy of engineers who are claiming the dropouts to be a network configuration or wireless interference problem when it’s not. FYI, the link for thread is as below:
Please add yourself in the thread and hopefully we can help each other come up with a solution as @Sonos hasn’t been able to fix it yet..
@kuwarrulz_11 you may wish to recruit others to your cause, but the OP said they had “a Play5, 3 Sonos One, and a Sonos Port”. No Arc. No surrounds or Sub. In short, nothing to do with the thread you referenced.
Thank you, but I'm not looking for troubleshooting help. I have already isolated this to Sonos device connectivity to WiFi using IP packet analyzation with a sniffer. The data has proven there is no issue with the network, devices on the network or from any interference. The disconnect is being caused by the Sonos devices themselves…. locking up and needing a reboot to reconnect, which is indicative of a firmware or OS issue, which is exactly what was recently updated.
The system has never had an issue until this last system update, and nothing else has changed.
I’m looking to see if there are others experiencing this issue.
Actually, it is indicative of duplicate IP addresses, something we have seen thousands of times over the last 15 years. These happen when the router loses track of its IP allocation table due to a crash or a reboot, and starts handing out IP addresses that are already in use. The symptoms often show up after an update, because an update causes Sonos devices to reboot, and they all request a new address upon startup. So the sooner you stop insisting it is some widespread error in the Sonos firmware, the sooner we can get it fixed.
Reboot/power cycle the following, in this exact order, waiting till each comes up before moving to the next:
Router/modem
Switches/hubs
Wired Sonos devices
Wireless Sonos devices
PC/Laptops/streaming devices
Printer and other peripherals
You can also switch WiFi Off/On on your phones/tablets
After that, you can eliminate the problem entirely by going into your router setup and reserving IP addresses for all you Sonos devices.
I'm not insisting anything, I simply asked a question. Your answer… and arrogance… is not helpful…. I suggest you read in detail before you just repeat the same answers that everyone else does which have nothing to do with the question asked. Of course, everyone uses DHCP, right? And its the root of all issues…. wrong in this case. I don't use DHCP and never would…. if you really understood networking and security you would know that DORA doesn’t apply… even if you know what DORA meant… but you probably felt great in front of others that don’t know any better.
Yes, in 15 years, every issue was user configs and routers… never Sonos firmware or devices. Enjoy your little bubble and your lack of reading comprehension and technology skills.
Please close the thread.
My system seems pretty stable, and has been for some time.
As far as your problems, if you’re looking for some help a bit more information would help. Which update? Are you running wired or wireless? Wifi or SonosNet? Have your neighbours changed wifi channel, causing interference in your system? Have you rebooted your router as well as all speakers?
Is the Sonos system connected to the Orbi WiFi? Or is there a Sonos component wired (preferably to the Orbi primary node), putting the system onto SonosNet?
Thank you, but I'm not looking for troubleshooting help.
...
I’m looking to see if there are others experiencing this issue.
There have been no significant reports, and if folks were seeing their players drop off the network regularly you can be assured this board would have lit up.
Thank you, but I'm not looking for troubleshooting help. I have already isolated this to Sonos device connectivity to WiFi using IP packet analyzation with a sniffer. The data has proven there is no issue with the network, devices on the network or from any interference. The disconnect is being caused by the Sonos devices themselves…. locking up and needing a reboot to reconnect, which is indicative of a firmware or OS issue, which is exactly what was recently updated.
The system has never had an issue until this last system update, and nothing else has changed.
I’m looking to see if there are others experiencing this issue.
Actually, it is indicative of duplicate IP addresses, something we have seen thousands of times over the last 15 years. These happen when the router loses track of its IP allocation table due to a crash or a reboot, and starts handing out IP addresses that are already in use. The symptoms often show up after an update, because an update causes Sonos devices to reboot, and they all request a new address upon startup. So the sooner you stop insisting it is some widespread error in the Sonos firmware, the sooner we can get it fixed.
Reboot/power cycle the following, in this exact order, waiting till each comes up before moving to the next:
Router/modem
Switches/hubs
Wired Sonos devices
Wireless Sonos devices
PC/Laptops/streaming devices
Printer and other peripherals
You can also switch WiFi Off/On on your phones/tablets
After that, you can eliminate the problem entirely by going into your router setup and reserving IP addresses for all you Sonos devices.
I’m not a network guru, so I have absolutely no idea what DORA is. Does it replace DHCP?
It’s an acronym for the DHCP message exchange. https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol#Operation
That’s the DHCP that the OP says they don’t use.
I don't use DHCP and never would
That’s strange, since Sonos relies on DHCP.
That’s strange, since Sonos relies on DHCP.
Methinks the poster doth protest too much.
I’m not a network guru, so I have absolutely no idea what DORA is. Does it replace DHCP?
Looking at Google, it could be:
DevOps Research and Development
Department of Regulatory Agencies
A children’t cartoon (that I’m way too familiar with)
Is it one of these, or is it something else, that replaces DHCP with some other networking standard?
Do you have static reservations for your IP addresses? The most common cause of post-update problems is IP duplication.
Yep, all static IPs.
@Craigster did say he’s running with static ip’s. He hasn’t said whether he’s done a sequential reboot, starting with his router. (He also said he’s not looking for help.)