Can you explain what you mean by recognised but won’t register?  Do you mean that you are unable to add the devices to your system?

Registering speakers (I suppose you mean re registering with Sonos) should not be necessary when changing.

In my own use-case I followed the instructions in the Sonos Support document (link below) last time I switched WiFi network/credentials (about 3 weeks ago) and all worked fine back then …all my devices run on WiFi, but there’s always the option to use a SonosNet connection instead.

https://support.sonos.com/en-us/article/connect-sonos-to-a-new-router-or-wi-fi-network

Explaination of recognised bu wont register.
The devices are recognised in the app, and are tested noise pings, and are added to assigned room.
The app then tries to register the device but fails, pops up a message with a fix bar, but fails.
This happens for 2 x Play 1 and a PlayBar.
dedicated ip addresses are assigned to all sonos units.
The wifi location is confirmed asame as app

Its just ias if the app gets confused during registration.

Yes I factory reset the Play1 and Play Bar as these earlier products dont have BLE capabilities,

Maybe try a different DNS in your router settings such as cloudflare or Google public DNS - ensue there are not things like Pi-Hole or other blockers that are blocking the registration.

CloudFlare DNS:

1.1.1.1 & 1.0.0.1

Google DNS:

8.8.8.8 & 8.8.4.4

Ken TY actually spent my life in IT former programmer, built data centres for major EU financial institutions, I have a very deep undestanding of networking and security. There is nothing blocking the Sonos App like very many other people the App just fails, doesnt give an error code or log to look at, which makes it very difficult , impossible for users and Sonos owners to diagnose. 


 

Dunno then - but since the new App was launched on May 7th I’ve setup a fair few Sonos products for myself and family and not encountered any registration issues - that said it doesn’t include old players, like the Play:1, or PlayBar, so I can’t assist, but I assume you’ve tried a SonosNet connection in place of your WiFi connection (or vice versa), just to see if that perhaps might work for you?

Yep I think the new app is pretty good for the new products but not so goo for older products.
Which is a shame since the older speakers are still sound great and can function BUT its just the app that letting them down.
The app needs to give error codes that can be looked up by users and then more easily fix.

Lack of storage, or memory, perhaps?- but personally speaking, I’d be really surprised if that was a factor, particularly as you did mention you had wiped them with a factory reset and I’ve seen other community users mention they have Play:1 & 3’s, PlayBase and PlayBar up and running on the new Sonos App and it seems they're all in a similar position in terms of hardware. (See chart below).

So not sure why you’re seeing the issue. Again I can’t  test these things here as I’ve no longer got anything that old, but maybe others who have, might chime in here.

As you say storage and memory ruled out as I have Factory Reset each product.
The wierd thing is they get recognised, sound tested/identified,  added , it at the final registration that fails.

@Acloud,

I take it that you did go onto create a brand ‘new’ Sonos Household after you factory reset your products, rather than attempt to use the existing Sonos HH within a non-reset App and that your current setup meets both the system and mobile controller device requirements mentioned in these two Sonos Support links?…

• https://support.sonos.com/en-us/article/sonos-app-requirements
• https://support.sonos.com/en-us/article/sonos-system-requirements

Ken, Yes. Again without an error code that tells users why the app has got stuck and failed final registration on the account of the devices, despite recognising them, updating firmware, doing the sound link sucessfully, adding to the room, and then getting stuck in registration which by that time is an app process not a device issue, there is very little that a user can understand or do. 

Ken, pleased that your experience with newer products has been sucessful, but very different from mine with older products. Also there are very many older Sonos product owners with similar problems.
I fear this will only be resolved with the application providing clear error codes to user to explan why any of the process steps fail. I think its been recognised that the Sonos software app has been a problem, not that ist geting regularily updated but doesnt seam “fit for purpose” for me and puts me off buying any more Sonos products, when other manufacturers dont appear to have these software problems.
Its a shame that a fantastic sound hardware product is let down to many customers by its software.

I have been advised that you can get older versions of the app and I will try to find an old version to use, never had this problem using older app versions just that worked.

It would be good to hear form anyone with Play 1 and PlayBars who have had app problems and resolved them.

I spoke to my Son this morning over the phone and he has two Era 300s, a Five, a Ray and two of the old Play:1’s and those are working okay for him in their Home with the new Sonos App, but he has simply upgraded from S2 to the new Sonos App and he’s not experiencing any issues. He just thinks the App is a little slow in places, but finds everything is working okay. Not sure that that helps, but if I get to visit in the next week or so. I’ll get him to reset one of his Play:1’s to see if there are any issues with setup/registration, unless in the meantime someone else chimes in here to say they have a Play:1 etc. that they have setup and is working okay for them.

I have another Sonos Playbar and Play 1s that havent been affected by having to update via new app, they are working fine , and i am leaving those alone. Did your son reinstall or move to another netork or just updated the app without reinstalling.
Unfortunately it appears its only if you have to move or reinstall these old units, that problems appear.

I thought SonosNet had resolved all those issues (or even a factory reset with a new Sonos HH) as detailed in the link I gave earlier in my first post above, for those products that don’t use Bluetooth .LE? I’m struggling to go onto test these things here, as I think all my Sonos devices here have .BLE built-in for device setup.