I'm new to Hubitat and have been trying all day to get my SONOS speakers to be found by the SONOS integration app. I've rebooted my speakers, reserved an IP for my hub and speakers, rebooted the hub, everything I could think of. Nothing. I wait 5, 10, 15 minutes and no devices are discovered. Is there anything I could do to fix this?
I'm migrating from ST and never had an issue discovering devices.
If you just want to work around this problem, you could try installing the devices manually:
That being said, I'm not sure why discovery isn't working for you, but you've already tried all the troubleshooting I can think of.
What platform version is on your Hubitat?
I'm on platform version 2.2.6.134. I also went into the logs and I see these keep repeating with new entries every few seconds of the identical item:
2021-04-01 05:13:07.545 pm warnUNVERIFIED PLAYERS!: [uuid:RINCON_000E58FA729401400::urn:schemas-upnp-org:device:ZonePlayer:1:[ssdpTerm:urn:schemas-upnp-org:device:ZonePlayer:1, port:578, ip:C0A85638, ssdpPath:/xml/device_description.xml, ssdpUSN:uuid:RINCON_000E58FA729401400::urn:schemas-upnp-org:device:ZonePlayer:1, mac:null], uuid:RINCON_000E588DF5DA01400::urn:schemas-upnp-org:device:ZonePlayer:1:[ssdpTerm:urn:schemas-upnp-org:device:ZonePlayer:1, port:578, ip:C0A85637, ssdpPath:/xml/device_description.xml, ssdpUSN:uuid:RINCON_000E588DF5DA01400::urn:schemas-upnp-org:device:ZonePlayer:1, mac:000E588DF5DA]]There were some changes in the Sonos integration in a recent platform release (2.2.6.133). So I'm tagging @mike.maxwell in case what you're seeing is a bug.
Edit: This appears to be a bug. I tried to rediscover my Sonos speakers on a C-5 running 2.2.6.134, and it fails with these warnings:
Had the same problem yesterday when I tried adding one via discovery, went the manual way that @mike.maxwell explains in the post linked above and that went really smooth.
Here is a screen shot of my logs if that helps...
as luck would have it… i just purchased a new sonos speaker a few days ago but had not added it yet. i was able to add it to hubitat a few minutes ago. it took a couple of minutes to be found but it added. 
.134 here
Did the hub update that rolled out last night fix this? I just tried again and discovery worked in about 5-seconds. 
Not fixed for me.
I opened a ticket with support (21222) on 3/24 and haven't heard from the support crew other than (on 3/26) "engineering is looking into it."
What platform version is on your Hubitat? I have verified, on a C5 and a C7, that platform 2.2.6.137 has the issue resolved.
C7 running 2.2.6.137. At best, I'm able to get the app to discover 2 of my 6 speaker pairs (though historically it discovered both speakers in a pair, in this instance of the discovery one is a single speaker and one is a pair which is discovered as a single device).
What I get is the same "Unverified Players" message when running the discovery:
UNVERIFIED PLAYERS!: [uuid:RINCON_7828CAD38C1201400::urn:schemas-upnp-org:device:ZonePlayer:1:[ssdpTerm:urn:schemas-upnp-org:device:ZonePlayer:1, port:578, ip:AC100521, ssdpPath:/xml/device_description.xml, ssdpUSN:uuid:RINCON_7828CAD38C1201400::urn:schemas-upnp-org:device:ZonePlayer:1, mac:7828CAD38C12], uuid:RINCON_347E5C3B19A401400::urn:schemas-upnp-org:device:ZonePlayer:1:[ssdpTerm:urn:schemas-upnp-org:device:ZonePlayer:1, port:578, ip:AC10051B, ssdpPath:/xml/device_description.xml, ssdpUSN:uuid:RINCON_347E5C3B19A401400::urn:schemas-upnp-org:device:ZonePlayer:1, mac:347E5C3B19A4], uuid:RINCON_347E5C3D1F2E01400::urn:schemas-upnp-org:device:ZonePlayer:1:[ssdpTerm:urn:schemas-upnp-org:device:ZonePlayer:1, port:578, ip:AC10051F, ssdpPath:/xml/device_description.xml, ssdpUSN:uuid:RINCON_347E5C3D1F2E01400::urn:schemas-upnp-org:device:ZonePlayer:1, mac:347E5C3D1F2E], uuid:RINCON_5CAAFDCD6C7001400::urn:schemas-upnp-org:device:ZonePlayer:1:[ssdpTerm:urn:schemas-upnp-org:device:ZonePlayer:1, port:578, ip:AC100520, ssdpPath:/xml/device_description.xml, ssdpUSN:uuid:RINCON_5CAAFDCD6C7001400::urn:schemas-upnp-org:device:ZonePlayer:1, mac:5CAAFDCD6C70], uuid:RINCON_7828CAD38C0601400::urn:schemas-upnp-org:device:ZonePlayer:1:[ssdpTerm:urn:schemas-upnp-org:device:ZonePlayer:1, port:578, ip:AC100522, ssdpPath:/xml/device_description.xml, ssdpUSN:uuid:RINCON_7828CAD38C0601400::urn:schemas-upnp-org:device:ZonePlayer:1, mac:7828CAD38C06], uuid:RINCON_347E5C3B14F601400::urn:schemas-upnp-org:device:ZonePlayer:1:[ssdpTerm:urn:schemas-upnp-org:device:ZonePlayer:1, port:578, ip:AC10051A, ssdpPath:/xml/device_description.xml, ssdpUSN:uuid:RINCON_347E5C3B14F601400::urn:schemas-upnp-org:device:ZonePlayer:1, mac:347E5C3B14F6], uuid:RINCON_542A1B6064F801400::urn:schemas-upnp-org:device:ZonePlayer:1:[ssdpTerm:urn:schemas-upnp-org:device:ZonePlayer:1, port:578, ip:AC100524, ssdpPath:/xml/device_description.xml, ssdpUSN:uuid:RINCON_542A1B6064F801400::urn:schemas-upnp-org:device:ZonePlayer:1, mac:542A1B6064F8], uuid:RINCON_347E5C3D42C201400::urn:schemas-upnp-org:device:ZonePlayer:1:[ssdpTerm:urn:schemas-upnp-org:device:ZonePlayer:1, port:578, ip:AC10051E, ssdpPath:/xml/device_description.xml, ssdpUSN:uuid:RINCON_347E5C3D42C201400::urn:schemas-upnp-org:device:ZonePlayer:1, mac:347E5C3D42C2], uuid:RINCON_48A6B81F09C401400::urn:schemas-upnp-org:device:ZonePlayer:1:[ssdpTerm:urn:schemas-upnp-org:device:ZonePlayer:1, port:578, ip:AC10051C, ssdpPath:/xml/device_description.xml, ssdpUSN:uuid:RINCON_48A6B81F09C401400::urn:schemas-upnp-org:device:ZonePlayer:1, mac:48A6B81F09C4], uuid:RINCON_542A1B6111B601400::urn:schemas-upnp-org:device:ZonePlayer:1:[ssdpTerm:urn:schemas-upnp-org:device:ZonePlayer:1, port:578, ip:AC100523, ssdpPath:/xml/device_description.xml, ssdpUSN:uuid:RINCON_542A1B6111B601400::urn:schemas-upnp-org:device:ZonePlayer:1, mac:542A1B6111B6]]
Adding my voice to the chorus- I bought my first Sonos (Symfonisk) yesterday and had quite a time. Got the same log messages at 5-second intervals as those above. Thankfully I stumbled on the workaround for adding the device manually in Devices | Add Virtual Device which did the trick.
Before finding the solution I had tried many reboots of the sonos, the hub, tried browsers Edge, Chrome, Firefox, set DHCP fixed IP assignment, removed/readded deivce in sonos, and tried direct ethernet connection to the speaker (none of those resolved it).
C-7, 2.2.6.140
I tried that, but was not actually able to control the speakers. I know there's been a platform update or two since then, but if the volume and media controls are working again with the manually added method, I'm not afraid to do it...but don't want to spend the time if the integration still isn't working correctly.
In short, are the actual controls working for you having manually added the speaker(s)? Are you getting correct metadata in the device when playing media through the speaker(s)?
On hubitat's sonos device page everything is working for me- volume controls, playing TTS, playing tracks, etc, and metadata updates appropriately even when controlling the speaker from the sonos app. When creating the device manually, all I set was the following:
Resuming streaming music after it is interrupted by a notification is a whole 'nother issue that seems like will probably never be correctly fixed without api/device updates from Sonos. I like some others have resigned myself to using it as a "TTS-only" appliance unfortunately.
unverified means that the integration is unable to connect to the discovered speaker from the Hub.
the ip of the speaker in question is shown in hex, AC 10 05 23 -> 172.16.5.35, see if you can ping it, and verify the ip is correct ect...
IP is definitely correct. They're statically assigned leases and when using Home Assistant or the Sonos Apps the speakers work 100% correctly.
Edit: Added all the speakers manually and at least on running a manual refresh they are all pulling data (save one speaker that needed power cycling)
Latest update, and now my manually added Sonos/Symfonisk speakers are not automatically updating. Manually hitting "Refresh" on the device updates them correctly, but discovery is still claiming "UNVERIFIED PLAYERS" if I try autodiscovery.
+1
No addressing/routing issues, since manually adding allows it to speak, etc.
Obviously, from the messages, it FOUND the device in some manner (it has the right IP address). So, not sure. IN any case, I'm using a 10.xxx.000.000/255.255.0.0 address space.
Download the Hubitat app
