-
Notifications
You must be signed in to change notification settings - Fork 256
Devices could be null and therefore forEach was not available resulting ... #131
Conversation
…ng in an exception
What Sonos setup would cause the device list to be null? My assumption here was that if at least one device was reporting back, then |
Hi stephen, I should have mention that I run airsonos on debian, the sonos topology: Sonos BRIDGE + Sonos Play:5. Regarding Air play devices: none.
This is what I get:
I can't guess why the first attempt is failing "Method Not Allowed" but the erroneous attempt should be handled before iterating on the devices list. |
Hi Stephen, I got this same error. When I applied fasol2002's patch it worked. Thanks. |
I've seen |
Unfortunately ignoring the error wasn't enough in my case. --- Message initial --- De : "Sam Beran" notifications@github.com I've seen devices come in null - the Reply to this email directly or view it on GitHub: |
I've got the forEach error too. When I implemented fasol2002's patch everything worked just fine. I've two Play 1 and one playbar all connected to each other with surround. |
I tried updating with fasol2002's patch. I get the below:
Its not able to find the sonos devices. Any tips? I have a full sonos system. I am running OSX yosemite 10.10.2, node v0.12.7 It is able to find the devices but devices seem to be null. Here is the output with diagnostics turned true Searching for Sonos devices on network... Device {"host":"10.0.0.15","port":1400,"state":{}} (ZPS9) |
Devices could be null and therefore forEach was not available resulting in an exception when airsonos startup