search

nfarina / homebridge-sonos

Sonos plugin for homebridge: https://github.com/nfarina/homebridge
155 stars 52 forks source link

Ignoring request; Sonos device has not yet been discovered. #18

Open ghost opened 8 years ago

ghost commented 8 years ago

I get this error whenever I try to let Siri control my Sonos Playbar.

Ignoring request; Sonos device has not yet been discovered.

leoneleone commented 8 years ago

I'm having the same issue. Anyone got any ideas?

fwboettger commented 8 years ago

@rvdodewaard - do you get this message solely when you try to control the Playbar via Siri, or also when you try to control it via your homekit app?

ghost commented 8 years ago

@fwboettger both indeed

fwboettger commented 8 years ago

@rvdodewaard, @leoneleone - could you kindly share your config.json as well as access one of the sonos' devices web interface at http://:1400/status/topology (replace with an applicable IP address) and post the results within "Zone Players"?

crabbytravvy commented 8 years ago

I'm having the same issue. When I try and use siri to control it I get.

[Kitchen Speakers] Ignoring request; Sonos device has not yet been discovered.
Zone Name   Coordinator Group   Location    UUID    Version MinCompatVer    Compat  WiMode  HasSSID WiFreq  WiEna   BeEx
Living Room false   RINCON_5CAAFD80270401400:4  http://192.168.1.42:1400/xml/device_description.xml RINCON_5CAAFD80270401400    31.9-26010  29.0-00000      0   1   5180    1   0
Garage  true    RINCON_B8E937EC0F5401400:2  http://192.168.1.239:1400/xml/device_description.xml    RINCON_B8E937EC0F5401400    31.9-26010  29.0-00000      1   1   2462    1   0
Den true    RINCON_B8E937BAB10401400:5  http://192.168.1.59:1400/xml/device_description.xml RINCON_B8E937BAB10401400    31.9-26010  29.0-00000      1   1   2462    1   0
Patio   true    RINCON_B8E937BBB23401400:3  http://192.168.1.111:1400/xml/device_description.xml    RINCON_B8E937BBB23401400    31.9-26010  29.0-00000      1   1   2462    1   0
Kitchen true    RINCON_B8E93783533E01400:3  http://192.168.1.115:1400/xml/device_description.xml    RINCON_B8E93783533E01400    31.9-26010  29.0-00000      1   1   2462    1   0
Living Room true    RINCON_5CAAFD153AF601400:15 http://192.168.1.24:1400/xml/device_description.xml RINCON_5CAAFD153AF601400    31.9-26010  29.0-00000      1   1   2462    1   0
    "accessories": [
        {
        "accessory": "Sonos",
        "name": "Bedroom Speakers",
        "room": "Bedroom"
        },
        {
        "accessory": "Sonos",
        "name": "Kitchen Speakers",
        "room": "Kitchen"
        },
        {
        "accessory": "Sonos",
        "name": "Living Room Speakers",
        "room": "Living Room"
        },
        {
        "accessory": "Sonos",
        "name": "Patio Speakers",
        "room": "Patio"
        },
        {
        "accessory": "Sonos",
        "name": "Garage Speakers",
        "room": "Garage"
        }
    ],
ghost commented 8 years ago

@fwboettger

I have a Sub, which has the same name as the Playbar (Woonkamer). I guess this might cause the issues?

Zone Name Coordinator Group Location UUID Version MinCompatVer Compat WiMode HasSSID WiFreq WiEna BeEx Woonkamer false RINCON_000E589BF42001400:2 http://192.168.1.22:1400/xml/device_description.xml RINCON_000E589BF42001400 31.9-26010 29.0-00000 0 1 5240 1 0 Draagbaar true RINCON_B8E9378C5D7E01400:2 http://192.168.1.23:1400/xml/device_description.xml RINCON_B8E9378C5D7E01400 31.9-26010 29.0-00000 1 1 2412 1 0 Woonkamer true RINCON_000E58BE3AE201400:1 http://192.168.1.21:1400/xml/device_description.xml RINCON_000E58BE3AE201400 31.9-26010 29.0-00000 0 1 2437 1 0

