Spotify Connect

Discuss, contribute and orient Volumio development!

Ads helps Volumio remain Free and Open Source. Please consider donating to help us continue to serve you.

Spotify Connect

Postby ashthespy » Thu Apr 11 2019 13:57

yungyaw wrote:I saw this when trying to connect to Volumio under Spotify Device List.
Code: Select all
[Vollibrespot] mdns::fsm: received question: IN _apple-pairable._tcp.local
[Vollibrespot] librespot_connect::discovery: Post "/" {}
[Vollibrespot] : Connecting to AP "gae2-accesspoint-b-8zx2.ap.spotify.com:4070"
[Vollibrespot] mdns::fsm: received question: IN _companion-link._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _homekit._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _airplay._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _sleep-proxy._udp.local
[Vollibrespot] mdns::fsm: received question: IN 40:4d:7f:6a:80:90@fe80::424d:7fff:fe6a:8090._apple-mobdev2._tcp.local
[Vollibrespot] mdns::fsm: received question: IN 40:4d:7f:6a:80:90@fe80::424d:7fff:fe6a:8090._apple-mobdev2._tcp.local
[Vollibrespot] mdns::fsm: received question: IN 40:4d:7f:6a:80:90@fe80::424d:7fff:fe6a:8090._apple-mobdev2._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _companion-link._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _homekit._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _airplay._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _sleep-proxy._udp.local
[Vollibrespot] mdns::fsm: received question: IN _companion-link._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _homekit._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _airplay._tcp.local
[Vollibrespot] mdns::fsm: received question: IN 04255CB411F0@Volumio._raop._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _sleep-proxy._udp.local


Can you tell what is my volspotconnect2 problem from the above?

FYI, I tried all Mixer Type settings (Hardware, Software, None). All same result.


logs don't show any connection attempts - can you debug further by:
1. Stop the plugin
2. Running the command to capture logs
Code: Select all
sudo journalctl -f -o cat -u volspotconnect2.service

3. Start the plugin
4. Try connecting
User avatar
ashthespy
Objectivist
Objectivist
 
Posts: 288
Joined: Fri Jul 22 2016 08:16

Ads helps Volumio remain Free and Open Source. Please consider donating to help us continue to serve you.


Spotify Connect

Postby yungyaw » Thu Apr 11 2019 15:27

I did as you told me. Here's the log:

Code: Select all
Stopping Volspotconnect2 Daemon...
Stopped Volspotconnect2 Daemon.
Starting Volspotconnect2 Daemon...
Started Volspotconnect2 Daemon.
vollibrespot v0.1.4 d207974 2019-03-26 (librespot 57a6586 2019-03-26) -- Built On 2019-03-26
[Vollibrespot] librespot_connect::discovery: Zeroconf server listening on 0.0.0.0:39967
[Vollibrespot] : Failed to register IPv6 receiver: Os { code: 19, kind: Other, message: "No such device" }
[Vollibrespot] librespot_connect::discovery: Post "/" {}
[Vollibrespot] : Connecting to AP "gae2-accesspoint-b-dmwm.ap.spotify.com:4070"
[Vollibrespot] librespot_connect::discovery: Post "/" {}
[Vollibrespot] : Connecting to AP "gae2-accesspoint-b-m3zs.ap.spotify.com:4070"
[Vollibrespot] mdns::fsm: received question: IN _companion-link._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _homekit._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _airplay._tcp.local
[Vollibrespot] mdns::fsm: received question: IN 04255CB411F0@Volumio._raop._tcp.local
[Vollibrespot] mdns::fsm: received question: IN YungYaw’s MacBook Pro._companion-link._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _sleep-proxy._udp.local
[Vollibrespot] mdns::fsm: received question: IN 40:4d:7f:6a:80:90@fe80::424d:7fff:fe6a:8090._apple-mobdev2._tcp.local
[Vollibrespot] mdns::fsm: received question: IN 40:4d:7f:6a:80:90@fe80::424d:7fff:fe6a:8090._apple-mobdev2._tcp.local
[Vollibrespot] mdns::fsm: received question: IN 40:4d:7f:6a:80:90@fe80::424d:7fff:fe6a:8090._apple-mobdev2._tcp.local
[Vollibrespot] mdns::fsm: received question: IN YY-2.local
[Vollibrespot] mdns::fsm: received question: IN YY-2.local
[Vollibrespot] mdns::fsm: received question: IN _companion-link._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _homekit._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _airplay._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _sleep-proxy._udp.local
[Vollibrespot] mdns::fsm: received question: IN YY-2.local
[Vollibrespot] mdns::fsm: received question: IN _companion-link._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _homekit._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _airplay._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _sleep-proxy._udp.local
[Vollibrespot] mdns::fsm: received question: IN _spotify-connect._tcp.local
[Vollibrespot] librespot_connect::discovery: Post "/" {}
[Vollibrespot] : Connecting to AP "gae2-accesspoint-b-qcdb.ap.spotify.com:4070"


