Trending Lyricist I

Sonos system has been a real pain

7 replies
58 views
Translate All

Did a search and there are many, MANY, topics posted on losing their Sonos system after replacing a router. Sonos needs to realize that some people have huge systems and some of the components may not be easily accessible. Having to go around and cycle power on every component after a router change is not acceptable, especially if the new router has the same ID and password.

FWIW: every other device on my network recovered in short order. Sonos is missing the basics. I for one will never buy another one of their products.

kdowling

It’s not clear what you are asking for. This explains how to use the New Idea / Request Line:

Translate

melvimbe

I’ve replaced my router a few times, and never had to cycle power with Sonos, as long as I kept the same SSID and password.

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

Translate

Danny

J

jmattioniAuthor

Trending Lyricist I

I finally traced the problem to the new router using a different subnet. It did eventually recover with the new subnet, but I had to cycle power on every speaker.

Translate

jgatie

Sonos or not, one should always cycle power on devices and/or reconnect to the network after a router change to ensure you are using DHCP assignments from the new router. Sometimes you can get away with it, but when the subnets don’t match, you are basically dead in the water (as you experienced).

Translate

controlav

Lead Maestro

Many people who replace their router don’t follow either of the two easy paths:

Use the same SSID/password as before
Read the Support article that @melvimbe linked

Translate

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

J

jmattioniAuthor

Trending Lyricist I

Using the same SSID and password is not enough. Most new routers choose their own random subnet that most likely doesn't match what you had. In my case that's what really confused Sonos.

Even if you choose the same subnet, your devices are then using IP addresses that the router did not assign. That could result in two devices getting assigned the same IP address. It would resolve eventually but could be disruptive until it does.

The thing is that a device should be able to figure out it's on a dead subnet and then request a new IP from DHCP. My LG refrigerator figured it out without me having to unplug it.

Translate

C

craigski

Local Superstar

Using the same SSID and password is not enough. Most new routers choose their own random subnet that most likely doesn't match what you had. In my case that's what really confused Sonos.

FWIW - Last year, I pressed pause on my Sonos system that was streaming Apple Music. I replaced my router, APs, and a new subnet. Used same SSID and password. I checked all Sonos devices has reconnected and obtained a new IP on the new subnet. Pressed play, and the stream continued. No Sonos device was power cycled, they all obtained a different IP on the new subnet when they reconnected to the new Wi-Fi using same credentials, and re-established a session to the Apple Music service.

If your setup has wired device(s), a power cycle of the switch(es) / router would suffice to re-establish a network connection on the Sonos devices. Modern routers with DHCP enabled will do a mathematical hash of the MAC address of the device requesting an IP address, ie a unique IP address, unlikely to clash with another device.

Translate

Sign up

Login to the community