Sonos Android App Can’t Find Speakers on VLAN? Here’s How to Fix It

If your Sonos speakers are online but the Android app shows “No products found,” and your iOS app or web player still works fine, the most likely cause is how your network handles mDNS across VLANs — combined with how the Android app performs device discovery in the background. This is not a standard Wi-Fi problem, and the usual advice to “reconnect to the same network” does not apply when your setup intentionally separates speakers from phones.

This guide covers the network-layer checks first (mDNS proxy, IGMP, firewall rules), then the UniFi-specific settings most commonly missed, and finally what to check if the issue only started after a recent Android app or speaker firmware update.

Why the Sonos Android App Shows “No Products Found” on a VLAN

Sonos discovers speakers using mDNS (multicast DNS), which broadcasts over the link-local multicast address 224.0.0.251. By design, mDNS packets do not cross VLAN or subnet boundaries — a router will not forward them without explicit help. When your Sonos speakers sit on an IoT VLAN and your Android phone sits on a Trusted or Main VLAN, the discovery packets from the app simply never reach the speakers unless your router or gateway is configured to bridge them.

Sonos also uses SSDP (Simple Service Discovery Protocol) on 239.255.255.250:1900 for player-to-player coordination. Like mDNS, SSDP is multicast and stops at the VLAN boundary.

Community reports consistently describe a pattern where the Android app loses speaker discovery after being backgrounded while the iOS app does not, suggesting a difference in how the two apps handle discovery on resume — though the specific cause has not been confirmed by Sonos.

First Checks Before Touching Router Settings

Before changing any VLAN or firewall configuration, confirm these four things. They eliminate the most common causes and help you establish a reliable baseline.

1. Confirm the speakers are actually online. Open a browser on a device connected to the IoT VLAN and try to reach a speaker’s IP address directly. If the speaker is unreachable, the problem is with the speakers themselves, not with the app.
2. Confirm your Android phone is on the correct VLAN. Go to Settings → Network & Internet → Wi-Fi, tap your network, and verify you are connected to the intended Trusted or Main VLAN, not the IoT VLAN. If you are connected to the IoT VLAN, the app should find the speakers without any cross-VLAN configuration — but you would lose the network separation you set up.
3. Check whether iOS finds the speakers. Open the Sonos app on an iPhone or iPad connected to the same VLAN as your Android phone. If iOS finds the speakers and Android does not, the underlying network configuration is likely working and the issue is specific to the Android app’s discovery behavior. If neither platform finds the speakers, the mDNS proxy or firewall rules are not working at all.
4. Turn off any VPN on the Android device. A VPN connection can intercept local discovery traffic and prevent mDNS from reaching the gateway proxy. Sonos’s official troubleshooting steps list this as a separate check.

Enable mDNS Proxy and IGMP Snooping (The Core Fix)

If the speakers are online and neither platform can find them across VLANs, two settings on your gateway are the most important place to start: the mDNS proxy and IGMP snooping.

mDNS Proxy (Gateway mDNS Proxy in UniFi): This is the setting that actually allows mDNS discovery to cross VLAN boundaries. Without it, no mDNS-based device — Sonos, AirPlay, Chromecast — can be discovered from a different VLAN, regardless of firewall rules. The mDNS proxy intercepts mDNS announcements on one VLAN and rebroadcasts them on another.

In UniFi Network, enable the Gateway mDNS Proxy under Settings → Networks. You must enable it on both the network where your phone lives (Trusted or Main) and the network where your speakers live (IoT). Enabling it on only one side is the most common mistake.

IGMP Snooping: This setting does not help mDNS cross VLANs, but it prevents multicast traffic from flooding every port on the IoT VLAN. On larger setups with many Sonos speakers or other multicast devices, disabling IGMP snooping can cause excessive traffic that degrades discovery reliability. Keep it enabled.

After enabling the mDNS proxy and IGMP snooping, restart the gateway and close and reopen the Sonos Android app. Give it 30–60 seconds to perform a discovery scan before concluding it has not worked.

UniFi-Specific Settings to Review for Sonos Discovery

If you are running UniFi, there are a few additional settings that community members with confirmed working Sonos + IoT VLAN setups consistently include. These go beyond enabling the mDNS proxy.

Firewall rules between VLANs: The mDNS proxy handles discovery, but once the app knows the speaker’s IP address, it communicates with it over unicast TCP and UDP. Without the right firewall rules, the app can find the speakers but cannot control them, or loses control intermittently.

Based on Sonos’s official documentation, the ports that need to be open from your client VLAN (phone) to your IoT VLAN (speakers) are:

