Skip to main content
Sullydks
Renowned Enthusiast I
July 14, 2018

Yet another Upgrade nightmare

  • July 14, 2018
  • 42 replies
  • 1365 views
I now dread upgrades.
This time, like MOST SONOS UPGRADES in the last few years, After applying an upgrade I seem to have to manually reboot every single device and also reboot my wi-fi router and boost.
WHY ? What is causing this?
Network Matrix shows GREENS everywhere. Half my ZP's are ethernet linked. Hald on wi-f- + boost which likely isnt needed but...
Never used to be this way. Shoudln't be this way.
After the iphone and playbar upgrade -- all other zones were there. But choose one to play.. ....it starts.. then bombs. Then its gone from the ROOMS list. Then iPhone App cannot find Sonos. THis is 30 minutes or more after the upgrade.successful meesage. . Eventually the APp connects and now the zones are still gone.
7 zones are now down to 2 on my iPhone App. Then 3 more appear.. then they drop. Ludicrous.

Its going to take me a while but I'm now actively looking into Bluesound as an alternative. Seems to have the same capabilities. SONOS - pull your sock up.
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.

42 replies

Prodigy I
July 15, 2018
On another note, I’ve been using Sonos since 2009 and have never reserved IP addresses for any device on my network.
Only once did I face an issue with music skipping after an update, which was solved by restarting the router and all network devices.
I think that’s a pretty good track record for Sonos!
July 15, 2018
I have never reserved addresses either and have never had a problem. True of 99.99% of users as I have said. But where problems have arisen on someone's network it is a way of reducing the risk of future problems. That is all I am saying, and it remains true.
Ken_Griffiths
July 15, 2018
I have never reserved addresses either and have never had a problem. True of 99.99% of users as I have said. But where problems have arisen on someone's network it is a way of reducing the risk of future problems. That is all I am saying, and it remains true.
Yes, I completely agree with John B, that’s a very fair comment ...and if anyone is having such issues after updating their Sonos System, then it’s the first thing to try, as in my own experience of reading the community posts, for several years now, reserving the IP addresses in the router, almost always solves the problem.
Sullydks
SullydksAuthor
Renowned Enthusiast I
July 15, 2018
If someone is having problems after an upgrade, then Sonos Support should surely be made aware....
If the community is the way to do this ...then this thread has done its job.
If every user just hits the community pages, says nothing but grabs the workaround/fix they need from a great post by someone from eons ago, then we all blissfully march on using workarounds and not getting fixes... not good IMHO

The Community is FANTASTIC , no argument there , but there is a difference between WORKAROUND and FIX (assuming a fix is required/feasible). There is also often mixed/conflicted (but always well meant) messaging here on the community and you generally need to set aside an hour or more to make sure you find A thread with the most likely solutions.
..
eg... From a post a year ago. from Ratty, a very well respected member of this community if memory serves.:- ..

"But why do you actually need to explicitly reserve the IPs? The HH6 (Smart Hub) has a habit of keeping the same address for each device anyway, presumably based on hashing the MAC address. Certainly I've found that the IPs assigned to the few Sonos units that I have directly connected to the HH6 don't change."

Which applies to my scenario.
As it happens, I've spent the morning trying to work out how to reserve IP's on a BT Smarthub. I've given up. I can assign an IP per device by making it static but it seem the hub wont actually save them and apply. This appears to be a known Hub problem.
So Ratty's guidance above seems to be my best model at the moment..

I just need to remember NOT to upgrade unless I have a 2 hour window open and clear to toubleshoot afterwards. 🙂 🙂
====, Synology NAS. FLAC only.
Ken_Griffiths
July 15, 2018
It’s perhaps also worth mentioning here, that in some cases, there are some short video tutorials on YouTube for reserving device IP Addresses on a router, that users have made for the various different brands/models of router.

These tutorials may (perhaps) help others who want to reserve or fix their Sonos IP addresses in their router. A few examples I just found in a quick search, are shown below... I’ve just quickly picked a few at random here, but there are many dozens of these type of videos:

BT Home Hub 6
https://youtu.be/dMyJ6QHjyYE

Sky Hub Router
https://youtu.be/GnydEDF806s
https://youtu.be/GnydEDF806s

Netgear R7000 Router
https://youtu.be/8UhiORc5QAc

Netgear WNDR3700 Router
https://youtu.be/agbTosILwuw

D-Link Routers
https://youtu.be/_lqy2bZIQ1U

DD-WRT Firmware Router
https://youtu.be/eRhkv-hD8ZY

It maybe worth searching on YouTube for your own brand of router, even if the tutorial refers to a different model, there can often be many similarities that make it easy to then configure your own routers DHCP Reservation Table.

Hope that helps...
ratty
July 15, 2018
These days I try and stay away from the 'update broke my Sonos' posts, which are almost always due to IP conflicts. However in this case I'm not so sure since, as noted, the HH6 has a tendency to hang onto MAC-IP mappings by default.

Full disclosure. I don't ask much of my HH6, since it can sometimes struggle with a lot of wireless clients. It only hosts a small Sonos household. Most of my devices are on a secondary subnet, behind a Netgear router and with a standalone DHCP server.

I'd suggest a diagnostic is submitted and Sonos Support consulted to see if they can spot something. With the reduction in the amount of diagnostic data now accessible to the home user this seems like the best course.
ratty
July 15, 2018
@Sullydks, There was a suggestion in your first post that you might, at some stage, have attempted to use Sonos in WiFi ('Standard') mode, rather than with a wired component. If that's the case, and you've not removed the stored WiFi credentials from the system since then, I suggest you do so immediately. Leaving them in the system can lead to instability.
July 15, 2018
@sullydks. There is much I would agree with in your most recent post, although I still think you are mistaken in thinking that Sonos can do anything to prevent this. Let's agree to differ on that.

Leaving aside the question of whether it is actually likely to be IP addresses in this case, you said you could not find how to reserve them in the HH6. I have a HH6. Did you find the place for every device where you can choose 'Always use this IP address'? Are you saying this would not work? If so, in what sense?
Stanley_4
Grand Maestro
July 15, 2018
Sonos might be able to add a bit more health monitoring to SonosNet to detect and fix IP issues but the more they add the less other features they can add and the more traffic Sonos will be pushing over the network. I'd like to see it a bit more robust if it can be done without too much impact.
Sullydks
SullydksAuthor
Renowned Enthusiast I
August 22, 2018
@Sullydks, There was a suggestion in your first post that you might, at some stage, have attempted to use Sonos in WiFi ('Standard') mode, rather than with a wired component. If that's the case, and you've not removed the stored WiFi credentials from the system since then, I suggest you do so immediately. Leaving them in the system can lead to instability.

I need to research how to check this. Thx.

Having just applied the latest update. And once again reset the router multiple times to get so is working again and still have a wired ZP dropping out (not able to play yet visible) and the app now randomly failing to connect at all. Somethings up.
UPDATE---- I do now have BOOST but prior to that did try 'standard' for a while. But have checked and that's all cleared.
====, Synology NAS. FLAC only.