No Sonos Architectural Speakers Detected

Sorry, missed the topic title.

Since they are the Architectural speakers, and not separated from the Sonos Amp by any other device, you’re probably served best by calling Sonos Support directly to discuss it.

When you speak directly to the phone folks, they have tools at their disposal that will allow them to give you advice specific to your network and Sonos system.

I am having the exact same issue with my brand new amp and architecture speakers purchased from the Sonos website. I called their customer service and the only explanation was this could be a bug. Very disappointing. 

I would agree (on the surface) that’s a very disappointing answer. So you are saying Sonos Tech Support (STS) offered no suggestions or remedies or next steps? Did they offer to run a diagnostic? Typically STS is more helpful/forthcoming versus what you have indicated.

Yes, they ran diagnostics and had me troubleshoot a couple different connections and that was it. He said his engineers would look at my case and that it is most likely a software bug. I asked when someone would get back to me and he said he doesn’t know.

Same issue happened to me today. Pair of 6 inch in ceiling speakers and AMP ordered directly from Sonos. Installed and setup today. Tried “Optimize Sonos speakers” from the app and got this “no architectural speakers detected” error. The high pitch test sound could be heard. I contacted support and submitted the diagnostics. No solutions other than trying a different mobile phone and waiting for fixes. 😟

I have the same issue. I have two Sonos Amps with the following configurations:

1. AMP connected to two in-wall speakers: These work fine. They are detected as Sonos and can be tuned with trueplay.
2. AMP connected to four 8” in-ceiling speakers: These are not identified as official Sonos speakers, and cannot be tuned with trueplay.

I called customer support, and they ran diagnostics. I was told that this is a known issue, and received a case number (for any Sonos employees reading this). The representative did not know when the issue would be resolved, but said the engineering team is working on it.

Replying here just to share the information I have, and so that I can follow along.

For any Sonos employees: could you post an issue number, or let us know how we can follow along to know when it’s resolved? Thank you!

Moderator Note - Recorded and removed case number.

As with the many people having the same issue as me here I called support and they too said it was a bug and offered no help or solution.  So it looks like this is just a broken feature at the moment with no fix in sight.   What else should I expect from Sonos after that sh** show from last year.  

As Sonos now is aware of the problem you can be sure they are investigating it and working on a fix. Just wait and hopefully they will find a solution soon. 
 

​@Petehu 

Please do not post any personal information including your case number. If needed you can post it to a mod via pm. But I recommend to stay in contact with Sonos support directly.

The bug earlier this year took several months before it was fixed iirc. So you can expect a wait likely.  

Wow… bashing on its best imho. Why do you think that a fix will take a certain time just because in the past it might has been so? But hey… your choice always to call a half glas of water „half empty“ instead of „half full“.