Yet another Upgrade nightmare

As to the fact that you can't find any IP conflicts, that's not unusual. They don't actually 'show up' in any available report that I've ever seen on a router's DHCP report page. Those are snapshots of a moment in time, and none of the ones I've ever seen include anything like "and this IP address has been occupied by these two devices over the last hour". Instead, they just say "this IP address is currently connected to this device". No other indicator.

Someone else around here suggested another tool, which I didn't write down and investigate, which might make that kind of thing more evident to a user. I would suggest that the router's software should provide that without me figuring out some other random way....alas, I've not made any headway on my complaints to the router companies at large.

And honestly, it's a pretty small issue, which seems to be, at least in my experience, mostly exposed by Sonos, which is less tolerant of that situation than almost any other device, due to the nature of music streaming, and the fact that they don't have a ton of memory on the speakers to be caching data in advance to cover for lapses.

I'm happy you're back up and working. I'd still recommend for your long term happiness that you figure out how to assign those reserved IP addresses, and do it for all of your equipment that connects to your router, not just your Sonos. It's a "good" thing 🙂

I just skimmed over this after a couple days away, only a bit to add.

When you are looking at IPO address issues you need to not only look at your network and router states during the process but at the internal IP states of the Sonos gear. Making this even harder you don't have good access to your Sonos innards during an update/reboot process and all the Sonos gear is going to be rebooting and fetching/updating IP addresses at close but random times.

Like pretty much all the other folks I worked at this for a while trying to see if I could make headway in identifying the problem so I could submit a report to Sonos and hopefully get it queued up for fixing. What I suspect is that the Sonos gear is going down, rebooting, reestablishing the SonosNet and asking for and getting DHCP IP addresses. When the addresses Sonos is using don't match what ir in told to use things get odd.

Since I was failing, running out of time and getting frustrated I did the static/reserved IP assignment and the update problem has not happened again. In addition some of the controller oddness when coming back from an overnight sleep has gone away.

It wouldn't hurt Sonos to put up a FAQ on setting the static/reserved IP addresses for the more common gear and accepting further input to add to it from users of gear they don't have access to.