Skip to main content
Answered

connect:amp won’t reset

  • February 18, 2023
  • 4 replies
  • 2313 views

Hi there

i have two connect:amps, one for kitchen, one for garden. The garden is the amp connected to router. 
 

this was working fine till yesterday. Nothing has changed. Now kitchen dropped off Sonos 1 app and I can’t reconnect and the amp won’t reset, i.e. unplug, hold buttons, get flashing lights… when I try and do the reset the light just stays solid white. 
 

 

any ideas? 

Best answer by buzz

Very likely a hardware failure. A very slight possibility is that the buttons you are pressing are defective and the unit does not actually reset. As I recall, the wired port lights will not start flashing until late in the reset process. Normally, the lights will start flashing shortly after power up. I have seen a failure where the lights will turn ON without any connection.

Avoid Factory Reset of the working unit because this will trash all of your settings.

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.

4 replies

buzz
  • February 19, 2023

Likely a hardware issue.

Another test would be to wire the Kitchen player to the network. The network port lights should not be lit until you attach the network cable. 


  • Author
  • Contributor I
  • February 19, 2023

Thanks buzz

no light when change Ethernet cable to kitchen unit… nothing at all. 
 

So guess that means hardware? 


buzz
  • Answer
  • February 19, 2023

Very likely a hardware failure. A very slight possibility is that the buttons you are pressing are defective and the unit does not actually reset. As I recall, the wired port lights will not start flashing until late in the reset process. Normally, the lights will start flashing shortly after power up. I have seen a failure where the lights will turn ON without any connection.

Avoid Factory Reset of the working unit because this will trash all of your settings.


  • Author
  • Contributor I
  • February 22, 2023

Was hardware failure. Thanks