Announcement

Collapse
No announcement yet.

Remotely reboot a SONOS device

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • paul
    replied
    Ok here's the first part - debug logs for the following:

    - 22:40:30 - changed track to Sleepy Starry Sky
    - 22;41:02 - paused
    - 22:41:23 - played
    - 22:42:24 - ran event "Play Hot Air Balloons Zanders Room" (Nothing happened)
    - 22:45:40 - pressed pause on Homeseer for zanders room (nothing happened)
    - 22;45:55 - pressed play on Homeseer for zander's room (nothing happened)
    - waited an hour, then turned off logging

    (I noticed after that my laptop may be a second out from my HS server, so these stamps might be out by a second.)

    As it turns out, kid had to go to bed, so I can't get in there to do the unplugging right now. Sorry. Fortunately for our purposes the speaker will most likely remain unavailable overnight. So tomorrow I'll make sure turn logging back on and test, do the restart HS and test, unplug speaker, plug back in and test (as per previous messages) and get you the results.....

    Here's the debug log:

    http://www.fielding.ca/sonosdebug/SonosDebug.txt.zip

    regards,

    Paul

    Leave a comment:


  • dcorsus
    replied
    Originally posted by paul View Post
    Ok, so it looks like my homeseer log actually goes back to sometime in October. Here's the whole thing:

    http://www.fielding.ca/sonosdebug/HomeSeerLog.hsd.zip

    Unfortunately I don't have timestamps for you in that log, but if you're able to discern anything weird with the Zander speaker, that'd be awesome. Gonna setup logging and testing right now as previously discussed.

    Paul
    No revelations but noted that your system is being reset at 3:30 am on some days but nothing off there. Then I see all players drop off on the 31st at 9:05pm. Interesting enough you HStouch clients seems to be coming and going around the same time frame, but looking at it some more, your clients seems to be coming and going all the time, what's up with that?
    Other than that ,nothing off......

    Leave a comment:


  • paul
    replied
    Ok, so it looks like my homeseer log actually goes back to sometime in October. Here's the whole thing:

    http://www.fielding.ca/sonosdebug/HomeSeerLog.hsd.zip

    Unfortunately I don't have timestamps for you in that log, but if you're able to discern anything weird with the Zander speaker, that'd be awesome. Gonna setup logging and testing right now as previously discussed.

    Paul

    Leave a comment:


  • dcorsus
    replied
    Originally posted by paul View Post
    Sure thing, I can do that. Will send it as soon as I can....
    Thanks so do the HS restart before trying to booting or disconnecting the Zander player. I’m now ver curious to see what you experience with:

    HS restart
    player disconnect for 1 hour
    player reboot

    Leave a comment:


  • paul
    replied
    Sure thing, I can do that. Will send it as soon as I can....

    Leave a comment:


  • dcorsus
    replied
    Originally posted by dcorsus View Post

    If you rebooted HS a few days ago and the issue is there right now, I would be very interested in the whole HS log. It should be under <HS root>\logs and is in an SQLite format but that’s ok. Could you zip that and pm me
    Moreover , after you send me that log, I would actually prefer to see a restart of HS with all the logging active and figure out why a HS restart didn’t solve it, it must show a problem with discovery

    Leave a comment:


  • dcorsus
    replied
    Originally posted by paul View Post
    Doesn't look like it, however I did reboot hs3 a couple of days ago, and I believe the issue reoccurred prior to that last reboot (and HS3 reboots don't seem to get the speaker back, just speaker reboots). But I'll definitely be aware of it moving forward, after getting it working again tonight, if the problem reoccurs I'll get a dump of the HS3 log prior to doing anything else....
    If you rebooted HS a few days ago and the issue is there right now, I would be very interested in the whole HS log. It should be under <HS root>\logs and is in an SQLite format but that’s ok. Could you zip that and pm me

    Leave a comment:


  • paul
    replied
    Doesn't look like it, however I did reboot hs3 a couple of days ago, and I believe the issue reoccurred prior to that last reboot (and HS3 reboots don't seem to get the speaker back, just speaker reboots). But I'll definitely be aware of it moving forward, after getting it working again tonight, if the problem reoccurs I'll get a dump of the HS3 log prior to doing anything else....

    Leave a comment:


  • dcorsus
    replied
    Originally posted by paul View Post
    Sounds good. I'll do the above, and if unplugging does fix it at the end, after copying out the log I'll turn regular debug on as directed and let it go.....
    Do you normally leave any debit log on for this PI? I need to look at code but it could be that players dropping out leave log entries. If you go to the HS log page and open up options, search on things like warning or error or Zander or the up address of Zander or the udn of Zander, does anything show up of interest?

    Leave a comment:


  • paul
    replied
    Sounds good. I'll do the above, and if unplugging does fix it at the end, after copying out the log I'll turn regular debug on as directed and let it go.....

    Leave a comment:


  • dcorsus
    replied
    Originally posted by paul View Post
    Sounds good, I'll make that happen. At work right now, as soon as I get home I'll set it up.

    Indeed I agree that unplugging the speaker will likely fix it, that's typically what works for me. Just annoying that it happens, since the problem will reoccur again a few days from now if I do that.

    Cool, when I get home I'll do the following. Let me know if I should adjust this list:
    - Setup debug logging
    - play, pause, play, change a track on Zander
    - play, pause, play using direct control in HS3
    - run my event that changes the playlist, repeat and volume in HS3
    - Leave debug running for an hour
    - unplug Zander
    - monitor player table until Zander shows Off-Line
    - plug back in
    - Monitor player table until Zander shows On-line
    - Re-test connectivity as above
    - shut down debug log
    - document exactly what times each step was performed

    Thanks!

    Paul
    Sounds about right.
    If unplugging Zander fixes it, what we could do is leave things as is, set regular debug on, NO super debug and upnp log level to errors only, log to disk and hope it happens soon again. What I at least would expect is some events from Zander dropping out and somehow messing up state between upnp and plug in. Would be great to find out and perhaps add some audit functions to catch and correct those. There is a chance that the latest version takes care of business but this issue seems a bit different from what I’ve seen before

    Leave a comment:


  • paul
    replied
    Sounds good, I'll make that happen. At work right now, as soon as I get home I'll set it up.

    Indeed I agree that unplugging the speaker will likely fix it, that's typically what works for me. Just annoying that it happens, since the problem will reoccur again a few days from now if I do that.

    Cool, when I get home I'll do the following. Let me know if I should adjust this list:
    - Setup debug logging
    - play, pause, play, change a track on Zander
    - play, pause, play using direct control in HS3
    - run my event that changes the playlist, repeat and volume in HS3
    - Leave debug running for an hour
    - unplug Zander
    - monitor player table until Zander shows Off-Line
    - plug back in
    - Monitor player table until Zander shows On-line
    - Re-test connectivity as above
    - shut down debug log
    - document exactly what times each step was performed

    Thanks!

    Paul

    Leave a comment:


  • dcorsus
    replied
    Originally posted by paul View Post

    Hey Dirk,

    The log is accurate, and yeah the posted table hasn't changed - all IPs are static, no changes anywhere. 192.168.15.103 is the IP of my homeseer server. I haven't restarted anything today. I'm not sure I understand what yo mean by "There are no events which explains why your events are not firing..." I have an event that listens for the specific playlist change mentioned earlier, and the event that I used to trigger the change on the speaker (that isn't successfully hitting the speaker) is what I fired.

    Both these events are pretty straightforward, I can post them if you'd like to see them, but I"m (fairly) confident that they're solid. They worked flawlessly 100% of the time for several years before this issue started with speakers occasionally stopping working from homeseer. What I can tell you is that right now the speaker in question probably won't work until I bounce the speaker (which is good from a longevity of troubleshooting perspectiive). I'm about to hit the sack, but if you like tomorrow I could do some more debugging, charting out again the failure for that speaker, leave the logs alone for an hour, then I could pull the plug on teh speaker and plug it back in, which will most likely then allow communication to the speaker again. Might make for an interesting log?

    regards,

    Paul
    Looking through the log, I find the event where you try to play a track. However, the absence of some expected log entries suggest that either the PI thinks the player is off-line or the service is not existing. The player table unfortunately shows the UPNP subsystem view where the player appear to be happy. There is an audit in the PI to detect inconsistencies but that does seem to rectify it which leaves the last possibility that we lost the service somehow, and I'm not sure how I can debunk that theory or confirm it, or how that even could have happened.

    So before we decide to upgrade and potentially wipe out all evidence, you could leave the log on for 1 hour, during that hour, say in the first few minutes, do some actions from the SONOS APP(!!) to say pause/play or change track on the Zander player, I want to check that at least events show up. At the end of the hour, we could try to reboot the Zander player and see if that makes a difference. If it doesn't make a difference, you could take the Zander player off-line for 1 hour and reconnect it, that I would think will take care of this issue. If you take the zander player off-line, you can monitor the player table and once it goes off-line, you can reconnect it. The close the log and zip it and tell me at which times you did what.

    Dirk

    Leave a comment:


  • paul
    replied
    Originally posted by dcorsus View Post

    Is the log in sync with the posted table? The log ONLY received unsolicited events from player with IP address 192.168.15.103 which doesn't even show in your table but with UDN = RINCON_000E58BB895101400 which in your table has IP address 192.168.15.166 ???? Did you restart your router or what's happening.

    Nothing from the other players. Is this a Window machine? Firewall not configured properly?
    I see from the trace that you used events as opposed to just clicking pause/stop etc on the device page. There are no events which explains why your events are not firing and perhaps there is something with the events as well.
    Hey Dirk,

    The log is accurate, and yeah the posted table hasn't changed - all IPs are static, no changes anywhere. 192.168.15.103 is the IP of my homeseer server. I haven't restarted anything today. I'm not sure I understand what yo mean by "There are no events which explains why your events are not firing..." I have an event that listens for the specific playlist change mentioned earlier, and the event that I used to trigger the change on the speaker (that isn't successfully hitting the speaker) is what I fired.

    Both these events are pretty straightforward, I can post them if you'd like to see them, but I"m (fairly) confident that they're solid. They worked flawlessly 100% of the time for several years before this issue started with speakers occasionally stopping working from homeseer. What I can tell you is that right now the speaker in question probably won't work until I bounce the speaker (which is good from a longevity of troubleshooting perspectiive). I'm about to hit the sack, but if you like tomorrow I could do some more debugging, charting out again the failure for that speaker, leave the logs alone for an hour, then I could pull the plug on teh speaker and plug it back in, which will most likely then allow communication to the speaker again. Might make for an interesting log?

    regards,

    Paul

    Leave a comment:


  • paul
    replied
    That's correct, still in this state, not upgraded yet - didn't want to muddy the waters. You're correct, the device is not paired with any other speakers. Ok, here's the View Sonos Devices:
    UPnP Viewer

    Image
    Device Friendly Name
    Alive
    IP Address
    IP Port
    Location
    DeviceType
    UDN
    192.168.15.165 - Sonos Play:1 True 192.168.15.165 1400 http://192.168.15.165:1400/xml/device_description.xml urn:schemas-upnp-org:device:ZonePlayer:1 uuid:RINCON_000E58C94D6E01400
    192.168.15.162 - Sonos Play:1 True 192.168.15.162 1400 http://192.168.15.162:1400/xml/device_description.xml urn:schemas-upnp-org:device:ZonePlayer:1 uuid:RINCON_B8E93787A7C401400
    192.168.15.164 - Sonos Play:1 True 192.168.15.164 1400 http://192.168.15.164:1400/xml/device_description.xml urn:schemas-upnp-org:device:ZonePlayer:1 uuid:RINCON_5CAAFD95C1EA01400
    192.168.15.166 - Sonos Playbar True 192.168.15.166 1400 http://192.168.15.166:1400/xml/device_description.xml urn:schemas-upnp-org:device:ZonePlayer:1 uuid:RINCON_000E58BB895101400
    192.168.15.168 - Sonos Play:1 True 192.168.15.168 1400 http://192.168.15.168:1400/xml/device_description.xml urn:schemas-upnp-org:device:ZonePlayer:1 uuid:RINCON_949F3E8D1C4A01400
    192.168.15.161 - Sonos Play:1 True 192.168.15.161 1400 http://192.168.15.161:1400/xml/device_description.xml urn:schemas-upnp-org:device:ZonePlayer:1 uuid:RINCON_000E58CF9D2C01400
    192.168.15.163 - Sonos Play:1 True 192.168.15.163 1400 http://192.168.15.163:1400/xml/device_description.xml urn:schemas-upnp-org:device:ZonePlayer:1 uuid:RINCON_B8E9375B4FB201400
    192.168.15.167 - Sonos Play:1 True 192.168.15.167 1400 http://192.168.15.167:1400/xml/device_description.xml urn:schemas-upnp-org:device:ZonePlayer:1 uuid:RINCON_949F3E1F962601400
    192.168.15.160 - Sonos Bridge True 192.168.15.160 1400 http://192.168.15.160:1400/xml/device_description.xml urn:schemas-upnp-org:device:ZonePlayer:1 uuid:RINCON_000E58EEC6E401400
    UPnP Device Viewer uuid:RINCON_949F3E1F962601400

    Alive = True
    Friendly Name = 192.168.15.167 - Sonos Play:1
    Device UDN = uuid:RINCON_949F3E1F962601400
    IP Address = 192.168.15.167
    IP Port = 1400
    Location = http://192.168.15.167:1400/xml/device_description.xml
    Device Type = urn:schemas-upnp-org:device:ZonePlayer:1
    Application URL =
    WakeUp =
    SSID =
    Header = NOTIFY * HTTP/1.1 HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age = 1800 LOCATION: http://192.168.15.167:1400/xml/device_description.xml NT: urn:schemas-upnp-org:device:ZonePlayer:1 NTS: ssdp:alive SERVER: Linux UPnP/1.0 Sonos/53.2-70100 (ZPS12) USN: uuid:RINCON_949F3E1F962601400::urn:schemas-upnp-org:device:ZonePlayer:1 X-RINCON-HOUSEHOLD: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF X-RINCON-BOOTSEQ: 76 X-RINCON-WIFIMODE: 0 X-RINCON-VARIANT: 2 HOUSEHOLD.SMARTSPEAKER.AUDIO: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF.1NohWHaQSiTHB8CfmkPP receiveep:192.168.15.167:37244
    Has Children = True
    192.168.15.167 - Sonos Play:1 Media Server
    Zander's Room - Sonos Play:1 Media Renderer
    ManufacturerName = Sonos, Inc.
    Model Number = S12

    Has Services = 8
    Service ID = urn:upnp-org:serviceId:AlarmClock
    Service Type Identifier = urn:schemas-upnp-org:service:AlarmClock:1
    Service LastTransportStatus = 0
    Service Type = urn:schemas-upnp-org:service:AlarmClock:1
    Location = http://192.168.15.167:1400/xml/device_description.xml
    NotificationEvent = NOTIFY * HTTP/1.1 HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age = 1800 LOCATION: http://192.168.15.167:1400/xml/device_description.xml NT: urn:schemas-upnp-org:service:AlarmClock:1 NTS: ssdp:alive SERVER: Linux UPnP/1.0 Sonos/53.2-70100 (ZPS12) USN: uuid:RINCON_949F3E1F962601400::urn:schemas-upnp-org:service:AlarmClock:1 X-RINCON-HOUSEHOLD: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF X-RINCON-BOOTSEQ: 76 X-RINCON-WIFIMODE: 0 X-RINCON-VARIANT: 2 HOUSEHOLD.SMARTSPEAKER.AUDIO: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF.1NohWHaQSiTHB8CfmkPP receiveep:192.168.15.167:37244
    Service URL = http://192.168.15.167:1400/xml/AlarmClock1.xml
    Service Control URL = http://192.168.15.167:1400/AlarmClock/Control
    Service Event URL = http://192.168.15.167:1400/AlarmClock/Event

    Service ID = urn:upnp-org:serviceId:MusicServices
    Service Type Identifier = urn:schemas-upnp-org:service:MusicServices:1
    Service LastTransportStatus = 0
    Service Type = urn:schemas-upnp-org:service:MusicServices:1
    Location = http://192.168.15.167:1400/xml/device_description.xml
    NotificationEvent = NOTIFY * HTTP/1.1 HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age = 1800 LOCATION: http://192.168.15.167:1400/xml/device_description.xml NT: urn:schemas-upnp-org:service:MusicServices:1 NTS: ssdp:alive SERVER: Linux UPnP/1.0 Sonos/53.2-70100 (ZPS12) USN: uuid:RINCON_949F3E1F962601400::urn:schemas-upnp-org:service:MusicServices:1 X-RINCON-HOUSEHOLD: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF X-RINCON-BOOTSEQ: 76 X-RINCON-WIFIMODE: 0 X-RINCON-VARIANT: 2 HOUSEHOLD.SMARTSPEAKER.AUDIO: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF.1NohWHaQSiTHB8CfmkPP receiveep:192.168.15.167:37244
    Service URL = http://192.168.15.167:1400/xml/MusicServices1.xml
    Service Control URL = http://192.168.15.167:1400/MusicServices/Control
    Service Event URL = http://192.168.15.167:1400/MusicServices/Event

    Service ID = urn:upnp-org:serviceIdeviceProperties
    Service Type Identifier = urn:schemas-upnp-org:serviceeviceProperties:1
    Service LastTransportStatus = 0
    Service Type = urn:schemas-upnp-org:serviceeviceProperties:1
    Location = http://192.168.15.167:1400/xml/device_description.xml
    NotificationEvent = NOTIFY * HTTP/1.1 HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age = 1800 LOCATION: http://192.168.15.167:1400/xml/device_description.xml NT: urn:schemas-upnp-org:serviceeviceProperties:1 NTS: ssdp:alive SERVER: Linux UPnP/1.0 Sonos/53.2-70100 (ZPS12) USN: uuid:RINCON_949F3E1F962601400::urn:schemas-upnp-org:serviceeviceProperties:1 X-RINCON-HOUSEHOLD: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF X-RINCON-BOOTSEQ: 76 X-RINCON-WIFIMODE: 0 X-RINCON-VARIANT: 2 HOUSEHOLD.SMARTSPEAKER.AUDIO: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF.1NohWHaQSiTHB8CfmkPP receiveep:192.168.15.167:37244
    Service URL = http://192.168.15.167:1400/xml/DeviceProperties1.xml
    Service Control URL = http://192.168.15.167:1400/DeviceProperties/Control
    Service Event URL = http://192.168.15.167:1400/DeviceProperties/Event

    Service ID = urn:upnp-org:serviceId:SystemProperties
    Service Type Identifier = urn:schemas-upnp-org:service:SystemProperties:1
    Service LastTransportStatus = 0
    Service Type = urn:schemas-upnp-org:service:SystemProperties:1
    Location = http://192.168.15.167:1400/xml/device_description.xml
    NotificationEvent = NOTIFY * HTTP/1.1 HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age = 1800 LOCATION: http://192.168.15.167:1400/xml/device_description.xml NT: urn:schemas-upnp-org:service:SystemProperties:1 NTS: ssdp:alive SERVER: Linux UPnP/1.0 Sonos/53.2-70100 (ZPS12) USN: uuid:RINCON_949F3E1F962601400::urn:schemas-upnp-org:service:SystemProperties:1 X-RINCON-HOUSEHOLD: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF X-RINCON-BOOTSEQ: 76 X-RINCON-WIFIMODE: 0 X-RINCON-VARIANT: 2 HOUSEHOLD.SMARTSPEAKER.AUDIO: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF.1NohWHaQSiTHB8CfmkPP receiveep:192.168.15.167:37244
    Service URL = http://192.168.15.167:1400/xml/SystemProperties1.xml
    Service Control URL = http://192.168.15.167:1400/SystemProperties/Control
    Service Event URL = http://192.168.15.167:1400/SystemProperties/Event

    Service ID = urn:upnp-org:serviceId:ZoneGroupTopology
    Service Type Identifier = urn:schemas-upnp-org:service:ZoneGroupTopology:1
    Service LastTransportStatus = 0
    Service Type = urn:schemas-upnp-org:service:ZoneGroupTopology:1
    Location = http://192.168.15.167:1400/xml/device_description.xml
    NotificationEvent = NOTIFY * HTTP/1.1 HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age = 1800 LOCATION: http://192.168.15.167:1400/xml/device_description.xml NT: urn:schemas-upnp-org:service:ZoneGroupTopology:1 NTS: ssdp:alive SERVER: Linux UPnP/1.0 Sonos/53.2-70100 (ZPS12) USN: uuid:RINCON_949F3E1F962601400::urn:schemas-upnp-org:service:ZoneGroupTopology:1 X-RINCON-HOUSEHOLD: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF X-RINCON-BOOTSEQ: 76 X-RINCON-WIFIMODE: 0 X-RINCON-VARIANT: 2 HOUSEHOLD.SMARTSPEAKER.AUDIO: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF.1NohWHaQSiTHB8CfmkPP receiveep:192.168.15.167:37244
    Service URL = http://192.168.15.167:1400/xml/ZoneGroupTopology1.xml
    Service Control URL = http://192.168.15.167:1400/ZoneGroupTopology/Control
    Service Event URL = http://192.168.15.167:1400/ZoneGroupTopology/Event

    Service ID = urn:upnp-org:serviceId:GroupManagement
    Service Type Identifier = urn:schemas-upnp-org:service:GroupManagement:1
    Service LastTransportStatus = 0
    Service Type = urn:schemas-upnp-org:service:GroupManagement:1
    Location = http://192.168.15.167:1400/xml/device_description.xml
    NotificationEvent = NOTIFY * HTTP/1.1 HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age = 1800 LOCATION: http://192.168.15.167:1400/xml/device_description.xml NT: urn:schemas-upnp-org:service:GroupManagement:1 NTS: ssdp:alive SERVER: Linux UPnP/1.0 Sonos/53.2-70100 (ZPS12) USN: uuid:RINCON_949F3E1F962601400::urn:schemas-upnp-org:service:GroupManagement:1 X-RINCON-HOUSEHOLD: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF X-RINCON-BOOTSEQ: 76 X-RINCON-WIFIMODE: 0 X-RINCON-VARIANT: 2 HOUSEHOLD.SMARTSPEAKER.AUDIO: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF.1NohWHaQSiTHB8CfmkPP receiveep:192.168.15.167:37244
    Service URL = http://192.168.15.167:1400/xml/GroupManagement1.xml
    Service Control URL = http://192.168.15.167:1400/GroupManagement/Control
    Service Event URL = http://192.168.15.167:1400/GroupManagement/Event

    Service ID = urn:tencent-com:serviceId:QPlay
    Service Type Identifier = urn:schemas-tencent-com:service:QPlay:1
    Service LastTransportStatus = 0
    Service Type = urn:schemas-tencent-com:service:QPlay:1
    Location = http://192.168.15.167:1400/xml/device_description.xml
    NotificationEvent = NOTIFY * HTTP/1.1 HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age = 1800 LOCATION: http://192.168.15.167:1400/xml/device_description.xml NT: urn:schemas-tencent-com:service:QPlay:1 NTS: ssdp:alive SERVER: Linux UPnP/1.0 Sonos/53.2-70100 (ZPS12) USN: uuid:RINCON_949F3E1F962601400::urn:schemas-tencent-com:service:QPlay:1 X-RINCON-HOUSEHOLD: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF X-RINCON-BOOTSEQ: 76 X-RINCON-WIFIMODE: 0 X-RINCON-VARIANT: 2 HOUSEHOLD.SMARTSPEAKER.AUDIO: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF.1NohWHaQSiTHB8CfmkPP receiveep:192.168.15.167:37244
    Service URL = http://192.168.15.167:1400/xml/QPlay1.xml
    Service Control URL = http://192.168.15.167:1400/QPlay/Control
    Service Event URL = http://192.168.15.167:1400/QPlay/Event

    Service ID = urn:smartspeaker-audio:service:SpeakerGroup:1
    Service Type Identifier = urn:smartspeaker-audio:service:SpeakerGroup:1
    Service LastTransportStatus = 0
    Service Type = urn:smartspeaker-audio:service:SpeakerGroup:1
    Location = http://192.168.15.167:1400/xml/group_description.xml
    NotificationEvent = NOTIFY * HTTP/1.1 HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age = 3600 LOCATION: http://192.168.15.167:1400/xml/group_description.xml NT: urn:smartspeaker-audio:service:SpeakerGroup:1 NTS: ssdp:alive SERVER: Linux UPnP/1.0 Sonos/53.2-70100 (ZPS12) USN: uuid:RINCON_949F3E1F962601400::urn:smartspeaker-audio:service:SpeakerGroup:1 BOOTID.UPNP.ORG: 76 CONFIGID.UPNP.ORG: 10 GROUPINFO.SMARTSPEAKER.AUDIO: gc=1; gid=RINCON_B8E93787A7C401400:467; gname="Zander's Room" WEBSOCK.SMARTSPEAKER.AUDIO: wss://192.168.15.167:1443/websocket/api HOUSEHOLD.SMARTSPEAKER.AUDIO: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF.1NohWHaQSiTHB8CfmkPP APIVER.SMARTSPEAKER.AUDIO: 1.15.1 MINAPIVER.SMARTSPEAKER.AUDIO: 1.1.0 receiveep:192.168.15.167:47083
    Service URL =
    Service Control URL =
    Service Event URL =


    UPnP Device Viewer uuid:RINCON_949F3E1F962601400_MS

    Alive = True
    Friendly Name = 192.168.15.167 - Sonos Play:1 Media Server
    Device UDN = uuid:RINCON_949F3E1F962601400_MS
    IP Address = 192.168.15.167
    IP Port = 1400
    Location = http://192.168.15.167:1400/xml/device_description.xml
    Device Type = urn:schemas-upnp-org:device:MediaServer:1
    Application URL =
    WakeUp =
    SSID =
    Header = NOTIFY * HTTP/1.1 HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age = 1800 LOCATION: http://192.168.15.167:1400/xml/device_description.xml NT: urn:schemas-upnp-org:device:MediaServer:1 NTS: ssdp:alive SERVER: Linux UPnP/1.0 Sonos/53.2-70100 (ZPS12) USN: uuid:RINCON_949F3E1F962601400_MS::urn:schemas-upnp-org:device:MediaServer:1 X-RINCON-HOUSEHOLD: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF X-RINCON-BOOTSEQ: 76 X-RINCON-WIFIMODE: 0 X-RINCON-VARIANT: 2 HOUSEHOLD.SMARTSPEAKER.AUDIO: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF.1NohWHaQSiTHB8CfmkPP receiveep:192.168.15.167:37244
    Has Children = False
    ManufacturerName = Sonos, Inc.
    Model Number = S12

    Has Services = 2
    Service ID = urn:upnp-org:serviceId:ContentDirectory
    Service Type Identifier = urn:schemas-upnp-org:service:ContentDirectory:1
    Service LastTransportStatus = 0
    Service Type = urn:schemas-upnp-org:service:ContentDirectory:1
    Location = http://192.168.15.167:1400/xml/device_description.xml
    Service URL = http://192.168.15.167:1400/xml/ContentDirectory1.xml
    Service Control URL = http://192.168.15.167:1400/MediaServ...ectory/Control
    Service Event URL = http://192.168.15.167:1400/MediaServ...irectory/Event

    Service ID = urn:upnp-org:serviceId:ConnectionManager
    Service Type Identifier = urn:schemas-upnp-org:service:ConnectionManager:1
    Service LastTransportStatus = 0
    Service Type = urn:schemas-upnp-org:service:ConnectionManager:1
    Location = http://192.168.15.167:1400/xml/device_description.xml
    Service URL = http://192.168.15.167:1400/xml/ConnectionManager1.xml
    Service Control URL = http://192.168.15.167:1400/MediaServ...anager/Control
    Service Event URL = http://192.168.15.167:1400/MediaServ...nManager/Event

    UPnP Device Viewer uuid:RINCON_949F3E1F962601400_MR

    Alive = True
    Friendly Name = Zander's Room - Sonos Play:1 Media Renderer
    Device UDN = uuid:RINCON_949F3E1F962601400_MR
    IP Address = 192.168.15.167
    IP Port = 1400
    Location = http://192.168.15.167:1400/xml/device_description.xml
    Device Type = urn:schemas-upnp-org:device:MediaRenderer:1
    Application URL =
    WakeUp =
    SSID =
    Header = NOTIFY * HTTP/1.1 HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age = 1800 LOCATION: http://192.168.15.167:1400/xml/device_description.xml NT: urn:schemas-upnp-org:device:MediaRenderer:1 NTS: ssdp:alive SERVER: Linux UPnP/1.0 Sonos/53.2-70100 (ZPS12) USN: uuid:RINCON_949F3E1F962601400_MR::urn:schemas-upnp-org:device:MediaRenderer:1 X-RINCON-HOUSEHOLD: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF X-RINCON-BOOTSEQ: 76 X-RINCON-WIFIMODE: 0 X-RINCON-VARIANT: 2 HOUSEHOLD.SMARTSPEAKER.AUDIO: Sonos_2GCppHTdSXNVM9QGJQjffnVGUF.1NohWHaQSiTHB8CfmkPP receiveep:192.168.15.167:37244
    Has Children = False
    ManufacturerName = Sonos, Inc.
    Model Number = S12

    Has Services = 6
    Service ID = urn:upnp-org:serviceId:RenderingControl
    Service Type Identifier = urn:schemas-upnp-org:service:RenderingControl:1
    Service LastTransportStatus = 0
    Service Type = urn:schemas-upnp-org:service:RenderingControl:1
    Location = http://192.168.15.167:1400/xml/device_description.xml
    Service URL = http://192.168.15.167:1400/xml/RenderingControl1.xml
    Service Control URL = http://192.168.15.167:1400/MediaRend...ontrol/Control
    Service Event URL = http://192.168.15.167:1400/MediaRend...gControl/Event

    Service ID = urn:upnp-org:serviceId:ConnectionManager
    Service Type Identifier = urn:schemas-upnp-org:service:ConnectionManager:1
    Service LastTransportStatus = 0
    Service Type = urn:schemas-upnp-org:service:ConnectionManager:1
    Location = http://192.168.15.167:1400/xml/device_description.xml
    Service URL = http://192.168.15.167:1400/xml/ConnectionManager1.xml
    Service Control URL = http://192.168.15.167:1400/MediaRend...anager/Control
    Service Event URL = http://192.168.15.167:1400/MediaRend...nManager/Event

    Service ID = urn:upnp-org:serviceId:AVTransport
    Service Type Identifier = urn:schemas-upnp-org:service:AVTransport:1
    Service LastTransportStatus = 0
    Service Type = urn:schemas-upnp-org:service:AVTransport:1
    Location = http://192.168.15.167:1400/xml/device_description.xml
    Service URL = http://192.168.15.167:1400/xml/AVTransport1.xml
    Service Control URL = http://192.168.15.167:1400/MediaRend...nsport/Control
    Service Event URL = http://192.168.15.167:1400/MediaRend...ransport/Event

    Service ID = urn:sonos-com:serviceId:Queue
    Service Type Identifier = urn:schemas-sonos-com:service:Queue:1
    Service LastTransportStatus = 0
    Service Type = urn:schemas-sonos-com:service:Queue:1
    Location = http://192.168.15.167:1400/xml/device_description.xml
    Service URL = http://192.168.15.167:1400/xml/Queue1.xml
    Service Control URL = http://192.168.15.167:1400/MediaRenderer/Queue/Control
    Service Event URL = http://192.168.15.167:1400/MediaRenderer/Queue/Event

    Service ID = urn:upnp-org:serviceId:GroupRenderingControl
    Service Type Identifier = urn:schemas-upnp-org:service:GroupRenderingControl:1
    Service LastTransportStatus = 0
    Service Type = urn:schemas-upnp-org:service:GroupRenderingControl:1
    Location = http://192.168.15.167:1400/xml/device_description.xml
    Service URL = http://192.168.15.167:1400/xml/Group...ngControl1.xml
    Service Control URL = http://192.168.15.167:1400/MediaRend...ontrol/Control
    Service Event URL = http://192.168.15.167:1400/MediaRend...gControl/Event

    Service ID = urn:upnp-org:serviceId:VirtualLineIn
    Service Type Identifier = urn:schemas-upnp-org:service:VirtualLineIn:1
    Service LastTransportStatus = 0
    Service Type = urn:schemas-upnp-org:service:VirtualLineIn:1
    Location = http://192.168.15.167:1400/xml/device_description.xml
    Service URL = http://192.168.15.167:1400/xml/VirtualLineIn1.xml
    Service Control URL = http://192.168.15.167:1400/MediaRend...LineIn/Control
    Service Event URL = http://192.168.15.167:1400/MediaRend...alLineIn/Event


    Many thanks!

    Paul

    Leave a comment:

Working...
X