📲 New Sonos App & Player updates for early-March are now available! 🔊

Hi, 

Thought I'd share  my first update issue with latest app/firmware, normally the updates are seamless, however the latest update, my system lost all the speakers era300's and sub-mini , they wouldn't bond with the soundbar, tried the usual steps, without success so factory reset  them, still with the same result, my network could see them, yet refused to bond.

I even changed the network on all devices same result.

Eventually spoke to support, who were pretty good, it was found UNP was switched off in the controller app; soon as UNP was switched back on, the speakers were immediately available to the app for configuration. 

I guess with UNP set to off in my app  caused  issues; so why only now has this surfaced, and the other updates firmware, didn't mind UNP off?

Its not end of days stuff, I'm happy the system is back, just curious.

I'm not a fan of unp, I think I switched it off last November/December 2025 when I bought the system, however this was the first time having unp set to off in the app upset system updates,

​@Dg7559, What is UNP? UPNP?

I thought UPnP was so other control point apps could see the Sonos devices and play to them using UPnP/DLNA.  I use that capability a lot so that I can play music that is not indexed.  I access the two MinimServer servers.

Reporting all devices connected via ETHERNET cable no longer work after this update. Devices with WIFI working without issue. If unplugging the ETHERNET cable, device will connect with WIFI right away. This update has caused ETHERNET connected devices to stop working. System contains three devices, two on ethernet, one on wifi. Only solution at this time is to remove ethernet cables from devices. Level two support call scheduled.

 My Port on Ethernet works…. I think.  All unplugged now with storm coming in.  Will check again after storm.

 The Port WiFi was also turned OFF.

Yes,  my bad

​@Dg7559, Thanks a lot for sharing the solution.

What happens if you disable UPnP now the speakers have been reconfigured?

My understanding is UPnP is only required for legacy Sonos Windows/MacOS Apps, and also 3rd Party integration. I have HA integration, so require UPnP, but when I disable UPnP, iOS App still works fine with latest Sonos system firmware.

I switched UPNP off in the app, when I bought the system late last year, all previous the updates all went through seamlessly.

However, this March update, caused the system to lose the speakers, i could see them on the network, Sonos confirmed from their end they can see them on diagnostics.

After Sonos mentioned to turn UPNP on, instantly the speakers were presented to the system for configuration. 

I saw other instances of this condition on other forums. 

I'm just happy all is working, On router level UPnP is disabled, so I assume the private network, was affected with this update, requiring UPnP on for the controller app maybe; who knows?

 Plugged the Ethernet connected Port back in ( we had a storm ).  It shows in the app.  My system, though, has always had UPnP on.  I believe it is on by default.

Have you tried disabling UPnP again?

Hi, 

Yes it's now been disabled, as i personally have no need for it.

All speakers are fine and not affected by disabling the UPnP in the app. 

So as it has been off since I owned the system, and quite a few updates have gone in smoothly, without issue. 

This March update seemed to require UPnP to be on, some forums have reported the same issue, and toggled  UPnP back on to bond their speakers again. 

 Is there something detrimental when UPnP is ON in the Sonos app?  Why turn it OFF?  I understand why it should be OFF in the router.  Just don’t understand why folks are turning it OFF in the app.

I’ve just had another system update. My speakers are now on 94.1-75110, whereas the one rolled out on Tuesday ended 75011. 

My legacy speakers (Symfonisk and Sub gen 2) are also on a higher build number than the one listed on Tuesday - it’s now 86.6-75110, vs 75010. 

It doesn’t matter, I just wondered if this mini-update added/changed anything...

Same here. And wondering the same thing. I haven’t noticed anything different yet and haven’t found any information about the update.

​@kdowling 

Given this thread started with “This release is quiet with the usual stability and performance fixes to keep your system running smoothly”, I suspect something was missed and it remains a quiet release (rather than it adding a home page button to transfer cash into a nominated bank account).  ;)

I suspect you’re correct. But if a bank account is needed for that new home page button, I hereby nominate mine.

Today’s (I think?) ‘firmware’ / ‘System’ update isn’t reflected on the linked page. 

Anyway There was a bug with UPnP they patched it according to Sonos

UPnP SSDP messages are multicast, which in a large Wi-Fi network can be excessive. Disabling will reduced unwanted multicast traffic, however needs to be enabled for legacy Windows/MacOS Sonos Apps and 3rd party Apps that still require UPnP/SSDP. If just using just S2 App on phone/tablet and/or play.sonos.com, can be disabled.

https://support.sonos.com/en-gb/article/adjust-connection-security-settings

UPnP: This pertains to integrations that utilize the unsupported UPnP protocol. Note that turning this setting off will also prevent the Sonos app for macOS and Windows from controlling your system.

 So far no issues here so I’ll leave UPnP on.  Particularly because I do use the Windows app & SonoPhone.  Also I stream to Sonos devices using other control point apps using UPnP.  I’m guessing that would not work if UPnP was turned OFF.

Applied the second “minor” update on March 12 and it did not fix my ETHERNET issues. Level Two support blaming my Pi-Hole for blocking malware, adware, and phishing domains. One sonos domain blocked in the Pi-Hole has been whitelisted, but still no connection with ETHERNET. 

Unplug the cable, power cycle speaker, and it connects via WIFI without any issue.

Tried with UPNP OFF (it was originally set to on) and no help. L2 Support says UPNP should remain ON.

Official Sonos take on PiHole

https://en.community.sonos.com/advanced-setups-229000/sonos-pi-hole-6870549

If I see Sonos update or post-update oddities I just disable my PiHole for five minutes and try Sonos again. If Sonos works a look at the PiHole logs tells me what Sonos tweak is needed.

Yes I did try to disable pi-hole and it didn’t help.

Is there any stance on recursive DNS?

Since that is the normal operating mode of DNS it shouldn't be an issue.

Some of the DNS security options could cause problems if not working, shouldn't be just for Sonos though. The errors if any should be in the DNS logs.