Need help troubleshooting Sonos Move downgrade to S1

The BRIDGE is the device that can not be moved to S2. The BOOST easily runs it. 

**UPDATE 4***   (Moving from S1 to S2)

The nightmare continues plus good news.

I thought I would share my story in case it helps anyone not want to send back 800quids worth of products.

1st setup Attempt.

The new port arrived and the Move is still a paperweight.

(I have left the S1 network and products alone - Boost & ZonePlayer).

I download the S2 app and start to setup a “NEW” system, it finds the port and starts the install.
Half way through its trying to join my network and I remember the router is set to block any new devices from joining, by the time I open it up the sonos wizard had timed out.

I started again but at this point no matter what I reset, retried, rebooted or setup followed S2 couldn't find any products. About 30mins later and very frustrated it told me the port was registered to another system, so I had to factory reset it.

2nd Setup Attempt.

This is important as its not mentioned if you are upgrading from S1.
I chose the option to join an existing system. (Out of frustration).

Now this is how I expect Sonos stuff to work - easy, straight forward, pain free and fool proof.

The first message on S2 is that my system needs updating- OK.
A bit strange as none of the products are attached yet.
Neither of my new products are flashing to indicate they are being updated, so not sure what's going on at this point….. but I am moving forward.
(However, I later realised it was updating my boost - an information popup would be good).
Then it finds my Move, starts updating but fails as its not on the network yet, cancel out. (Its a known feature I knew about).
The S2 app is also now showing the Port can be added.
Port added and updated - OK.
Move added and updated - OK.

All ok and working, just waiting for indexing to finish.

Thanks all for your help.
Des.

Apologies for hijacking this thread and taking it off on a tangent.

That’s okay, so do you think the issue might have been with your router being set to block new devices from joining the network? Was that MAC address filtering, or some other device-blocking method?

Hi Ken,

No it wasn't, I turned it off on my first attempt to add the Move last weekend as I know its on.
I forgot today as I was excited on receiving my Port :)

It’s standard functionality on the NetGear Nighthawk routers (RAX200), MAC address blocking (ips can change), if your names not on the list you ain't getting in.

So probably something to do with the Sonos Boost needing an update then - Oh well, I guess all’s well that ends well. 👍

I bought a Play1 from a stranger but have been unable to connect it to my network. It appears to need to be downgraded since some of my equipment isn’t compatible with the S1. The S1 controller finds the item but asks me for an email but rejects the email with my account. Does this mean it’s looking for the seller’s email address? Is there any workaround? (This item has been factory reset already.)

This problem drove me nuts.  My solution, I created a totally different email account that had nothing to do with sonos.  That was the key to getting my Move to downgrade to S1.

I believe my email that I had used to register all my current sonos S1 products causes some Software bug to surface in the process of downgrading.   Using a totally unknown email (to sonos) made the downgrade finally complete.

Once downgraded I added the Move to my existing setup.

Rbasil,

Thanks for your post!  I was adding another used Play:1 and needed to downgrade it.  I spent several hours today with no progress.  I received all the same error messages posted above.  Your simple solution was exactly what I needed. 

I used a different email address that I rarely use to create a “dummy” Sonos account. I started the downgrade process and it sailed right through it without issue.  

Thank you so much for posting your solution.  I generally don’t post or comment, but your post deserved it. 

Rbasil, THANK YOU. I had the same problem for hours of troubleshooting while downgrading a Beam *Gen1 , and after creating a new account with a different email address, something other than my primary Sonos email address/login, everything downgraded smoothly and the Beam is now on S1.