pairing with my sonos move with iphone 16

4 replies
463 views

Just got a new iPhone 16 which pairs with other devices. However it’s not pairing with Sonos move. Has anyone had this problem & how did you resolve it?

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.

Gabriel ZAnswer

Enthusiast II

Hey @StargazerLily, welcome to the Sonos Community!

Sorry to hear you are not able to use your iPhone with the Move. Are you trying to connect via the Sonos app or Bluetooth? The Sonos Move needs to be set-up on a WiFi network before Bluetooth is available for pairing.

Hope this helps!

Mark good posts by pressing the like button, and select the best answer on questions you've asked to help others find solutions.

Gabriel ZAnswer

Enthusiast II

Hey @StargazerLily, welcome to the Sonos Community!

Sorry to hear you are not able to use your iPhone with the Move. Are you trying to connect via the Sonos app or Bluetooth? The Sonos Move needs to be set-up on a WiFi network before Bluetooth is available for pairing.

Hope this helps!

Mark good posts by pressing the like button, and select the best answer on questions you've asked to help others find solutions.

S

StargazerLilyAuthor

Contributor I

Thank you. Sonos support was able to get it working. Thank you for responding.

E

Egesq

Lyricist I

Hello. I'm having the same issue and have been on with Sonos for over an hour. My iphone 16 doesn't connect anymore but my gf’s iPhone 13 does. How did Sonos fix yours? Thank you.

S

StargazerLilyAuthor

Contributor I

I’m not sure what support did on their end. I had shut down my phone completely, then restarted. I updated my Sonos app. I made sure I was connected to my WiFi. I tried to connect to Sonos and failed. At this point I ran diagnostics which gave me a ref# to give to support on the phone. I made two attempts to connect to my Sonos via Bluetooth (with support on the line) and failed. The 3rd attempt was successful. I assume support did something on their end, based on the diagnostics, to fix the issue.

Sign up

Login to the community