Skip to main content
Avid Contributor I
July 27, 2023
Answered

Difference between latest Port and earlier Connect Gen2

  • July 27, 2023
  • 24 replies
  • 28431 views

I have made the decision to stick with Sonos and upgrade all of my Sonos kit to S2.

My question now is whether for the Connect/Port component there is any benefit in having the current Port vs the Connect Gen2. It appears to me there is no clear benefit in using the newer box.

I ask because the Port costs £499 each in the UK before trade-in discount. The Connect Gen 2 is readily available used for about £150. I need several.

Thanks as always for any insights.

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.
Best answer by GuitarSuperstar

From the Sonos website:

How is Port different from Connect?

Port is the successor to Connect, delivering richer sound and extending the Sonos platform to traditional audio equipment. Port includes an updated digital-to-analog converter for clearly detailed sound and a 12V trigger, which automatically turns on your amplifier to more reliably initiate playback. Port also allows you to control content using Apple AirPlay 2 and features a versatile design compatible with a standard AV rack.

24 replies

July 30, 2023

How about short term memory starting to go as a better excuse?!

buzz
Grand Maestro
July 30, 2023

You know you’re getting ‘mature’ when “short term” is six years. 😀

July 30, 2023

Add to that the way these/similar fora are structured, to make matters worse! Which is why I have a folder in my computer of screenshots of key/relevant posts, so that when I need to access these for troubleshooting, I can just refer to that one folder.

Contributor I
August 5, 2023

I’d stay away from the Connect.  I’ve got an S2 Connect and it loses sync with the rest of the Sonos network gradually.  (A bunch of people have reported this problem - search the forums for Connect Sound Out of Sync or similar.). I’ve created a workaround for now by hardwiring the Connect to the router and selecting the Connect as the head node for any group it’s in, but your case may be complicated.  At least one user here has reported that replacing the Connect with a Port fixed the problem, but there’s been no support from Sonos on the issue.