"accessories": [
{
  "accessory": "Sonos",
  "name": "Woonkamer Speaker",
  "room": "Woonkamer"
}
fwboettger commented 8 years ago

@rvdodewaard, @crabbytravvy - could you please give the improved index.js as in Pull Request https://github.com/nfarina/homebridge-sonos/pull/15 a try. The discovery logic implemented with current version 0.0.4 hadn't been perfect (and prior to version 0.0.4 wouldn't have been able to cope with your setup), the discovery improvements as with this pull request should be able to resolve for you. Didn't find anything else possibly causing this from your config.json and topology information really....

crabbytravvy commented 8 years ago

Same issue when I try and control the speakers using siri.

fwboettger commented 8 years ago

@crabbytravvy - yes, no difference possible (if it's not working via any homekit app due to 'not yet discovered', then Siri won't work as well). Believe that the improved index.js as in Pull Request https://github.com/nfarina/homebridge-sonos/pull/15 will resolve your situation (simply download https://raw.githubusercontent.com/fwboettger/homebridge-sonos/enhancements-0.0.4/index.js and replace the current index.js with it....).

crabbytravvy commented 8 years ago

I put that file into place it did not work

On Monday, February 15, 2016, fwboettger notifications@github.com wrote:

@crabbytravvy https://github.com/crabbytravvy - yes, no difference possible (if it's not working via any homekit app due to 'not yet discovered', then Siri won't work as well). Believe that the improved index.js as in Pull Request #15 https://github.com/nfarina/homebridge-sonos/pull/15 will resolve your situation (simply download https://raw.githubusercontent.com/fwboettger/homebridge-sonos/enhancements-0.0.4/index.js and replace the current index.js with it....).

— Reply to this email directly or view it on GitHub https://github.com/nfarina/homebridge-sonos/issues/18#issuecomment-184259471 .

fwboettger commented 8 years ago

@crabbytravvy - hmmm. Does it just happen for your kitchen speakers, or any of the others as well?

crabbytravvy commented 8 years ago

yes I was trying to control the kitchen speakers

fwboettger commented 8 years ago

@crabbytravvy - how about the bedroom, garage or bedroom ones?

crabbytravvy commented 8 years ago

So I can turn on and turn off the kitchen speaker but no other devices. Before I was not able to do that. I can only turn on and off. Volume commands are not working

fwboettger commented 8 years ago

@crabbytravvy - understood. which homekit app are you using?

crabbytravvy commented 8 years ago

Home - Smart Home Automation

On Monday, February 15, 2016, fwboettger notifications@github.com wrote:

@crabbytravvy https://github.com/crabbytravvy - understood. which homekit app are you using?

— Reply to this email directly or view it on GitHub https://github.com/nfarina/homebridge-sonos/issues/18#issuecomment-184462282 .

fwboettger commented 8 years ago

@crabbytravvy - hmmm. could you maybe share/post the complete log file you have?

crabbytravvy commented 8 years ago

I haven't had a chance to look at this, I will get you the logs as soon as I can.

On Mon, Feb 15, 2016 at 8:21 PM, fwboettger notifications@github.com wrote:

@crabbytravvy https://github.com/crabbytravvy - hmmm. could you maybe share/post the complete log file you have?

— Reply to this email directly or view it on GitHub https://github.com/nfarina/homebridge-sonos/issues/18#issuecomment-184465618 .

crabbytravvy commented 8 years ago

[Den Speakers] Initializing Sonos accessory... [Kitchen Speakers] Initializing Sonos accessory... [Patio Speakers] Initializing Sonos accessory... [Garage Speakers] Initializing Sonos accessory... [Living Room Speakers] Initializing Sonos accessory... [Den Speakers] Found device at 192.168.1.24 [Kitchen Speakers] Found device at 192.168.1.24 [Den Speakers] Found device at 192.168.1.59 [Patio Speakers] Found device at 192.168.1.24 [Garage Speakers] Found device at 192.168.1.24 [Living Room Speakers] Found device at 192.168.1.24 [Kitchen Speakers] Found device at 192.168.1.59 [Patio Speakers] Found device at 192.168.1.59 [Garage Speakers] Found device at 192.168.1.59 [Living Room Speakers] Found device at 192.168.1.59 [Garage Speakers] Ignoring request; Sonos device has not yet been discovered. [Garage Speakers] Ignoring request; Sonos device has not yet been discovered. [Garage Speakers] Ignoring request; Sonos device has not yet been discovered. [Kitchen Speakers] Ignoring request; Sonos device has not yet been discovered. [Living Room Speakers] Ignoring request; Sonos device has not yet been discovered. [Den Speakers] Ignoring request; Sonos device has not yet been discovered. [Patio Speakers] Ignoring request; Sonos device has not yet been discovered. [Den Speakers] Ignoring request; Sonos device has not yet been discovered. [Living Room Speakers] Ignoring request; Sonos device has not yet been discovered. [Kitchen Speakers] Ignoring request; Sonos device has not yet been discovered. [Kitchen Speakers] Ignoring request; Sonos device has not yet been discovered. [Living Room Speakers] Ignoring request; Sonos device has not yet been discovered. [Den Speakers] Ignoring request; Sonos device has not yet been discovered. [Patio Speakers] Ignoring request; Sonos device has not yet been discovered.

crabbytravvy commented 8 years ago

It looks like the sonos.search is not finding all my devices. I have a work around but I'm sure there is a better way. This gets me passed the error above and my devices are controllable. Is there a reason the code doesn't just search for one device then use the topology.xml to register the rest of the devices?

--- index.js.0.0.4      2016-02-29 20:54:56.000000000 -0500
+++ index.js    2016-02-29 19:13:18.000000000 -0500
@@ -202,6 +202,8 @@
                                                 this.log("Found a playable coordinator device at %s in zone '%s' for accessory '%s' in accessory room '%s'", data.ip, data.CurrentZoneName, this.name, this.room);
                                                 this.device = device;
                                                 search.socket.close(); // we don't need to continue searching.
+                                        } else {
+                                                this.device = new sonos.Sonos(coordinator.ip)
                                         }
                                 }
benzman81 commented 7 years ago

I have the same issue. Sometime it find all speaker but most times the "ignoring request; Sonos device has not yet been discovered" will appear on some of my speakers.

leoneleone commented 7 years ago

My problems with Sonos search (in homebridge and within the Sonos app itself) seems to go away once I set static up addresses for my Sonos speakers. Not sure if that will solve the issue, but it has made my Sonos system much more stable in general. Worth a try 🙂

leoneleone commented 7 years ago

I meant to say: Set Static IP addresses

icepicknz commented 7 years ago

Hey guys, thanks for this tool, took me ages to get it to work mainly because i kept getting an error and that was because no playlist was assigned to the Sonos at the time.

Is there a way to specify playlists? Secondly is there any volume control from Siri? I'm using Eve and can control the volume but voice command would be good.

Lastly; due to having a speaker that has a SUB woofer paired; i can't seem to play music to it

icepicknz commented 7 years ago

Lastly if a speaker is part of a group of speakers, it doesn't seem to maintain the grouping :/