Skip to main content
Contributor I
April 23, 2022

Lost surround and sub ( after update ?)

  • April 23, 2022
  • 1604 replies
  • 81296 views

Hi 

I don’t know if my issue is related to the 14.6 update but I noticed today that I had no sound from my surround (play 3) and my sub (Gen 2), only the Arc is working They are still present in the app under the my System view but now sound which every sources

When I reboot each of them, the sound comes back temporary, but when I switch to another source or audio format, thé Sound disappears again. Tried several times, same behavior

Thanks for your help

 

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.

1604 replies

Trending Lyricist I
May 4, 2022

Connection problems which appear suddenly are often caused by network problems, not Sonos problems.  The  typical cause is duplicate IP addresses.  These often show up after an update or power outage because a reboot requires the device to request a new IP, and the router, having lost track of current IP assignments, issues a new IP that is in use by another device.  To cure this, do the following:

Reboot/power cycle your devices in the following order:

Modem
Router
Switches or hubs
Wired Sonos units
Wireless Sonos units
Computers/printers
Wireless devices - phones/tablets etc.

Allow each device to come back up before proceeding to the next.  Note that you can permanently prevent duplicate IP addresses by assigning an IP to each device's MAC address in the router setup.  See your router manual for details.

None of this works.

I’ve tried hard wiring, I’ve tried IP reservations across my whole network (even as far as breaking my groups up and reserving before regrouping them), I’ve tried rebooting the modem, the router, the AP’s.

The only thing that fixes it for me is rebooting the surrounds, sub, or Arc.  Which means it’s an issue with the Sonos Arc communicating with its OWN wireless signal to the satellite speakers.

Sonos messed up, they owned it for 5 minutes - and are now trying to back pedal on it being them.. just so they can have all of us submit multiple diagnostic reports repeatedly till they can find their own smoking gun.

This needs a patch to fix it, nothing else.  There is this thread and others reporting the same issues, reporting the same suggestions from sonos, and reporting that everything sonos suggests does nothing to fix the issue.

Flo14000
Lyricist III
May 4, 2022

please stop saying it's a network or IP address problem! it's your 14.6 Sonos update that's causing the problem, so get to work on a new update that fixes all that! otherwise it will be back to Bose for me!!!!

jgatie
May 4, 2022

please stop saying it's a network or IP address problem! it's your 14.6 Sonos update that's causing the problem, so get to work on a new update that fixes all that! otherwise it will be back to Bose for me!!!!

 

Please stop reacting as if the people giving advice actually work for Sonos!  

Airgetlam
May 4, 2022

Is this the same BOSE that’s purportedly laying off people? 

I see a lot of “me too” posts, but not a lot of interaction (which may be hidden, don’t know) with Sonos in providing them hard data via diagnostics about what the potential issue is. There have been a few people in this thread who have at the least provided diagnostics, and I’m thankful for that, and hope that Sonos is too.

In 99% of the previous issues like this, it has indeed been as @jgatie suggests. If you feel it’s different for you, posting here may not be the best way to resolve the issue, but engaging directly with Sonos support and providing them hard data/evidence from which to work would likely be much more helpful. 

Bruce
Flo14000
Lyricist III
May 4, 2022

J’ai soumis 4 diagnostic à Sonos aujourd’hui. Je parle en français marre de faire la traduction !! 

peterbault
Enthusiast II
May 4, 2022

working directly with sonos support and submitting a diagnostic just results in them asking me to power cycle everything which of course fixes it temporarily but it just eventually comes back.

 

what else am I supposed to do?

Airgetlam
May 4, 2022

Génial. Qu'est-ce que Sonos a dit en réponse à ces diagnostics?

D'après ce que je vois, peu de gens ont été aussi proactifs que vous, malheureusement.

Bruce
Flo14000
Lyricist III
May 4, 2022

Sauf que je ne sais plus quoi faire pour que Sonos décide enfin de régler ce problème ! Alors oui désolé, je sais que vous ne travaillez pas chez Sonos, mais si vous avez lu le fil depuis le debut, vous seriez au courant que ce n’est pas un problème de réseau !! 

Flo14000
Lyricist III
May 4, 2022

A part dire que ça vient de notre réseau, rien d’autres ! Alors vous avez une solution ????? 

Airgetlam
May 4, 2022

I think you’ve done what you need to, at this point. What I would thing would help (or hearing about) is more people submitting their own diagnostics to Sonos, like you and @Flo14000 seem to have done. 

Right now, they’re claiming it’s not an issue in their software. They may be right, they could be wrong, I don’t know, but the more people who supply hard data, beyond the “me too” posts, will certainly help if it is indeed a Sonos issue. Bug reproduction in software is often a very difficult thing, and more so if the issue is in transmission across wifi, for instance. The more hard data provided, the better the chances of figuring out if this is indeed a software issue. Right now, Sonos is pointing at potential issues elsewhere.

In the past, when there has indeed been a software issue, they’ve owned up pretty quickly, and it took several weeks for them to get the bug ironed out, tested, and rolled out.  

Yelling at them in the forums, which is not what you’ve done, but others seem to be, is unlikely to help. Providing them hard data to prove the point, one way or the other, will always be a better path. And either support your contention, or allow them to point at other possibilities. 

Just as a note, that last time it was a serious bug in their software, there were thousands of posts in 24 hours. This current issue appears to be affecting fewer people, although there has been evidence of posts in other areas that would likely be less helpful to Sonos. 

Bruce