New Sonos integration finds no devices: "No Sonos mDNS services found yet" (C-8 Pro, 2.5.2.128)

Get Help Integrations
1

Haven’t seen this specific issue in other discussions of known issues so reporting it here. Let me start by disclosing I did have the legacy Sonos integration. The new integration would not run with that installed so I deleted the legacy integration and all speakers and rebuilt my Sonos network

Summary
The new Sonos integration can't discover my speakers. Discovery reports "No Sonos mDNS services found yet," and Live Logs show nothing at all when I run discovery, even after clicking it several times.

Hub

  • Hubitat C-8 Pro, platform 2.5.2.128
  • Wired Ethernet, reserved IP 192.168.199.124

Sonos system

  • 12 S2 devices: Boost (wired to router), Beam, Play:1s, Sub, Play:3, One, and a Move
  • Most speakers on SonosNet via the Boost; the Move is on Wi-Fi
  • All devices work normally in the Sonos app
  • All 12 have DHCP reservations on 192.168.199.x, the same subnet as the hub

What I've tried

  • Factory reset of all Sonos devices including the Boost, then rebuilt the system from scratch in the Sonos app
  • Reserved IPs for every speaker and the hub
  • Power-cycled speakers and the Boost
  • Rebooted the hub and reran discovery (multiple times)

Evidence the network is fine
I connected a Mac by Ethernet to the same LAN and used an mDNS browser. All 12 devices advertise sonos._tcp and appear in the list (for example, RINCON_…@Family Room, @Kitchen, @Boost). So, the speakers advertise correctly on the wired network, and the hub still finds none.

image
image692×432 93.9 KB

Questions

  1. Is this a known issue with the current Sonos integration?
  2. Will a fix be in the next platform update?
  3. Is there a way to add speakers manually (for example by IP) in the meantime?

Happy to provide logs (if available) or test anything that would help.

Thanks

2

It isn't, you're the first person to experience this

If they show in an mDNS browser they should be discovered

Resetting them won't fix it.

If you go to the home page on your hub is there anything listed under discovered devices?

3

This is all there is.

image
image2094×442 48.3 KB

4

This is a snippet of the device list in my router.

image
image1322×780 89.6 KB

5

Some additional info that may or may not be useful.

  • The Boost and the Hubitat hub are plugged into the same unmanaged switch, so there's no filtering device between them.
  • The hub's Connect Devices panel finds a Hue bridge and a Reolink device, so mDNS discovery works in general, just not for Sonos.
  • Sonos firmware versions in my system: some devices are on build 86.10-80260 and others on 97.1-80312 (from the Sonos app info screens). If the integration is sensitive to Sonos builds, that's useful for engineering to know.
6

This dns-sd -B _sonos._tcp local from the unmanaged switch that the Hubitat hub and the Sonos Boost are plugged into. The earlier test I was connected to the primary router.

image
image1608×578 217 KB

7

The lack of any airplay is also telling, most if not all of your Sonos players should also have airplay listings

If possible I would move your hub even if only temporarily to a different switch or try WiFi temporarily

Something's blocking mDNS at the hubs port or upstream from it

8

Thinking about this more, I had the legacy integration installed when I installed and ran the new integration. That generated errors which ultimately led me to delete the legacy integration and rebuild my Sonos infrastructure. Just now took a long shot and deleted the new integration then rebooted the hub and re-installed the new integration and ran discovery. All devices were discovered. Supposed something got hosed up with both the integrations running/colliding. Thanks for looking at it!

image
image690×932 27.5 KB

9

Most of my speakers are Play:1 models that don't individually support Airplay. They can however stream audio when grouped with an AirPlay-2 compatible speaker (Beam, Sonos One, Era 100).