Well quick update, had a time scheduled today and never received a call. Now back to square one again.
Dang that sucks- keep us updated
Well quick update, had a time scheduled today and never received a call. Now back to square one again.
Dang that sucks- keep us updated
Yeah emailed the person in the scheduling email but shockingly haven't heard anything back.
I am experiencing exactly the same issue. Four architectural speakers connected to the same Amp and none are detected. I’m hopping that someone is able to determine the cause.
Same problem with my system. Thanks everyone for sharing
Hey everyone have an update. Spent 1.5 hours on the phone with level 2 with unfortunately no outcome. They are escalating to level 3 and will have to schedule a time with them to get on a call. We did everything to the amp including a factory reset. I even got a ladder and took a pair of my speakers out of the ceiling to give them the serial numbers. @ConanJim how old are your amps/speakers?
Ceiling architectural speakers and Amp are approximately 7 years old. Never moved them and they worked flawlessly until this issue
Ceiling architectural speakers and Amp are approximately 7 years old. Never moved them and they worked flawlessly until this issue
Interesting. Mine are roughly 2 years old and it may be a change in their design and the new S2 platform that broke them. I have a call with Level 3 this week to dive further into it.
Adding that my 4 architectural in-ceiling speakers are about 4 years old, same amp and same location. They were detected upon installation by S1. I attempted detection of the 4 speakers this last weekend with S2, which failed multiple times and after factory reset, and with 2 other amps. I spent about 1.5 hours with level 1. The result was an offer to replace my out of warranty speakers for a discount of 30% and return of the old speakers. If S2 is the culprit and is not corrected this would be a really poor instance of forced obsolescence.
Adding that my 4 architectural in-ceiling speakers are about 4 years old, same amp and same location. They were detected upon installation by S1. I attempted detection of the 4 speakers this last weekend with S2, which failed multiple times and after factory reset, and with 2 other amps. I spent about 1.5 hours with level 1. The result was an offer to replace my out of warranty speakers for a discount of 30% and return of the old speakers. If S2 is the culprit and is not corrected this would be a really poor instance of forced obsolescence.
It would be greatly disappointing if S2 broke the older speakers. Even more so SONOS never mentioned their discontinuing. I have a call today with level 3 support and will update here.
Same exact issue here. Eight brand-new ceiling speakers; four brand new Amps that seemingly don’t recognize any of them. Hopefully Sonos recognizes this is not an isolated issue.
Brand new! I think that convinces me this is an S2 issue and not hardware.
Same exact issue here. Eight brand-new ceiling speakers; four brand new Amps that seemingly don’t recognize any of them. Hopefully Sonos recognizes this is not an isolated issue.
Just to make sure, they are SONOS Sonance specific in-ceiling speakers?
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!
Having almost the same identical issue, goes from no speakers detected to speaker mismatch. Brand new Sonos architectural speakers, sonos arc ultra, and an older amp.
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.
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.
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.
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 ?