ashthespy wrote:
yungyaw wrote:I saw this when trying to connect to Volumio under Spotify Device List.
Code: Select all
[Vollibrespot] mdns::fsm: received question: IN _apple-pairable._tcp.local
[Vollibrespot] librespot_connect::discovery: Post "/" {}
[Vollibrespot] : Connecting to AP "gae2-accesspoint-b-8zx2.ap.spotify.com:4070"
[Vollibrespot] mdns::fsm: received question: IN _companion-link._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _homekit._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _airplay._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _sleep-proxy._udp.local
[Vollibrespot] mdns::fsm: received question: IN 40:4d:7f:6a:80:90@fe80::424d:7fff:fe6a:8090._apple-mobdev2._tcp.local
[Vollibrespot] mdns::fsm: received question: IN 40:4d:7f:6a:80:90@fe80::424d:7fff:fe6a:8090._apple-mobdev2._tcp.local
[Vollibrespot] mdns::fsm: received question: IN 40:4d:7f:6a:80:90@fe80::424d:7fff:fe6a:8090._apple-mobdev2._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _companion-link._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _homekit._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _airplay._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _sleep-proxy._udp.local
[Vollibrespot] mdns::fsm: received question: IN _companion-link._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _homekit._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _airplay._tcp.local
[Vollibrespot] mdns::fsm: received question: IN 04255CB411F0@Volumio._raop._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _sleep-proxy._udp.local


Can you tell what is my volspotconnect2 problem from the above?

FYI, I tried all Mixer Type settings (Hardware, Software, None). All same result.


logs don't show any connection attempts - can you debug further by:
1. Stop the plugin
2. Running the command to capture logs
Code: Select all
sudo journalctl -f -o cat -u volspotconnect2.service

3. Start the plugin
4. Try connecting
Random avatar
yungyaw
Sunday DIYer
Sunday DIYer
 
Posts: 16
Joined: Wed Jul 22 2015 12:00


Spotify Connect

Postby ashthespy » Thu Apr 11 2019 17:45

yungyaw wrote:I did as you told me. Here's the log:

Code: Select all
Stopping Volspotconnect2 Daemon...
Stopped Volspotconnect2 Daemon.
Starting Volspotconnect2 Daemon...
Started Volspotconnect2 Daemon.
vollibrespot v0.1.4 d207974 2019-03-26 (librespot 57a6586 2019-03-26) -- Built On 2019-03-26
[Vollibrespot] librespot_connect::discovery: Zeroconf server listening on 0.0.0.0:39967
[Vollibrespot] : Failed to register IPv6 receiver: Os { code: 19, kind: Other, message: "No such device" }
[Vollibrespot] librespot_connect::discovery: Post "/" {}
[Vollibrespot] : Connecting to AP "gae2-accesspoint-b-dmwm.ap.spotify.com:4070"
[Vollibrespot] librespot_connect::discovery: Post "/" {}
[Vollibrespot] : Connecting to AP "gae2-accesspoint-b-m3zs.ap.spotify.com:4070"
[Vollibrespot] mdns::fsm: received question: IN _companion-link._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _homekit._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _airplay._tcp.local
[Vollibrespot] mdns::fsm: received question: IN 04255CB411F0@Volumio._raop._tcp.local
[Vollibrespot] mdns::fsm: received question: IN YungYaw’s MacBook Pro._companion-link._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _sleep-proxy._udp.local
[Vollibrespot] mdns::fsm: received question: IN 40:4d:7f:6a:80:90@fe80::424d:7fff:fe6a:8090._apple-mobdev2._tcp.local
[Vollibrespot] mdns::fsm: received question: IN 40:4d:7f:6a:80:90@fe80::424d:7fff:fe6a:8090._apple-mobdev2._tcp.local
[Vollibrespot] mdns::fsm: received question: IN 40:4d:7f:6a:80:90@fe80::424d:7fff:fe6a:8090._apple-mobdev2._tcp.local
[Vollibrespot] mdns::fsm: received question: IN YY-2.local
[Vollibrespot] mdns::fsm: received question: IN YY-2.local
[Vollibrespot] mdns::fsm: received question: IN _companion-link._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _homekit._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _airplay._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _sleep-proxy._udp.local
[Vollibrespot] mdns::fsm: received question: IN YY-2.local
[Vollibrespot] mdns::fsm: received question: IN _companion-link._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _homekit._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _airplay._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _sleep-proxy._udp.local
[Vollibrespot] mdns::fsm: received question: IN _spotify-connect._tcp.local
[Vollibrespot] librespot_connect::discovery: Post "/" {}
[Vollibrespot] : Connecting to AP "gae2-accesspoint-b-qcdb.ap.spotify.com:4070"



