Sonos Play One Device Can Not Be Added


(Andy Hawks) #1

I just bought a Sonos Play One and can’t get this device added to SmartThings. I have added it to Alexa just fine, and can play it via Alexa or the Sonos app, so, I know it’s working and visible on the network and that shouldn’t be the issue. My steps for setup and recreating the problem are simply as follows:

  1. Complete setup in the Sonos app
  2. In the SmartThings App go to Marketplace > SmartThings Labs > Sonos (Labs) > Connect Now
  3. At the ‘Add a Thing’ screen it will just spin endlessly and never appear.

In the logs at https://graph-na04-useast2.api.smartthings.com/ide/logs I see the following block repeated every minute or so:

fd2dc5d3-7f0c-4417-b677-7b0b4cf97a51  9:13:34 PM: error super_connect_error Caught exception while adding device with type LAN Hue Bridge, exception : grails.validation.ValidationException: Validation Error(s) occurred during save():
- Field error in object 'physicalgraph.device.Device' on field 'deviceNetworkId': rejected value [00178879029D]; codes [physicalgraph.device.Device.deviceNetworkId.unique.error.physicalgraph.device.Device.deviceNetworkId,physicalgraph.device.Device.deviceNetworkId.unique.error.deviceNetworkId,physicalgraph.device.Device.deviceNetworkId.unique.error.java.lang.String,physicalgraph.device.Device.deviceNetworkId.unique.error,device.deviceNetworkId.unique.error.physicalgraph.device.Device.deviceNetworkId,device.deviceNetworkId.unique.error.deviceNetworkId,device.deviceNetworkId.unique.error.java.lang.String,device.deviceNetworkId.unique.error,physicalgraph.device.Device.deviceNetworkId.unique.physicalgraph.device.Device.deviceNetworkId,physicalgraph.device.Device.deviceNetworkId.unique.deviceNetworkId,physicalgraph.device.Device.deviceNetworkId.unique.java.lang.String,physicalgraph.device.Device.deviceNetworkId.unique,device.deviceNetworkId.unique.physicalgraph.device.Device.deviceNetworkId,device.deviceNetworkId.unique.deviceNetworkId,device.deviceNetworkId.unique.java.lang.String,device.deviceNetworkId.unique,unique.physicalgraph.device.Device.deviceNetworkId,unique.deviceNetworkId,unique.java.lang.String,unique]; arguments [deviceNetworkId,class physicalgraph.device.Device,00178879029D]; default message [{0} must be unique]
fd2dc5d3-7f0c-4417-b677-7b0b4cf97a51  9:13:34 PM: debug getChildDevices(false), children=0
fd2dc5d3-7f0c-4417-b677-7b0b4cf97a51  9:13:34 PM: trace in addChildDeviceHelper Hue 79029D (Hue Bridge)
fd2dc5d3-7f0c-4417-b677-7b0b4cf97a51  9:13:32 PM: debug username is 1llkZUUPLw5Cto0oI97HDaj-0s4AsTHDTrvSHgc0, value: uuid:2f402f80-da50-11e1-9b23-00178879029d={ssdpUSN=uuid:2f402f80-da50-11e1-9b23-00178879029d, installed=false, networkAddress=0A000081, ssdpNTS=null, deviceAddress=0050, mac=00178879029D, hub=16425c3b-5ad5-49b7-b694-621a6bf6d734, ssdpPath=/description.xml, ssdpTerm=urn:schemas-upnp-org:device:basic:1, stringCount=04, username=1llkZUUPLw5Cto0oI97HDaj-0s4AsTHDTrvSHgc0, verified=true, name=Hue 79029D, devicetype=04}
fd2dc5d3-7f0c-4417-b677-7b0b4cf97a51  9:13:32 PM: trace i is 1
fd2dc5d3-7f0c-4417-b677-7b0b4cf97a51  9:13:32 PM: trace ssdpTerm: urn:schemas-upnp-org:device:basic:1
fd2dc5d3-7f0c-4417-b677-7b0b4cf97a51  9:13:32 PM: trace device: uuid:2f402f80-da50-11e1-9b23-00178879029d={ssdpUSN=uuid:2f402f80-da50-11e1-9b23-00178879029d, installed=false, networkAddress=0A000081, ssdpNTS=null, deviceAddress=0050, mac=00178879029D, hub=16425c3b-5ad5-49b7-b694-621a6bf6d734, ssdpPath=/description.xml, ssdpTerm=urn:schemas-upnp-org:device:basic:1, stringCount=04, username=1llkZUUPLw5Cto0oI97HDaj-0s4AsTHDTrvSHgc0, verified=true, name=Hue 79029D, devicetype=04}
fd2dc5d3-7f0c-4417-b677-7b0b4cf97a51  9:13:32 PM: debug detecting status for 16425c3b-5ad5-49b7-b694-621a6bf6d734 : true
fd2dc5d3-7f0c-4417-b677-7b0b4cf97a51  9:13:32 PM: trace device: uuid:RINCON_949F3EFA2D8601400::urn:schemas-upnp-org:device:ZonePlayer:1={ssdpUSN=uuid:RINCON_949F3EFA2D8601400::urn:schemas-upnp-org:device:ZonePlayer:1, installed=false, networkAddress=0A66435F, ssdpNTS=null, data={port=0578, model=Sonos PLAY:1, manufacturer=Sonos, mac=949F3EFA2D86, ssdpTerm=urn:schemas-upnp-org:device:ZonePlayer:1, ip=0A66435F}, mac=949F3EFA2D86, deviceAddress=0578, hub=16425c3b-5ad5-49b7-b694-621a6bf6d734, ssdpPath=/xml/device_description.xml, ssdpTerm=urn:schemas-upnp-org:device:ZonePlayer:1, stringCount=04, verified=true, name=Master Bedroom, devicetype=04}
fd2dc5d3-7f0c-4417-b677-7b0b4cf97a51  9:13:32 PM: trace pre-name: Master Bedroom
fd2dc5d3-7f0c-4417-b677-7b0b4cf97a51  9:13:32 PM: trace ------------------------------------adding device-----------------------------------
fd2dc5d3-7f0c-4417-b677-7b0b4cf97a51  9:13:32 PM: trace addDevice evaluation: d: null, selectedDevice: uuid:RINCON_949F3EFA2D8601400::urn:schemas-upnp-org:device:ZonePlayer:1={ssdpUSN=uuid:RINCON_949F3EFA2D8601400::urn:schemas-upnp-org:device:ZonePlayer:1, installed=false, networkAddress=0A66435F, ssdpNTS=null, data={port=0578, model=Sonos PLAY:1, manufacturer=Sonos, mac=949F3EFA2D86, ssdpTerm=urn:schemas-upnp-org:device:ZonePlayer:1, ip=0A66435F}, mac=949F3EFA2D86, deviceAddress=0578, hub=16425c3b-5ad5-49b7-b694-621a6bf6d734, ssdpPath=/xml/device_description.xml, ssdpTerm=urn:schemas-upnp-org:device:ZonePlayer:1, stringCount=04, verified=true, name=Master Bedroom, devicetype=04}, dni: 949F3EFA2D86
fd2dc5d3-7f0c-4417-b677-7b0b4cf97a51  9:13:32 PM: trace in ssdpDiscover

