Sonos Connect - cannot factory reset (flashing orange-white, never green)

  • 2 November 2022
  • 43 replies
  • 1027 views

Hi,

I hope you can help me reset my Sonos Connect.

After applying power with the pause button depressed, then releasing the pause button after about 15 seconds:

  • the led flashes white/orange forever
  • the led does not transition to green.
  • the network port (cable connected) flashes so the switch and network is working.

I have tried other combinations many times without success.

Any ideas please?  

Thanks

Rich


43 replies

They told me that unfortunately my Connect is broken and not repairable. I could start an RMA procedure. I‘d need to send back my Connect in order to get a 30% discount on a new device.

gave it a try, did not work. thank you for all the support.

Same exact issue as shared by many others , Sonos Connect flashing orange.

This cant be a coincidence with this many incidents , must be a known issue, 

I understand my Connect is from 2015,  but still should not go dead….or Sonos should be clear upfront that their products last 4-6 years. Am not interested in buying something else that will die in 4-6 years.

 

 

I have a CONNECT from 2010 that is still working. This community is similar to a hospital -- after a quick walkthrough you might jump to the conclusion that “everyone” is sick. We don’t know what the ultimate life of these units will be. For any manufacturer’s product a few fail on day one and along the way. In the 8-10yr range the failure rate will start creeping up. Lots of original 2005 units are still functional. Each product has an age related characteristic failure. If you go to a large service center with a broken product, as soon as they know the model number, before you speak, they likely know the issue. This doesn’t mean that all units will fail, only that when they do fail, they tend to follow a pattern.

More likely caused by the Illuminati. 

Mother nature is never fair. At some point all electronics will fail. Failures tend to be age related and the failure signature will change with age. Large service centers become familiar with a given model’s failure signature(s). If you simply give a model number, the center can likely describe your symptoms. If production control on model XYZ is very tight, all or most XYZ’s will fail at approximately the same time. This failure could occur after a few days, weeks, or decades. Warranties are designed to protect the user from manufacturing defects that will show up in the early weeks. It is possible to design units that have an expected life of decades, but these units cost more than a few hundred dollars.

I’m aware of a high quality speaker design that suddenly started experiencing problems. A driver would simply fall apart. This was new production. Production from years past was not having issues. Worse, the replacement part would fall apart in shipment. It took a few weeks to shake this out, but the failure was ultimately traced to units assembled over a three day period by one individual on the production line. Naturally, customers were annoyed, but protected by the warranty.

If you think that a unit has failed too soon, it pays to check with the manufacturer because there may be a known issue that affected one batch of product and the manufacturer might extend the warranty on that batch.

Hey Buzz,

 

I don’t think that it failed too fast, per se.  I just think it’s curious that so many of the same model had reported failures around the same time.  

To some extent this is a hospital. Here, “everyone” is sick. Unfortunately, we don’t have enough data to declare that xx% of the units have or will fail with this issue at this point in the unit’s life. With a large complex device, such as an automobile, an ideal product characteristic would be that all subassemblies would turn to dust on the same day. This would save the owner from experiencing an ever increasing string of more and more expensive repairs until ultimately deciding that no more attempts should be made to support the remaining usable parts.

Bottom line: There are no user remedies beyond reboot or Factory Reset. The cold Factory Reset has helped a few users for an unknown period. SONOS does not repair units or provide any repair documentation.

There are a few 3rd party repair agents in Europe that could likely repair the unit. If you are a DIY, there may be some discussions about this issue, however, replacing memory will require surface mount soldering skills.

That’s curious. My 2010 CONNECT is wirelessly connecting via WiFi. Describe your WiFi hardware for us. CONNECT’s use some older WiFi standards that some WiFi access points block by default. If you can configure your router, make sure that “b/c compatibility” is enabled. Note that some routers do a bad job of this and will slowdown overall throughput.

Absolutely - just had the same issue on a previously perfectly-working Connect:Gen2 !

by the way, thank you for taking the time and making suggestions, I appreciate your help.

 

More evidence suggesting a hardware issue. While not a fix, simply powering down the unit for a couple days might allow it to Factory Reset. This is more proof that there is a hardware issue. If there is a temperature issue, the “cooling off” might help, but only till the unit warms again.