It would seem from your logs that the daemon received the login request from your client, but was unable to contact Spotify servers to actually authenticate - I would:

1. Try logging in directly with credentials to rule out any zeroconf/mdns issues
2. Recheck Volumio's dns settings to ensure it's got access to the Internetz.
User avatar
ashthespy
Objectivist
Objectivist
 
Posts: 288
Joined: Fri Jul 22 2016 08:16


Spotify Connect

Postby yungyaw » Fri Apr 12 2019 05:08

ashthespy wrote:
yungyaw wrote:I did as you told me. Here's the log:

Code: Select all
Stopping Volspotconnect2 Daemon...
Stopped Volspotconnect2 Daemon.
Starting Volspotconnect2 Daemon...
Started Volspotconnect2 Daemon.
vollibrespot v0.1.4 d207974 2019-03-26 (librespot 57a6586 2019-03-26) -- Built On 2019-03-26
[Vollibrespot] librespot_connect::discovery: Zeroconf server listening on 0.0.0.0:39967
[Vollibrespot] : Failed to register IPv6 receiver: Os { code: 19, kind: Other, message: "No such device" }
[Vollibrespot] librespot_connect::discovery: Post "/" {}
[Vollibrespot] : Connecting to AP "gae2-accesspoint-b-dmwm.ap.spotify.com:4070"
[Vollibrespot] librespot_connect::discovery: Post "/" {}
[Vollibrespot] : Connecting to AP "gae2-accesspoint-b-m3zs.ap.spotify.com:4070"
[Vollibrespot] mdns::fsm: received question: IN _companion-link._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _homekit._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _airplay._tcp.local
[Vollibrespot] mdns::fsm: received question: IN 04255CB411F0@Volumio._raop._tcp.local
[Vollibrespot] mdns::fsm: received question: IN YungYaw’s MacBook Pro._companion-link._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _sleep-proxy._udp.local
[Vollibrespot] mdns::fsm: received question: IN 40:4d:7f:6a:80:90@fe80::424d:7fff:fe6a:8090._apple-mobdev2._tcp.local
[Vollibrespot] mdns::fsm: received question: IN 40:4d:7f:6a:80:90@fe80::424d:7fff:fe6a:8090._apple-mobdev2._tcp.local
[Vollibrespot] mdns::fsm: received question: IN 40:4d:7f:6a:80:90@fe80::424d:7fff:fe6a:8090._apple-mobdev2._tcp.local
[Vollibrespot] mdns::fsm: received question: IN YY-2.local
[Vollibrespot] mdns::fsm: received question: IN YY-2.local
[Vollibrespot] mdns::fsm: received question: IN _companion-link._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _homekit._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _airplay._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _sleep-proxy._udp.local
[Vollibrespot] mdns::fsm: received question: IN YY-2.local
[Vollibrespot] mdns::fsm: received question: IN _companion-link._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _homekit._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _airplay._tcp.local
[Vollibrespot] mdns::fsm: received question: IN _sleep-proxy._udp.local
[Vollibrespot] mdns::fsm: received question: IN _spotify-connect._tcp.local
[Vollibrespot] librespot_connect::discovery: Post "/" {}
[Vollibrespot] : Connecting to AP "gae2-accesspoint-b-qcdb.ap.spotify.com:4070"



It would seem from your logs that the daemon received the login request from your client, but was unable to contact Spotify servers to actually authenticate - I would:

1. Try logging in directly with credentials to rule out any zeroconf/mdns issues
2. Recheck Volumio's dns settings to ensure it's got access to the Internetz.


Thanks for your support. Appreciate it.

1. Try logging in directly with credentials to rule out any zeroconf/mdns issues
I also installed Spotify Plugin for Volumio2 and entered my Spotify credential. I am able to play songs using this plugin. So I guess my Volumio is able to access the Internet and my credential is correct.

