Skip to main content
Answered

Arc won't connect to TV via HDMI cable.

  • February 6, 2025
  • 4 replies
  • 211 views

Forum|alt.badge.img

Sonos Arc won't connect to my Samsung TV.  Has been working perfectly for years.  Just quit working.  I have replaced the HDMI cable running from TV to Arc HDMI connection.  Have gone into setup mode to connect the Arc to TV but when it tests the connection, it says not connected.  My Samsung TV does not have an area in sound settings to set for Arc.  It never did and I never had to do this previously.  Hoping someone can help.  I literally have spent hours trying to figure this out.

Best answer by srssrs

My Samsung model is UN55D7000.  I contacted Sonos support and you are correct, they were able to see things I could not.  The tech I had was very thorough and super helpful.  It was determined that my HDMI-CEC was turned on but was not enabled in my Samsung TV.  On my model, Samsung calls it Anynet+ (HDMI-CEC).  The tech was not able to get it resolved.  Read on for my resolution to this.

After doing more research on this topic, several people and Sonos suggested removing everything from the HDMI ports, restarting the TV, and trying to set up TV in the Arc again.  I had a ROKU device inserted in the HDMI port just above my ARC port.  I unplugged it and then restarted my TV, then plugged the ROKU back into the same HDMI port.  I have 4 HDMI ports on my model TV.  All of a sudden my Arc started working properly and the Anynet+ showed up on my input source screen at the ROKU port #3.  My ARC is on HDMI port #2.  I am concluding that somehow my ROKU device was interfering internally in my Samsung TV with enabling the Anynet+ (HDMI-CEC) connection.

Prior to resolving this, I tried the solutions proposed by Stanley_4 and buzz, but they did not work.  I hope this helps anyone else running into this in the future.  I literally spent hours trying to resolve this before contacting Sonos support. Thank you everyone for your suggestions.

View original
Did you find what you were looking for?

4 replies

Stanley_4
  • Lead Maestro
  • 11223 replies
  • February 6, 2025

Power down both, disconnect the HDMI cable, power both up. Try setup again.

If that fails you probably need to call Sonos Support as they can see internal information we users can’t.


buzz
  • 23893 replies
  • February 6, 2025

Keep the TV powered down for at least two minutes.


Forum|alt.badge.img
  • Contributor I
  • 3 replies
  • February 6, 2025

What model is your Samsung TV


Forum|alt.badge.img
  • Author
  • Contributor II
  • 7 replies
  • Answer
  • February 8, 2025

My Samsung model is UN55D7000.  I contacted Sonos support and you are correct, they were able to see things I could not.  The tech I had was very thorough and super helpful.  It was determined that my HDMI-CEC was turned on but was not enabled in my Samsung TV.  On my model, Samsung calls it Anynet+ (HDMI-CEC).  The tech was not able to get it resolved.  Read on for my resolution to this.

After doing more research on this topic, several people and Sonos suggested removing everything from the HDMI ports, restarting the TV, and trying to set up TV in the Arc again.  I had a ROKU device inserted in the HDMI port just above my ARC port.  I unplugged it and then restarted my TV, then plugged the ROKU back into the same HDMI port.  I have 4 HDMI ports on my model TV.  All of a sudden my Arc started working properly and the Anynet+ showed up on my input source screen at the ROKU port #3.  My ARC is on HDMI port #2.  I am concluding that somehow my ROKU device was interfering internally in my Samsung TV with enabling the Anynet+ (HDMI-CEC) connection.

Prior to resolving this, I tried the solutions proposed by Stanley_4 and buzz, but they did not work.  I hope this helps anyone else running into this in the future.  I literally spent hours trying to resolve this before contacting Sonos support. Thank you everyone for your suggestions.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings