Sonos Move disappearing on Airplay

Alas, with Support I worked through a few troubleshooting steps (including switching to Sonosnet, enabling groups with the missing speakers etc) but it came to naught and they suggested I try again over the phone at a later time.

I’m so happy I’ve found this. I have the same issue. Tired everything including reaching out to support. And it only affects the Move’s. They blame apple, but all the other devices work. I wish they would fix this. It’s very annoying to deal with. 

OK, so suddenly, for the first time in months  my Sonos Moves are now both recognizable.  Looks like last week my Move speakers auto-updated to 14.14, and I’m guessing that solved the problem?  I’d love others to chime in to see if their problem is fixed, too.  I’m seriously pumped things work the way they used to, but I am a bit disappointed in SONOS blaming Apple when it was as SONOS update that both killed the functionality and then repaired it. After the 14.14 update, my two moves are finally showing different Remote Audio Output Protocol ID’s where-as before they were the exact same.

 Anyway, though they didn’t respond on this thread, and they were little help on support calls, it looks like (for me at least) the problem of being able to see my two Moves on AirPlay has been fixed.  I would love to have the hours and hours of troubleshooting back in my life, but c’est la vie.  Still love my SONOS system.  Just wish I hadn’t been gaslighted into thinking the problem was on my end when I didn’t change a single thing in my system other than allowing ‘auto-updates’ for my SONOS and Apple devices.

Let me poke @nowislife @graham1980 @jack_a @Robert62 @jshadow @Ken_Griffiths @ahcl20 @Robert62 to see if you guys’ problem is fixed.

Finally Happy (as long as it’s still working tomorrow...)

-Sully

@HungryWookie,

I reset both my Moves a while back, prior to the last Sonos update and all started working for me prior to that v14.14 release and each speaker had different remote audio output protocol identifiers and continued to work fine, so I’m not sure who fixed the issue behind the scenes. It might have been Apple, or Sonos, or both.

Both speakers have continued to work/airplay for quite some time and I’ve just checked and both RAOP ID’s have remained unique/different. 

I do believe that whenever companies fix these sort of issues they usually just include them as ‘bug fixes’ in the comments/remarks released with their updates  - neither Apple or Sonos (or other manufacturers/suppliers) tend to ever give a comment much beyond that.

I have an ongoing issue now for example, with (zoomed in) text selection on an Apple iPad Pro screen causing it’s display to often scroll to the top of the page, but Apple appear to not be keen to comment on that issue aswell.

All three of my Moves were accessible in the Airplay menu for about a week, but now they have reverted back to cloning each other. Still not fixed. 

Did you check the RAOP ID’s before/after the latest S2 updates @mullenjsm? Just wondering if you did ever factory reset them to ensure they each had unique identifiers to begin with, going into the update.

My two Moves have kept their unique identifiers (for a long time now) but I did have to put them right to begin with.

Happy I’ve found this thread but unfortunately, seems the Move might be playing up again. I’ve read through the thread and tried all suggestions but for the life of me I cannot get my Move to stream via Airplay from any iDevices via Apple Music yet I can stream via Airplay to my Beam (Gen 2) fine on the same network from all iDevices from Apple Music. 

The Move and Beam are setup fine on my Sonos account and both are visible in Airplay on Apple Music on my iDevices but no matter what when I cast via Airplay on any iDevice to the Move from Apple Music, the move hits me with ‘Unable to connect to ‘Sonos Move’’. To compound matters my partners android phone can cast to the Move fine and Spotify Connect works fine to the Move on all iDevices so it leads me think its some Airplay/Apple Music iDevice protocol issue. I can use Apple Music on the Move fine on my iDevices using the SONOS companion app. 

Move and Beam both updated to 14.16 and S2 - any suggestions before I drop-kick the Move into the stratosphere? 

Sure. Submit a diagnostic when you’ve experienced this issue, and contact Sonos support. Let them look at the diagnostic, and give you information about what the hard data is showing.

Maybe try this out; helped me with Moves going offline when moved around the house (different access point zones): https://community.ui.com/questions/An-optimal-configuration-for-a-Unifi-Managed-Network-and-Sonos/4819df0b-cc15-43b1-8f8f-4ca36c486f1c#answer/ef0a895d-5ec8-4522-9000-ce0ad73ef1dd

I have 2 Sonos Ones and a Sub Mini as my Living Room system. I also have a Sonos Move that I have to connect to the system separately. I recently got a new modem and so changed my network settings. Since then either the Living Room system, or the Move, or both constantly drop off Airplay. They are still connected to the app, but just drop off all my Airplay lists on all my devices.

When I unplug them and turn them back on, they reconnect for a couple of hours, then drop off again. It’s driving me mad! I’ve tried various sequences of unplugging the modem, unplugging the speakers, unplugging both, but nothing works for more than a few hours. Sounds like the same problem. Hoping someone finds a solution!