BUG REPORT: Can't setup new system on separate network with existing app install

Forum|Forum|3 years ago
September 1, 2023
13 replies
667 views

I’ve been banging my head against a brick wall trying to setup a new Sonos system in my RV using two Sonos Roams. I already have a home system (two Sonos Beams & four Sonos Ones) and have connected to a separate system at work (two Sonos Fives) so thought it would be no bother. How wrong I was!

The problem seems to be that when creating a new system when you get to the part where the speaker gets connected to the Wi-Fi network the app tells it to connect to the Wi-Fi network of the existing system, not the one you’re connected to and are trying to set it up on. This happened to me on both Android and iOS and using the same account as my home system and with a new account I setup fresh.

I finally found a way round it by using a spare device that had a fresh install of Sonos that hadn’t connected to any other Sonos system before. But that took a while as the first two device I tried were too old and the OS wasn’t supported (iOS 12 and Android 7). So after two days of trying I finally got there, but it would be good if the Sonos app was fixed to tell the new speaker to connect to the correct Wi-Fi network rather than picking up the one from a different system!

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.

Best answer by 106rallye

You can have the app forget a system and it will show up when you contact it again.

Show previous replies

controlav

Lead Maestro

The way things work presently are ‘by design’ it’s certainly not a bug

So do you work for Sonos and therefore have access to the design and the source code of the app and can say that with 100% certainty?

I did work in the Sonos codebase and can tell you it’s not a bug.

Author of the leading independent Sonos apps for Android, MacOS, iOS, Windows and Xbox.

106rallye

I can understand in daily use it’s good to have the system remember the last used household. It would make it easier for the app to connect to this system. Only when setting up a new household you would actually be hampered a bit by this choice.

Ken_Griffiths

It’s perhaps somewhat easier (although not essential) if separate mobile controller devices are used for each Sonos system. Remember that Sonos once produced/sold hardware controllers too, before the mobile device S1/S2 software which, as stated earlier, the App is merely a ‘remote’. or ‘viewer’ of the information/firmware and all settings/services etc; that are held on the players themselves.

Currently where one controller device only is used, the App needs to be reset, or freshly installed, on a compatible mobile device in order to create a brand new Sonos HH. Once any Sonos HH exists though, the Sonos App can connect to it whenever the mobile device is operating on the same network subnet.

When the App has been made aware of multiple Sonos HH’s you can also forget a connected HH in order to connect it to a different one, which perhaps may sometimes exist on the same subnet too.

In my own use-case, my main controllers are an iPad and iPhone XR, I can’t recall the last time the Sonos App on those were ever reset and I do use them both to connect to multiple Sonos HH’s, but whenever I have occasion to perhaps create a new Sonos system, then I just use a reset Sonos App on an iPhone SE (my Wife’s mobile) to do the setup/creation step. Then once the HH is in place, I connect my own controllers to the new HH, so no factory reset is required on my own mobile devices.

Finally, I go back to what I said earlier, once the necessary steps are perhaps understood, it really can be quite straightforward. I’m not personally sure that the Sonos development costs required to change the way things work at the moment would be worthwhile, to achieve what would just be, the exact same outcome.

Sign up

Login to the community