…So it looks like the Sonos is discovered, but it never appears in the ST ‘Add a Thing’ screen as a device that can be added. I’m not sure if this has anything to do with the error that appears at the top of this log, since the error seems to be around Hue Bridge.

I thought maybe this log hinted at a name conflict? On initial setup of the Sonos device I chose the ‘Master Bedroom’ room name from the Sonos app. I don’t have any devices in SmartThings just named ‘Master Bedroom’, but this ‘pre-name’ bullshit I see in the logs may infer I had a hue or other device that was at one time also named ‘Master Bedroom’ but nothing is named that now, so I’m not sure if that’s the issue. So I did a factory reset on the Sonos and gave it the name ‘Sonos: Bedroom’, but it still looks like SmartThings might think it’s called ‘Master Bedroom’? If that’s the case I have absolutely no idea how to reset that if a factory reset on the Sonos doesn’t do the trick.

I also tried adding the thing manually at the ST console ‘My Devices’ screen, but I’m not sure what the network ID should be.

I just bought 4 of these POSs and am going to return them this week if this kind of trouble is all I have to look forward to with the others - not taking the others out of the box until I get this one fixed.

So I’m really hoping someone can help isolate the issue from the logs above.

Thx in advance!


Sonos One compatibility
(Matt Behnken) #2

I added my sonos by just searching by hitting the generic add a thing +. Do you use the sonos boost by chance? Is the speaker hard wired or wifi?


(Andy Hawks) #3

My speakers are connected via wifi. I do not use a BOOST. Do I need one for SmartThings? The weird thing is Alexa can discover the speakers just fine - SmartThings can not. I don’t believe it’s a wifi signal strength issue. Every part of my house is covered.

And if you look at the log snippet above, it looks like SmartThings ‘sees’ the Sonos from the ‘Add a thing’ screen, it just doesn’t allow me to add it as a thing for some reason? That’s what I can’t figure out.

Thanks in advance for any help or tips!


(jkp) #4

Sonos Play 1 or Sonos One?


(Andy Hawks) #5

Sonos Play 1


(Stuart) #6

I am working through a similar issue. I have 8 sonos devices in my house that I have used for years. All WiFi connected. They work great through Alexa, the sonos app, etc. When I discover them in ST app, only 4 of them show up (and they are a variety - 2 Play 3s, an old ZP-80 and a soundbar).
RV
I suspect it is a network blocking issue. The ST hub is hardwired to my Cisco RV325 router. The Cisco router has 3 Cisco Meraki mesh network wireless access points plugged in as well (1 on each level of house). I know the WiFi and router are enterprise grade gear but that also means they are pretty stringent with filters and access control rules.

While I can see all 8 sonos devices in the Meraki and Cisco Router admin screens, I still believe something is getting blocked by Cisco in the ST discover routine. If I have time this weekend, I am going to temporarily replace the router with a switch and retry the “add a thing” routine to see if that all show up.


(Matt Behnken) #7

I’ve been really lucky with adding sonos. I’ve got the 3 router panoramic wifi and all 7 sonos just showed up after I hit add a thing.


(Andy Hawks) #8

@Sg45 when you do this, it would be great to know if your logs show if ST ‘sees’ the Sonos like mine but doesn’t add them, from looking at Live Logs. to see the Logs, go to:

https://account.smartthings.com

(or click on ‘Community’ > ‘Developer Tools’ from this page)

Then login and click on ‘My locations’, click on your location, then click on ‘Live Logging’. Once it starts populating the logs, click on ‘Super LAN connect’ to limit to just seeing the device discovery.


#9

No, you do not.


(jkp) #10

https://account.smartthings.com


(Andy Hawks) #11

Sonos has finally discovered all my devices. I’ve listed the requirements for Sonos<>SmartThings connectivity that I can confirm to the first post in this thread:


(Stuart) #12

I realized I never replied to this Andy. Sorry. My live logs do not even see the other SONOS devices. Every device that appears in the log, can be added.The 4 that I can not add, do not show up in the logs.


(michael) #13

i can’t get my play 1’s to connect either. sonicwall firewall for the router and ubiquity for the ap. speakers don’t have problem otherwise. did ST discontinue support for sonos?