Skip to main content
Trending Lyricist II
October 16, 2024
Answered

Amps no longer “see” Sonos Architectural speakers

  • October 16, 2024
  • 53 replies
  • 1585 views

Hello,

 

I moved some furniture in my office and decided I wanted to use TruePlay again. I went in the app and when it went to confirm the speakers it came back as failed. I have 3 different amps with 3 different pairs of Sonos architectural speakers that aren’t working. I’ve had this setup for over 2 years and nothing has changed which leads me to believe it’s software based. Has anyone else noticed their amps not “seeing” the Sonos speakers?

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.
Best answer by KHeinold

Hey everyone I have news: they have updated the app/system and fixed the issue. I received an email this afternoon from Sonos staking they have fixed the issue and was told to look for an update in my system. Went in the app and checked for an update and sure enough one was found. After the update all amps/speakers are working as they should. 

53 replies

KHeinoldAuthor
Trending Lyricist II
November 19, 2024

Hi ​@KHeinold  et al,

I wanted to update this thread for you all as our team have discovered a bug impacting Sonos Architectural Speakers detection when attempting to Trueplay and I’ve marked this thread as having this issue. We are investigating the issue and do not currently have an ETA, but hope to have this fixed as soon as possible. If I hear any more information regarding this, I’ll update this thread.

Thank you to ​@KHeinold for your troubleshooting with our team through the levels of support and to anyone else who called in to report this, in turn helping the bug report be created and progress.

Please note: This bug only occurs when using the Sonos Amp with Sonos Architectural Speakers on the new Sonos app.

I hope this information helps!

Are we going to be given an update on this thread when you guys do fix it?
I have 2 Architectural Speakers installed as of today and connected to my amp that cannot be detected.

I’ve been told I would receive an email since my support ticket is linked to it. If I hear anything I will post here. 

Jamie A
Sonos Staff
November 20, 2024

Are we going to be given an update on this thread when you guys do fix it?
I have 2 Architectural Speakers installed as of today and connected to my amp that cannot be detected.

Hi ​@mariogdi,

Most likely is that you’ll see the fix on your system before I or any other moderators post a reply, it’s common for other users to notice an update has fixed their issue and come back to the relevant threads to post an update. But in the case the issue is resolved, we’ll update this thread to let everyone know. 

 

Also, like ​@KHeinold said

I’ve been told I would receive an email since my support ticket is linked to it. If I hear anything I will post here. 

This is correct, and if anyone else has called in to discuss this with our support team and have a case number, then it will be linked to the issue and an email will be sent out once the issue is marked as resolved. 

Contributor I
November 24, 2024

I wish I had read this before I went through the pain of upgrading my S2 compatible devices.  It’s taken best part of 6 hours and I still have one Move (Gen 1) speaker to do - it’s incredibly annoying I have had to buy an Ethernet to usbc adapter to do that update - why don’t Sonos include one with the speaker !.  Now I find my Sonance speakers are not detected … by far the worst upgrade experience of any devices I’ve purchased in the last 4 years.  To top it all the S2 app is just awful..  not sure who designed it but I’m guessing they don’t use it (and laggy to boot).

 

come on Sonos - you can do better than this - surely ?

 

 

 

Lyricist II
December 7, 2024

+1 having this same issue 

Lyricist I
December 8, 2024

I also discovered this issue yesterday when I added two new ceiling speakers to my setup 

KHeinoldAuthorAnswer
Trending Lyricist II
December 12, 2024

Hey everyone I have news: they have updated the app/system and fixed the issue. I received an email this afternoon from Sonos staking they have fixed the issue and was told to look for an update in my system. Went in the app and checked for an update and sure enough one was found. After the update all amps/speakers are working as they should. 

Contributor I
December 17, 2024

Good to hear this is resolved for you.  Unfortunately even after updating I still have the same problem.  The Sonance in wall speakers are not detected.  
 

nothing changed in terms of moving any components it was simply the update to S2 that has cause it.

 

recently added an Era 300 and Move 2 (hence the need to upgrade everything to S2).

 

wish I had not bothered now - would have saved myself £700+ and had a fully working system. 
 

 

KHeinoldAuthor
Trending Lyricist II
December 17, 2024

Good to hear this is resolved for you.  Unfortunately even after updating I still have the same problem.  The Sonance in wall speakers are not detected.  
 

nothing changed in terms of moving any components it was simply the update to S2 that has cause it.

 

recently added an Era 300 and Move 2 (hence the need to upgrade everything to S2).

 

wish I had not bothered now - would have saved myself £700+ and had a fully working system. 
 

Sorry to hear that. All I can say is make sure your app is up to date and that your Sonos system is also up to date. I had to go into settings and look for a system update and one showed up. 

Stanley_4
Grand Maestro
December 17, 2024

Good to hear this is resolved for you.  Unfortunately even after updating I still have the same problem.  The Sonance in wall speakers are not detected.  
 

Just to be sure, you bought the Sonance speakers from Sonos and got the customized ones Sonos sells, not the similar but stock Sonance ones?

Contributor I
December 17, 2024

Hi

 

Yes they are the Sonos Sonance speakers ..  however I realised the update was to the components not the app (I had an app update in the App Store so assumed it was that )…

 

then noticed in the app the components also had an update and having done that they are now detected …

 

so all is well now - my stupidity !

 

thanks