Sonos Move disappearing on Airplay

Airplay issue - see this link here and the information mentioned by Sonos Staff:

https://en.community.sonos.com/general-feedback-and-conversation-229090/suddenly-cannot-find-airplay-on-sonos-move-6879260?postid=16637363#post16637363

@waynetempro 

All my devices are updated to 14.10 but the issue persists.  I think the issue on this thread is different than the Suspend issues others were having with their Moves not restarting after entering Suspend mode.  The 14.10 update addressed that, apparently.  

The issue on this thread is more one in how Apple Airplay recognizes the Move speakers.  This used to be seamless, but now, Airplay will only display one Move at a time.  Yes, you can connect to all SONOS Moves via the Sonos app, but things were much more functional until maybe about 3 months back.

Can Sonos confirm if this is a known issue for us on this thread?  Nothing has changed about my network over this time frame.  The problem began with either a SONOS update or an IOS update that now keeps the Moves from playing well with Airplay.

I have the same issue here. Only one Move speaker (out of 6) will appear in the ios airplay selection list. It is always the last one discovered by the ios device. If you have the ios device forget the network, then re-attach it to the network, the first time you open the ios airplay selection you will see it list all of the Move speakers one at a time. each one overwriting the previous one. To have ios show a specific speaker so you can select it, you must remove the speaker from the charging base and power it off. wait 10 seconds and place it back on the base (it will power on). Watch the ios airplay selection list and it will be the one listed once it is discovered and then you can select it. All the speakers are available in the Sonos app. Spent hours debugging with Sonos support and their “official” answer was: It is an Apple problem. It appears that we now have a finger pointing game between Apple and Sonos as Apple cannot determine the difference between multiple Move speakers.

Using latest iOS and Move is plugged in.

I’m not going to start messing with my router or Wi-Fi given I have not changed any of these settings in recent memory.

Resetted my iPhone network settings and still the same.  Wasn’t expecting this to work as this is happening to my iPad too.

I guess I will have to stick to using the Sonos app in the meantime until this gets sorted.  I did update iOS a few days ago and maybe this is the root of the issue…?

That’s strange, I have two ‘Moves’ as mentioned in my earlier post with screenshot attached and my Wife and I have iPads, iPhones and Apple TV (x2) and they all see the two Sonos Moves and our Sonos Roams too.. it sounds like your network/router is doing something to the iOS Airplay discovery service? 

edit: Perhaps see if the below links may assist you to begin to find an answer to this issue:

https://support.apple.com/en-gb/guide/deployment/depf138dd79c/web

https://support.apple.com/en-gb/guide/deployment/dep9151c4ace/1/web/1.0

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.

Well for the AirPlay/Bonjour service you will need all on the same subnet and if using extenders, then I would put all on the same SSID/WiFi Band & Channel and set the same channel-width too (preferably 20Mhz only), but some extenders can cause issues with multicast broadcast discovery. 

These things can often boil down to issues with the local wired/wireless network segments. You only have to search online to see the various issues users have reported with Airplay and a good many do not involve Sonos at all

I am still seeing this issue and unlike others, no amount of Sonos Move, iOS network nor router resets have led to my 2 Move’s getting unique Airplay “deviceid”s.

What is interesting is that my Moves both get the “00:0C:43:37:90:D1” deviceid, like @jeremyrwc, which is not a MAC address of either device, although it is in the format of one. When @jeremyrwc got his Moves working, one of the Moves obtained what I presume is its MAC address, the other one kept the MAC-address-like deviceid - “00:0C:43:37:90:D1”. My Play5 gets a deviceid assigned corresponding to its MAC address. The Airplay convention seems to be to use the MAC adddress as deviceid as per:

https://openairplay.github.io/airplay-spec/service_discovery.html

The “00:0C:43:37:90:D1” MAC address is owned by Ralink Technology Corp which is a WiFi chipset manufacturer which perhaps Sonos use. The MAC address of all 3 of my Sonos devices are reported as being owned by Sonos so I can only guess that Sonos are using a default chipset based MAC address as deviceid in some circumstances, perhaps when assigning a stereo pair which needs a distinct airplay address. I did note that to from a stereo pair I had to sign into Sonos, so there could be some hangover in our Sonos Cloud account that survives factory resets. 

I cannot see how this is not a Sonos bug, their software announces the Airplay deviceid, they have complete control over it, but some of us (maybe all who have formed a stereo pair and later tried to use Airplay to each speaker?) seem to get stuck with.

I will try and log a support ticket again but hopefully this thread helps …

@Sonos, are you out there?

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. 

@jack_a

That app is helpful!  As predicted, both my Sonos Moves are showing up in the Discovery App with the same Remote Audio Output Protocol address, despite different IP assignments and different MAC addresses.  Unfortunately, resetting the network settings on my iphone did not work for me. Both Moves still have the same AirPlay address.  I’ve also done a router reset and still, no luck.

I’ll try to look into how to better reset these airplay assignments, but if any Sonos officials or other forum members have a clue, please chime in! 

Thanks

p.s. I currently have 3 Apple TV’s and two Ipads, two iphones, as well as iTunes on a PC all on my home network.  Perhaps those are keeping the RAOP address from being reset?  It’s going to be a pain to reset all network settings for every single device.  I am looking for a better option. Particularly since this all worked seamlessly a few months ago...

I too have had this problem for a couple of months now. My network has 3 Moves, a Roam, and various Apple devices…all coexisting and working flawlessly on Airplay (I never used the Sonos app to stream music).  A couple of months ago I noticed only one Move was showing up, I cycled power, cycled my network, etc. and like another poster said, the last unit I cycled would replace the other, etc. 

As a workaround I’ve found that I can start playing to all my Airplay devices including whichever Move happened to show up, then go into the Sonos app to add the other Moves to the active stream. Although not as seamless as controlling them all in the Airplay menu this has worked reliably and allows for individual volume control. 

I have tried all of the steps mentioned in this thread including removing, resetting, and re-adding all my Moves. This problem is isolated to my Move speakers as my Roam consistently stays on my list of Airplay available devices. I even had an old iPad on IOS 14 that I dusted off to see if it would see all of the Moves…no luck.