-
Notifications
You must be signed in to change notification settings - Fork 252
Could not connect to "<speaker> (AirSonos)" #80
Comments
I have exactly the same issue. Same config too... |
Same issue, though mine never resolves with a reboot. Here's the result of a --verbose:
|
Same output, but I never get any audio working. |
I have the same problem as @adamburmister, i.e. I never get any audio working
|
@celtboy and @Diode0 - can you verify the network IPs for the machines you're running airsonos on? They're reported as I'm wondering if the challenge is not being accepted because the device thinks the IP is wrong.. @jkili - this might actually be a Yosemite/AirPlay stability issue. Instead of restarting when this happens, try running |
Thanks @stephen for the follow-up Yes, the IP address in the dump is correct: pi@raspberrypi:~$ ifconfig |
@stephen also thank you for the follow-up. Just chiming in to confirm my On Sun, Jan 11, 2015 at 4:26 PM, Diode0 notifications@github.com wrote:
|
Mine didn't resolve with reboot too |
Gave your suggestion a go but it didn't work, and I actually couldn't connect at all now. The speakers are gray'ed out like they are not connected. Not sure what is going on. I did do an upgrade to the latest version of airsonos as well, as well as being on the Yosemites 10.10.2 beta as well. |
Why did you close this issue? It's still very much alive. |
Thank you, Stephen! |
Mine is showing the wrong IP .. my ip is .0.15 but the client shows .0.11 |
interesting, I have airsonos running on 10.7 (lion) and haven't seen any issues so it might be related to yosemite dropping the ball. will confirm with walk through though. also I'm running it through supervisor so its possible supervisor is restarting it unbeknownst to me. |
Hello Stephen I apt-get upgraded my raspberry pi, rebooted it and then, upgraded node to 0.10.36 and airsonos to 0.1.1. Unfortunately, I still cannot get audio working at all and thus, this issue remains valid. Thanks in advance for looking into it. Please see below updated verbose logs as well as diagnostics output: pi@raspberrypi:/tmp$ airsonos --verbose Searching for Sonos devices on network... Device {"host":"192.168.1.28","port":1400,"state":{}} (ZP120) Device {"host":"192.168.1.27","port":1400,"state":{}} (ZPS1) |
Same issue here:
|
I had same problem for whatever reason connect to sonos would fail.
Looking itno this error i thought it can be related that challenge build for another ip than expected. Disabling ipv6 ( |
Disabling ipv6 works for Yosemite OSX. |
works for me too on yosemite |
This is fixed in 0.2.2. |
airsonos works great 50% of the time (probably 100% on a fresh boot). However, I think if I have run airsonos previously and got to use it later (i.e. after sleep) it starts up normally but when I go to select the speaker it says 'Could not connect to "Living Room (AirSonos)"'. A reboot will fix.
Is there anything I can do to make it work without the reboot?
-Justin
Here is the verbose startup output:
I get no stdout when I used the command: node examples/server_stdout.js and use the "NodeTunes" speaker but I get the same message.
Yosemite 10.10.1 and latest code (from today but has been happening since I started using airsonos months ago on Mavericks and Yosemite).
The text was updated successfully, but these errors were encountered: