Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Sonos - Again
#1
This was resolved with the latest Sonos update as of 6/23/15.

After a reboot, my Sonos driver is no longer connecting. I went ahead and tried to reconfigure the driver, and I think I made it worse. :-x

Any ideas?

[Image: ZyBP3N5.jpg]
do the needful ...
Hue | Sonos | Harmony | Elk M1G // Netatmo / Brultech
Reply
#2
log dump below. everything else works - desktop app, ios app, and remote control.

Code:
06/18 00:17:42-mini-vm7, CQCServer, CQCDrv_jk_sonosThread7
{
    CQCKit, CQCDriver_DriverBase.cpp.3505, Status/App Status
    Driver 'jk_sonos' is trying to get its comm resource
}
06/18 00:17:51-mini-vm7, CQCServer, CQCDrv_jk_sonosThread7
{
    CIDUPnP, CIDUPnP_Device.cpp.328, Failed/Not Ready, Error: 200/0/0
    The device object has not be initialized yet
      <CQCServer> SonosZPPropS_DriverImpl.cpp - 237

}
06/18 00:17:56-mini-vm7, CQCServer, CQCDrv_jk_sonosThread7
{
    CQCKit, CQCDriver_DriverBase.cpp.3505, Status/App Status
    Driver 'jk_sonos' is trying to get its comm resource
}
06/18 00:18:05-mini-vm7, CQCServer, CQCDrv_jk_sonosThread7
{
    CIDUPnP, CIDUPnP_Device.cpp.328, Failed/Not Ready, Error: 200/0/0
    The device object has not be initialized yet
      <CQCServer> SonosZPPropS_DriverImpl.cpp - 237

}
06/18 00:18:10-mini-vm7, CQCServer, CQCDrv_jk_sonosThread7
{
    CQCKit, CQCDriver_DriverBase.cpp.3505, Status/App Status
    Driver 'jk_sonos' is trying to get its comm resource
}
do the needful ...
Hue | Sonos | Harmony | Elk M1G // Netatmo / Brultech
Reply
#3
What CQC version are you on? And are you using the V1 or V2 driver? This isn't the renderer driver, right, but the Sonos specific one? Anything showing up in the logs? There might be some upstream failure that is causing the device object not to initialize.
Dean Roddey
Explorans limites defectum
Reply
#4
You sure it's on a unique IP address?
Dean Roddey
Explorans limites defectum
Reply
#5
4.7.3. i need to up to .4, but i haven't yet. its the ZP driver, not the renderer.

what other logs would you like me to check?

yeah, its on a unique IP address, and is constantly working as evidenced by:

[Image: Xo4Q4XW.jpg]
do the needful ...
Hue | Sonos | Harmony | Elk M1G // Netatmo / Brultech
Reply
#6
I just meant anything else upstream in the logs from what you posted, that might be related.

There's nothing Sonos related, actually only one thing at all, beyond 4.7.3, so you should be fine there. I just hooked my up to give it a try.

You didn't just get a Sonos update or anything, did you?
Dean Roddey
Explorans limites defectum
Reply
#7
jkmonroe Wrote:The device object has not be initialized yet
Yeah but it can has cheezburger.


;-)


Sorry, carry on ...
Reply
#8
Yeh, I just saw that and fixed it for next time.
Dean Roddey
Explorans limites defectum
Reply
#9
Dean Roddey Wrote:I just meant anything else upstream in the logs from what you posted, that might be related.

There's nothing Sonos related, actually only one thing at all, beyond 4.7.3, so you should be fine there. I just hooked my up to give it a try.

You didn't just get a Sonos update or anything, did you?

i did, but it was days (weeks?) ago. i made a post in karens thread about the silent update. yeah, 6/6 must have been the update since thats when i posted.

it didnt seem to affect anything. *shrug*
do the needful ...
Hue | Sonos | Harmony | Elk M1G // Netatmo / Brultech
Reply
#10
Everything seems to be working fine for me. Also, Karen uses the ZP driver extensively and has been recently all in that stuff and hasn't reported any issues of the getting connected sort either. So I'm assuming it's got to be something silly slash pathological.

One thing I noticed is that yours shows up differently from mine. Yours has an IP address in it. The display should just be the actual name. Did you actually put the IP address in the name? If so, that may be something that is different and that might cause some syntactical issue with the Windows UPnP stack (which apparently the Sonos stuff itself does not use.) Of course it could be messing with our UPnP support though that's less likely since the CQC version didn't change, whereas OS updates may have caused some change.

It might be worth getting it down to just a regular text name and seeing if that makes a difference somehow. It's unlikely, but when one person's doesn't work and everyone else's does, we have to explore these types of things just to be sure.

It shouldn't be any sort of caching of out of date info I don't think. The discovery is just done by listening to broadcasts, which is what is going on when you press the button to find the available Sonos boxes. So we should be getting good info.
Dean Roddey
Explorans limites defectum
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  SONOS and Grouping gReatAutomation 6 2,026 04-16-2020, 10:49 PM
Last Post: kblagron
  Sonos media success simplextech 0 814 01-07-2020, 07:52 PM
Last Post: simplextech
  Use TTS with Sonos (not Play:5) IVB 7 4,173 01-20-2018, 10:27 PM
Last Post: potts.mike
  Another big Sonos update coming Dean Roddey 7 4,377 01-18-2018, 04:45 AM
Last Post: batwater
  Sonos Favourites Query NightLight 17 13,501 03-30-2017, 07:15 PM
Last Post: DaveB
  Playing Sonos Favourites fails with & symbols in the name NightLight 3 3,385 01-01-2017, 08:23 PM
Last Post: Dean Roddey
  sonos and podcasts jkmonroe 6 5,232 05-01-2016, 02:08 PM
Last Post: bbrendon
  Sonos Ron Haley 37 14,750 03-17-2016, 10:18 PM
Last Post: bbrendon
  How to disable the Sonos transmitters Dean Roddey 1 2,470 10-27-2014, 07:09 AM
Last Post: ControlFreak
  Linking Sonos senddrvcmd to upb link rtarver 5 3,995 08-17-2014, 09:35 PM
Last Post: bbrendon

Forum Jump:


Users browsing this thread: 1 Guest(s)