2. Recheck Volumio's dns settings to ensure it's got access to the Internetz.
Currently I'm using custom DNS setting of 1.1.1.1 and 9.9.9.9. I also tried disabling Custom DNS setting. It's still the same.

Anything else I can try?
Random avatar
yungyaw
Sunday DIYer
Sunday DIYer
 
Posts: 16
Joined: Wed Jul 22 2015 12:00


Spotify Connect

Postby Pulcik » Fri Apr 19 2019 12:44

Hi guys,
I actually experiencing similar problem as yungyaw .

I use and test volumio with spotifyconnect2 0.9.3 in real use in several places. One I have at home, and one in workshop. Both of them have some connection issues some times. When I restart volumio, it connect to wifi and everything works flawlessly.

In Volumio at home, I find, it lose the ability to "connect to the device" ability in spotify when connection to the internet or to wifi just a wifi connection is lost anytime. For example during WAN fixes from provider, etc. Volumio reconnect just fine, but the volumioconnct2 doesn't seem to reconnect to the spotiy system. Then you can try to connect to the device, but after timeout it disapears from the spotify list.

Probably same issue with my device in workshop. Some time, when I got in, I want to play some music, and same procces happens. After time out, it disappears. In workshop, I don't know if during the night, there were some connection loss. But during a day, I practically never experience any loss.

The fixes for me is still same, just restart the system, and everything works flawless again. I turn on the debug mode for now. So will see, if there is something, when this happen. I think, that there is some reconnecting to the services issue. I started thinking about automatic restart the system every night because of that.

Any idea where is the issue?
Random avatar
Pulcik
Fresh off the boat
Fresh off the boat
 
Posts: 2
Joined: Sat Mar 23 2019 22:42


Spotify Connect

Postby ashthespy » Fri Apr 19 2019 13:02

yungyaw wrote:Anything else I can try?

Pulcik wrote:The fixes for me is still same, just restart the system, and everything works flawless again. I turn on the debug mode for now. So will see, if there is something, when this happen. I think, that there is some reconnecting to the services issue. I started thinking about automatic restart the system every night because of that.

Any idea where is the issue?


Yes - the underlying library used doesn't handle reconnection when a connection is dropped. I have made some changes that should help, you can test it by using v0.1.5 of vollibrespot. More detailed instructions on how you could do this is over at the issue - https://github.com/balbuze/volumio-plug ... -481268992
User avatar
ashthespy
Objectivist
Objectivist
 
Posts: 288
Joined: Fri Jul 22 2016 08:16


Spotify Connect

Postby james_b » Thu May 09 2019 10:32

Pulcik wrote:Hi guys,
I actually experiencing similar problem as yungyaw .

I use and test volumio with spotifyconnect2 0.9.3 in real use in several places. One I have at home, and one in workshop. Both of them have some connection issues some times. When I restart volumio, it connect to wifi and everything works flawlessly.

In Volumio at home, I find, it lose the ability to "connect to the device" ability in spotify when connection to the internet or to wifi just a wifi connection is lost anytime. For example during WAN fixes from provider, etc. Volumio reconnect just fine, but the volumioconnct2 doesn't seem to reconnect to the spotiy system. Then you can try to connect to the device, but after timeout it disapears from the spotify list.

Probably same issue with my device in workshop. Some time, when I got in, I want to play some music, and same procces happens. After time out, it disappears. In workshop, I don't know if during the night, there were some connection loss. But during a day, I practically never experience any loss.

The fixes for me is still same, just restart the system, and everything works flawless again. I turn on the debug mode for now. So will see, if there is something, when this happen. I think, that there is some reconnecting to the services issue. I started thinking about automatic restart the system every night because of that.

Any idea where is the issue?


This is quite similar to an issue I've been experiencing – After some time my Pi 3 will disappear from the device list on my iPhone and reconnecting isn't possible. Oddly it's almost always still connectable from my MacBook Pro and once I have connected from the MBP I can once again connect from my iPhone. This doesn't quite feel like a rational situation, why would my MBP be more likely to see the Pi than my iPhone? Does this sound familiar to anyone else?

All devices in this scenario are connected via wifi. My Pi 2 in the next room with a wired connection rarely/never drops which I suppose stands to reason.
Random avatar
james_b
Sunday DIYer
Sunday DIYer
 
Posts: 46
Joined: Sat Feb 18 2017 12:57
Location: Bristol, UK

Previous

Return to Development talks

Who is online

Users browsing this forum: No registered users and 0 guests