fwboettger

@leoneleone - you might want to take a look at pull request #39 . Could potentially be related and be a solution to this situation, would be worthwhile checking i...

@ScottGA - your config.json is wrong i believe, should rather be like below if i'm not mistaken? { "bridge": { "name": "Your Homebridge", "username": "CC:22:3D:E3:CE:31", "port": 51826, "pin": "031-45-154" },...

Give the new version (see also pull request #39 ) a try. Think this might help. A "npm update" should do the job...

Have a look at pull request #39 . I'm convinced this is the solution to this problem. Schau dir mal pull request #39 an, bin fast sicher dass das die...

Dann hast du noch die 'outdated' sonos library installiert. Du musst zuerst in der package.json den Eintrag von "^0.8.0" auf "^0.12.1" ändern (wenn es bei dir in Zeile 53 steht...

Ja das wäre das Vorgehen :-) > Am 23.10.2016 um 21:45 schrieb Nousemusic [email protected]: > > Hallo @fwboettger, > > ist es korrekt, in der package.json folgendes zu ändern: >...

@nfarina just merged the pull request. It should be available now as the updated official plugin version :-) Not familiar really with npm at all, sorry to admit cannot really...

@skibum333 - could you please 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...

@skibum333 - kindly rename please the 'room' parameter value in your config.json from "POOL" to "Pool" (needs to be an exact match, i.e. not all capital letters in config.json, to...

@skibum333 a) which version of homebridge-sonos are you using (0.0.4, or maybe already the improvement suggestions in index.js as per pull request https://github.com/nfarina/homebridge-sonos/pull/15)? b) have you tried multiple times, and...