[GH-ISSUE #100] Only approachable via Spotify on computer not via phone #89

Closed
opened 2026-02-27 19:28:46 +03:00 by kerem · 13 comments
Owner

Originally created by @sashahilton00 on GitHub (Jan 29, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/100

Issue by JHoogink
Saturday Dec 23, 2017 at 08:15 GMT
Originally opened as https://github.com/plietar/librespot/issues/269


Since updating both my raspberry and I think the spotify app on my phone (Android), I can no longer approach Librespot directly from my phone. When I setup a connect session via the computer I am able to use my phone as a remote.

Any ideas? I found out that the Spotify app does the same with Sonos lately

Originally created by @sashahilton00 on GitHub (Jan 29, 2018). Original GitHub issue: https://github.com/librespot-org/librespot/issues/100 <a href="https://github.com/JHoogink"><img src="https://avatars2.githubusercontent.com/u/11311503?v=4" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [JHoogink](https://github.com/JHoogink)** _Saturday Dec 23, 2017 at 08:15 GMT_ _Originally opened as https://github.com/plietar/librespot/issues/269_ ---- Since updating both my raspberry and I think the spotify app on my phone (Android), I can no longer approach Librespot directly from my phone. When I setup a connect session via the computer I am able to use my phone as a remote. Any ideas? I found out that the Spotify app does the same with Sonos lately
kerem 2026-02-27 19:28:46 +03:00
Author
Owner

@sashahilton00 commented on GitHub (Jan 29, 2018):

Comment by maxx
Thursday Dec 28, 2017 at 18:44 GMT


If this is occurring with Sonos as well, wouldn't that indicate it's a Spotify issue? It sounds like they've broken casting on android completely. Did you end up with any solution to this? I was considering switching back to Android again and this would be sad if this is the case.

<!-- gh-comment-id:361278372 --> @sashahilton00 commented on GitHub (Jan 29, 2018): <a href="https://github.com/maxx"><img src="https://avatars3.githubusercontent.com/u/2896?v=4" align="left" width="48" height="48" hspace="10"></img></a> **Comment by [maxx](https://github.com/maxx)** _Thursday Dec 28, 2017 at 18:44 GMT_ ---- If this is occurring with Sonos as well, wouldn't that indicate it's a Spotify issue? It sounds like they've broken casting on android completely. Did you end up with any solution to this? I was considering switching back to Android again and this would be sad if this is the case.
Author
Owner

@sashahilton00 commented on GitHub (Jan 29, 2018):

Comment by maxx
Thursday Dec 28, 2017 at 19:18 GMT


I suspect this is your issue:

https://community.spotify.com/t5/Other-Partners-Web-Player-etc/Sonos-Bug-Spotify-Connect-is-broken/td-p/3608434
https://community.spotify.com/t5/Android/Spotify-app-won-t-connect-to-Sonos/td-p/3564456

Downgrading the android app should solve your problem. That's a pretty bad bug!

<!-- gh-comment-id:361278404 --> @sashahilton00 commented on GitHub (Jan 29, 2018): <a href="https://github.com/maxx"><img src="https://avatars3.githubusercontent.com/u/2896?v=4" align="left" width="48" height="48" hspace="10"></img></a> **Comment by [maxx](https://github.com/maxx)** _Thursday Dec 28, 2017 at 19:18 GMT_ ---- I suspect this is your issue: https://community.spotify.com/t5/Other-Partners-Web-Player-etc/Sonos-Bug-Spotify-Connect-is-broken/td-p/3608434 https://community.spotify.com/t5/Android/Spotify-app-won-t-connect-to-Sonos/td-p/3564456 Downgrading the android app should solve your problem. That's a pretty bad bug!
Author
Owner

@ComlOnline commented on GitHub (Jan 29, 2018):

As this appears to be a Spotify bug that has since been fixed I'm going to close this issue.

<!-- gh-comment-id:361317822 --> @ComlOnline commented on GitHub (Jan 29, 2018): As this appears to be a Spotify bug that has since been fixed I'm going to close this issue.
Author
Owner

@Jergol commented on GitHub (Feb 8, 2018):

Apparently i have this issue as well. i got librespot running on a pi3 and can not find the device via Android. So this Android-Issue is still a problem. I don't know about the Sonos.

<!-- gh-comment-id:364230261 --> @Jergol commented on GitHub (Feb 8, 2018): Apparently i have this issue as well. i got librespot running on a pi3 and can not find the device via Android. So this Android-Issue is still a problem. I don't know about the Sonos.
Author
Owner

@sashahilton00 commented on GitHub (Feb 9, 2018):

Please test with a Sonos and librespot under the same network conditions. There has been another report of trouble connecting, but at this point it's difficult to say whether this is a librespot/Spotify bug, or down to network configuration.

<!-- gh-comment-id:364310270 --> @sashahilton00 commented on GitHub (Feb 9, 2018): Please test with a Sonos and librespot under the same network conditions. There has been another report of trouble connecting, but at this point it's difficult to say whether this is a librespot/Spotify bug, or down to network configuration.
Author
Owner

@Jergol commented on GitHub (Feb 9, 2018):

I do not own a Sonos. But i would like to get the pi3/librespot working again for my android. For the PC in the same network it's not a problem to connect at all, and i can start the playback @ librespot via PC and even see and controll forward n stuff via android afterwards. But when it comes to find the device and initiate it from android it's not even possible to find the librespot.

If there are any infos you need or settings i should try, just give me a hint and i give it a try.

Ty in advance.

<!-- gh-comment-id:364378908 --> @Jergol commented on GitHub (Feb 9, 2018): I do not own a Sonos. But i would like to get the pi3/librespot working again for my android. For the PC in the same network it's not a problem to connect at all, and i can start the playback @ librespot via PC and even see and controll forward n stuff via android afterwards. But when it comes to find the device and initiate it from android it's not even possible to find the librespot. If there are any infos you need or settings i should try, just give me a hint and i give it a try. Ty in advance.
Author
Owner

@sashahilton00 commented on GitHub (Feb 12, 2018):

@Jergol can you confirm whether you see the error message(s) in this issue at all in the console of your librespot device? Also, is your network IPv6 enabled?

<!-- gh-comment-id:364805739 --> @sashahilton00 commented on GitHub (Feb 12, 2018): @Jergol can you confirm whether you see the error message(s) in [this](https://github.com/librespot-org/librespot/issues/67) issue at all in the console of your librespot device? Also, is your network IPv6 enabled?
Author
Owner

@Jergol commented on GitHub (Feb 12, 2018):

Hello! I'd like to help but i am a very basic/rookie user and i actually do
not know how to view error-msgs. If you can tell me how i will take a look
at it.

2018-02-12 1:30 GMT+01:00 Sasha Hilton notifications@github.com:

@Jergol https://github.com/jergol can you confirm whether you see the
error message(s) in this issue at all in the console of your librespot
device? #67 https://github.com/librespot-org/librespot/issues/67


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/librespot-org/librespot/issues/100#issuecomment-364805739,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AimKE3Ud2jt-FcTmrfCWQjBxQWGnDho9ks5tT4Y6gaJpZM4Rww8n
.

<!-- gh-comment-id:364806415 --> @Jergol commented on GitHub (Feb 12, 2018): Hello! I'd like to help but i am a very basic/rookie user and i actually do not know how to view error-msgs. If you can tell me how i will take a look at it. 2018-02-12 1:30 GMT+01:00 Sasha Hilton <notifications@github.com>: > @Jergol <https://github.com/jergol> can you confirm whether you see the > error message(s) in this issue at all in the console of your librespot > device? #67 <https://github.com/librespot-org/librespot/issues/67> > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/librespot-org/librespot/issues/100#issuecomment-364805739>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AimKE3Ud2jt-FcTmrfCWQjBxQWGnDho9ks5tT4Y6gaJpZM4Rww8n> > . >
Author
Owner

@sashahilton00 commented on GitHub (Feb 12, 2018):

When you start librespot, there's a bunch of text in the console, the error which you're looking for looks something like this:

WARN:mdns: Failed to register IPv6 receiver: Error { repr: Os { code: 19, message: "No such device" } }

It will appear within the first 10 lines if it appears at all.

<!-- gh-comment-id:364806621 --> @sashahilton00 commented on GitHub (Feb 12, 2018): When you start librespot, there's a bunch of text in the console, the error which you're looking for looks something like this: ``` WARN:mdns: Failed to register IPv6 receiver: Error { repr: Os { code: 19, message: "No such device" } } ``` It will appear within the first 10 lines if it appears at all.
Author
Owner

@Jergol commented on GitHub (Feb 12, 2018):

i will check it in a minute, i am running a Raspberry Pi 3 with Libreelec
on it, if that matters. Checking now,

2018-02-12 1:42 GMT+01:00 Sasha Hilton notifications@github.com:

When you start librespot, there's a bunch of text in the console, the
error which you're looking for looks something like this:

WARN:mdns: Failed to register IPv6 receiver: Error { repr: Os { code: 19, message: "No such device" } }

It will appear within the first 10 lines if it appears at all.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/librespot-org/librespot/issues/100#issuecomment-364806621,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AimKE3IxgXkkX2FnBp2pOW3_-aYf0Iryks5tT4kLgaJpZM4Rww8n
.

<!-- gh-comment-id:364806878 --> @Jergol commented on GitHub (Feb 12, 2018): i will check it in a minute, i am running a Raspberry Pi 3 with Libreelec on it, if that matters. Checking now, 2018-02-12 1:42 GMT+01:00 Sasha Hilton <notifications@github.com>: > When you start librespot, there's a bunch of text in the console, the > error which you're looking for looks something like this: > > WARN:mdns: Failed to register IPv6 receiver: Error { repr: Os { code: 19, message: "No such device" } } > > It will appear within the first 10 lines if it appears at all. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/librespot-org/librespot/issues/100#issuecomment-364806621>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AimKE3IxgXkkX2FnBp2pOW3_-aYf0Iryks5tT4kLgaJpZM4Rww8n> > . >
Author
Owner

@Jergol commented on GitHub (Feb 12, 2018):

Since i do not directly start Librespot via app/addon on Libreelec
(running, managing in background) i can not rly see the msg. I did check
for updates, did deactivate and reactivate, even restartet the whole system
but i can not see any msgs, i also tried to see stuff in debugmode but i
can not find anything fitting to you description. Then again, i am not
experienced in this kinda stuff. Sry that i can not help you there atm.

2018-02-12 1:46 GMT+01:00

i will check it in a minute, i am running a Raspberry Pi 3 with Libreelec
on it, if that matters. Checking now,

2018-02-12 1:42 GMT+01:00 Sasha Hilton notifications@github.com:

When you start librespot, there's a bunch of text in the console, the
error which you're looking for looks something like this:

WARN:mdns: Failed to register IPv6 receiver: Error { repr: Os { code: 19, message: "No such device" } }

It will appear within the first 10 lines if it appears at all.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/librespot-org/librespot/issues/100#issuecomment-364806621,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AimKE3IxgXkkX2FnBp2pOW3_-aYf0Iryks5tT4kLgaJpZM4Rww8n
.

<!-- gh-comment-id:364809194 --> @Jergol commented on GitHub (Feb 12, 2018): Since i do not directly start Librespot via app/addon on Libreelec (running, managing in background) i can not rly see the msg. I did check for updates, did deactivate and reactivate, even restartet the whole system but i can not see any msgs, i also tried to see stuff in debugmode but i can not find anything fitting to you description. Then again, i am not experienced in this kinda stuff. Sry that i can not help you there atm. 2018-02-12 1:46 GMT+01:00 > i will check it in a minute, i am running a Raspberry Pi 3 with Libreelec > on it, if that matters. Checking now, > > 2018-02-12 1:42 GMT+01:00 Sasha Hilton <notifications@github.com>: > >> When you start librespot, there's a bunch of text in the console, the >> error which you're looking for looks something like this: >> >> WARN:mdns: Failed to register IPv6 receiver: Error { repr: Os { code: 19, message: "No such device" } } >> >> It will appear within the first 10 lines if it appears at all. >> >> — >> You are receiving this because you were mentioned. >> Reply to this email directly, view it on GitHub >> <https://github.com/librespot-org/librespot/issues/100#issuecomment-364806621>, >> or mute the thread >> <https://github.com/notifications/unsubscribe-auth/AimKE3IxgXkkX2FnBp2pOW3_-aYf0Iryks5tT4kLgaJpZM4Rww8n> >> . >> > >
Author
Owner

@sashahilton00 commented on GitHub (Feb 12, 2018):

No problem. I'm going to close this for now, as I think it is probably issue #67 you're experiencing, indirectly.

<!-- gh-comment-id:364809315 --> @sashahilton00 commented on GitHub (Feb 12, 2018): No problem. I'm going to close this for now, as I think it is probably issue #67 you're experiencing, indirectly.
Author
Owner

@markubiak commented on GitHub (Mar 13, 2019):

I had this issue, and the solution in my case was unrelated to librespot. It turns out that Spotify has a bug in their Android app that unintentionally interferes with ad blockers, as discussed in this AdAway issue.

The solution is a fork of AdAway that works around the issue, found here

<!-- gh-comment-id:472583529 --> @markubiak commented on GitHub (Mar 13, 2019): I had this issue, and the solution in my case was unrelated to librespot. It turns out that Spotify has a bug in their Android app that unintentionally interferes with ad blockers, as discussed in [this AdAway issue](https://github.com/AdAway/AdAway/issues/1009). The solution is a fork of AdAway that works around the issue, found [here](https://github.com/c64bob/AdAway/releases/tag/v4.1.0)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/librespot#89
No description provided.