• TCP ports: 1400, 1410, 1443, 1843, 3400, 3401, 3500 (Sonos control)
• UDP ports: 1900, 1901 (Sonos app control), 5353 (mDNS), 6969 (Sonos setup)

In UniFi, create firewall rules under Settings → Firewall & Security → LAN Rules to allow traffic from your client VLAN source to your IoT VLAN destination on those ports. The rule direction is client VLAN → IoT VLAN. You do not typically need to allow traffic in the reverse direction for basic control.

STP (Spanning Tree Protocol): If you have any Sonos speakers wired into your network, the Sonos community’s UniFi best practices guide recommends configuring STP on your UniFi switches to prevent network loops, since Sonos itself uses STP to determine optimal data paths. The recommended switch priorities are 4096 for the core switch, 8192 for secondary switches, and 12288 for tertiary switches.

What not to do: Some forum threads suggest disabling the mDNS proxy and instead running a third-party mDNS repeater service. On UniFi, the built-in Gateway mDNS Proxy is sufficient for most home setups and is the approach supported by the UniFi controller. Disabling the proxy and using an external repeater adds complexity without clear benefit unless you are running an unusually large or multi-gateway network.

When the Issue Follows an Android App Update

If your Sonos speakers were discoverable from your Android phone across VLANs for an extended period, and then stopped working after an app or firmware update, the network configuration itself may not be at fault.

Multiple users in the Sonos community have reported a pattern where the Android app loses speaker discovery specifically after certain updates, while the iOS app is unaffected in the same network setup. One confirmed thread from early 2026 describes a setup that had been running with Sonos devices on an IoT VLAN and an Android phone on a Trusted VLAN — with mDNS and inter-VLAN firewall rules — that broke after upgrading to Android app version 82.00.45 and speaker firmware 93.1-74010. The app would find the speakers on first launch, then show “No products found” after being backgrounded. Killing and relaunching the app temporarily restored discovery. Downgrading the Android app to the previous version (v81) resolved the issue, and a later update (v82.01.9) appeared to resolve it for some users in that thread.

A similar pattern was reported in mid-2024 when an Android app update broke discovery entirely for some users while iOS remained unaffected.

These are community-reported observations. The underlying reason for the Android-specific behavior in cross-VLAN setups has not been officially confirmed or explained by Sonos.

If you suspect an app update is the cause, check the following before downgrading:

• Confirm whether iOS finds the speakers from the same VLAN. If it does, the network layer is working.
• Check the Sonos app version currently installed on your Android device (Sonos app → Settings → About). Note the version number before making changes.
• Check the Sonos Community’s Advanced Setups section for threads mentioning your app version and VLAN behavior. The community is often the first place version-specific issues are reported.
• If a rollback is available through the Play Store’s version history or a trusted APK source, test it on a secondary device before changing your main device.
• Contact Sonos Support with your app version, speaker firmware version, and network setup details. The more specific the report, the more useful it is for identifying whether the issue is widespread.

Note that Sonos does not officially support split-VLAN configurations. Their system requirements describe a single flat network where all devices share the same subnet. This means Sonos Support may not be able to provide detailed guidance on VLAN setups, but the community forums (particularly the Advanced Setups section) contain detailed, confirmed working configurations.

How We Researched

This article is based on Sonos’s official support documentation, including the firewall port reference page, the “No products found” support article, and the official system requirements page. Network behavior described for mDNS is consistent with RFC 6762, which defines the link-local scope of multicast DNS. UniFi-specific settings and firewall rule approaches are drawn from the Sonos Community’s official tutorials section and the Advanced Setups forum. Real user reports referenced in the app update section are drawn from multiple confirmed threads in the Sonos Community, where the same iOS-works / Android-fails pattern was reported independently across different network setups and time periods. We have not conducted hands-on lab testing. Any references to specific app or firmware versions are based on community reports and are cited as such, not as confirmed Sonos engineering statements.

Summary: What to Check in Order

1. Confirm speakers are online and your phone is on the correct VLAN.
2. Disable VPN on the Android device.
3. Enable Gateway mDNS Proxy on both the client VLAN and the IoT VLAN in your router or gateway settings.
4. Confirm IGMP Snooping is enabled on your switches.
5. Add firewall rules allowing the Sonos TCP and UDP control ports from the client VLAN to the speaker IPs on the IoT VLAN.
6. If iOS works but Android still does not, check the current app version and look for community reports matching that version and your network setup.
7. If the issue started after a specific update, test with a previous app version before concluding the problem is in your network configuration.