The hardware failure could be vexing. Let’s postulate that a section of memory fails at a certain temperature. Factory Reset and update moves lots of stuff around in memory -- increasing the risk of stumbling over the intermittent section. If the Factory Reset and any updates are successful, and the bad memory is now not in use, the unit could continue working for a while -- until there is an attempt to use that bad section. This could be days, weeks, or months from now, long after you’ve disconnected your brain from this current problem. Then you’ll start looking for a seemingly unrelated problem because this problem was “fixed” long ago.

Keep us posted. 

I have exactly the same issue, was any fix found?

Same issue. I can get all the way to this screen with my connect amp but the flashing light never goes green this is where everthing dead ends as a result. Did everyone give up on this issue?

There has to be a fix somehow.

 

Any fix? Flashing orange and white, it never turns green....

Same exact issue as shared by many others , Sonos Connect flashing orange.

This cant be a coincidence with this many incidents , must be a known issue, 

I understand my Connect is from 2015,  but still should not go dead….or Sonos should be clear upfront that their products last 4-6 years. Am not interested in buying something else that will die in 4-6 years.

 

I contacted Sonos Support, got a case number. I was told the network card on the Connect is no longer compatible and can not connect to my wifi. They offered a 30% discount towards a new item. Knowing the Connect replacement has been out for 3 years, not sure its worth buying.

I am a Sonos fan and customer, with 10 Sonos products in my household, I understand technology can age. Time to go back to all analog, and only get a streamer that can be replaced every 4 years.

 

Same issue. Sonos Connect working fine. Gone for 3ish weeks, when I come back app can not detect and can not factory reset. Nothing here ?

Have you tried to call Sonos Support directly to discuss it?

This is suspicious, could Sonos have deliberately sabotaged the Sonos Connect, or made a mistake in the software update? I also have the same problem here.

I have had contact with Sonos Support and conclusion was: device is dead, that’s what orange-white flashing light after factory reset means.

I have the same issue.  Went away for 2 weeks (with the Connect:Amp plugged in and on), but upon my return it did not work.   Same issue as OP and others above.

 

I have 4 Connect:Amp devices, and the other 3 work fine.  All are hardwired with Ethernet.

 

Factory reset was not helpful - I can get to the point where it asks to press the button (which I do with all of my might), but with no positive result.

 

 

I am not sure what to do, now that I have 3 working Connect:Amp devices and one broken one.  I suppose I could buy another one (used on eBay or something). 

 

It does seem like a lot of us are having this problem all of a sudden, but again we are a self-selecting group.

 

If anyone makes any headway, please keep this group posted.

 

Hey Buzz,

 

I don’t think that it failed too fast, per se.  I just think it’s curious that so many of the same model had reported failures around the same time.  It’s not really a question of philosophy, nor of the lifecycle of electronics.  The real question is whether the failed unit can be resurrected or not (and if so, the steps to do so).  I think that’s the only question that the owners of these failed devices have.

As much as I respect the opinions provided, it’s a binary question.  Can a failed unit be made to work again?  That’s it; none of the other hand wringing or pontificating has any practical application.  Thus far it appears that the answer to the question is no.  There has not (yet) been a remedy discovered.

my wi/fi set up is pretty straight forward, its an Xfinity wireless router,  

everything including my current Sonos system with multiple speakers and Boost work well , the only thing that can not connect is the Sonos Connect.

my wi/fi set up is pretty straight forward, its an Xfinity wireless router,  

everything including my current Sonos system with multiple speakers and Boost work well , the only thing that can not connect is the Sonos Connect.

Maybe see if this will work for you which I found in a search for your router…

Xfinity Router

  1. Navigate to https://internet.xfinity.com/
  2. Sign in with your Xfinity xFi account
  3. Once logged in, click the Devices or Connect tab, then click on the Paused Sonos device
  4. On the following page, click on the Unpaused Device button
  5. Click on Apply Changes to complete the unblocking process of the device
  6. Repeat for each Paused Sonos device
  7. Once completed, the Sonos Player(s) will be able to connect, register, update, or stream. You may need to reboot the affected Sonos component(s)

Reply