Local Superstar

Sonos update on Sub failed error 30 in wireless WM: 1 configuration

16 replies
689 views

I was stumped today, iOS updated to 15.7.1, and trying a system update to 15.7 from 15.6.

I got an update error, more details showed an error 30 on the Sub, tried again, failed.

Restarted Arc and Sub, failed again, then iOS was showing status ‘updating’ with blue icon, now stuck updating. light was off on Sub, ie not flashing as does normally when updating.

Opened Sonos Desktop App, about my system, all on 15.7 apart from Sub on 15.6. I assume Network OK, as I could ping all Sonos devices with sub 5ms response, also able to access Network Matrix on Sub and Arc. App said there was an update, tried again failed.

Time to call Sonos support, so they could investigate diagnostic 😀

They suggested cause was a network issue, as is normally the case for any Sonos issue.

I wasn’t so sure, as I could ping all Sonos devices with latency <5ms, they have reserved IP addresses.

I managed to get the update installed eventually, involved restarting Arc + Sub several times, then disconnecting and reconnecting Sub to Arc via App.

I am still non the wiser what was the cause, I am curious, as this is only the second time in many updates (since 1.1?) that I have had update issue.

My environment is wireless (was SonosNet up until a couple of months back), and this is possibly the first or second software update in this configuration. Has been working flawlessly is this configuration for music listening including groups etc.

I have learnt today that the Sub uses the 2.4Ghz radio for updates, not the HT 5Ghz radio via the Arc. Looking at the Network Matrix, I also noticed my Sub is ‘root node’ for the STP network to the Arc, is this normal? I would have assumed the root node would be the Arc as this has the wireless uplink to LAN?

I think there could also be an issue with the iOS App, incorrectly reporting the status of updates, force closing the App resolves this.

Any network gurus have any thoughts on what I should investigate?

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.

Show previous replies

C

craigskiAuthor

Local Superstar

* How many devices do you have in your Sonos household? The recommendation these days, particularly for larger households, is to let everything update automatically. It takes the controller out of the equation and, I dare say, any needed retries are executed automatically. I understand that this recommendation is stronger in the case of station mode households.

I generally prefer a manual update, so I am in control, can review release notes etc before applying

The ‘workaround’ seems to be to force close the App and reapply the update a bit later

PS - I noticed the 15.8 update didn’t cause any of the older P1s to reconnect to WiFi, just newer devices seemed to restart.

Next update I will take an even closer look on network during the update.

ratty

I generally prefer a manual update, so I am in control, can review release notes etc before applying

That’s alright. Leave it on manual. When you get a prompt, decline, read the notes, switch it to auto, then reset it in the morning.

C

craigskiAuthor

Local Superstar

Leave it on manual. When you get a prompt, decline, read the notes, switch it to auto, then reset it in the morning.

A good compromise, thanks.

T

tophatdrop

Lyricist I

Just want to add what worked for me (and what didn’t) here:

Sub refusing to update with error 30. Sonos system using home 5GHz wifi.

Power cycled sub several times, same error.
Reset sub several times, same error.
Connected sub directly to router with ethernet cable and reset sub. Same error several times.
Connected sub back on wifi and reset. Same error.
Power-cycled (restarted) router: sub update worked FIRST TIME!

I hadn’t tried restarting the router previously, because every other device on our home wifi was working flawlessly and I didn’t think it sounded at all likely that the router was at fault. I had an Error30 with one (out of 4) of my Sonos Ones, and after many update attempts (and resets) the update worked perfectly immediately after I updated my Sonos app on iPhone, so I concluded that the error had been addressed in an app update somehow. But, having run out of ideas, I finally tried restarting the router, and the sub update worked immediately. I’m not sure why. Perhaps when the router’s DHCP wifi allocates new IP addresses to the Sonos devices, something in the update works differently. I don’t know. But just wanted to let others who might be stubborn like me and be think “There’s nothing wrong with my home wifi, I’m not restarting the router!” to just try it anyway.

Good luck :)

buzz

Grand Maestro

You can prevent this mayhem (duplicate IP addresses) by “reserving” IP addresses in the router. I reserve IP addresses for all regular network clients in addition to SONOS. There’s no point reserving an address for an occasional visitor’s phone.

SONOS system updates reboot all of the players and they’ll all ask for an IP address. The sudden barrage of DHCP requests can fluster the router. You can accidentally experience flawless updates 100 times in a row, then the Phantom strikes during 101 and SONOS is blamed as being broken. Community regulars all reserve IP addresses and we haven’t crossed swords with the Phantom in years.

Stanley_4

Grand Maestro

I spent many boring hours trying to find the DHCP issue way back when because I thought it better to fix the real problem than put the “static/reserved IP” band-aid on it. After many hours of work and much power-cycling of my Sonos I realized I wasn’t going to find anything.

Set the IPs years ago and all has worked since then. It is the first thing I do when I get a new Sonos as it also solves issues here with the initial setup as well as power-cycles and updates.

Sign up

Login to the community