search

ashthespy / Vollibrespot

Spotify Connect daemon for Volumio
MIT License
20 stars 9 forks source link

Cannot connect to Hifiberry with Spotify connect #13

Open Mrcloc opened 1 year ago

Mrcloc commented 1 year ago

It will often connect fine, but half the time Spotify will say connecting, and then never connect. And from any device. I've soft restarted the Hifiberry, I've turned the Spotify source on and off, I've restarted Spotify on PC and phone, but to no avail. This will go on for a long time, and then suddenly it will decide to connect. Issue

ashthespy commented 1 year ago

Would you have some logs to share from the daemon while this is happens? You could try also to switch to credential based auth on the daemon to rule out issues with mdns..

potatoleaf commented 11 months ago

I have the same problem since a few weeks. Journalctl shows the following entries:

Aug 08 19:07:43 tuberadio python3[398]: INFO: audiocontrol2 - configuring watchdog spotifyd: ['spotify']
Aug 08 19:07:49 tuberadio systemd[1]: Starting Vollibrespot...
Aug 08 19:07:49 tuberadio vollibrespot[741]: vollibrespot v0.2.4 UNKNOWN UNKNOWN (librespot 1a224a3 2020-10-25) -- Built On 2023-04-04
Aug 08 19:07:49 tuberadio vollibrespot[741]: Reading Config from "/etc/vollibrespot.conf"
Aug 08 19:07:49 tuberadio vollibrespot[741]: [Vollibrespot] : Using Alsa backend with device: default
Aug 08 19:07:50 tuberadio systemd[1]: Started Vollibrespot.
Aug 08 19:07:56 tuberadio node[765]: Registering source 'spotify'...
Aug 08 19:07:57 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:07:57 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:07:58 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:07:58 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:07:58 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:07:58 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:07:59 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:07:59 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:07:59 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:08:00 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:08:02 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid

Are there any other logs I could provide?

ashthespy commented 11 months ago

You could try also to switch to credential based auth on the daemon to rule out issues with mdns..

innir commented 6 months ago

It indeed seems to be an issue with mdns, it's reported and fixed upstream: https://github.com/librespot-org/libmdns/issues/19

Mrcloc commented 6 months ago

Thank you for the responses. It's been a while but I haven't had further issues.

On Tue, 2 Jan 2024, 21:49 Philip Rinn, @.***> wrote:

It indeed seems to be an issue with mdns, it's reported and fixed upstream: librespot-org/libmdns#19 https://github.com/librespot-org/libmdns/issues/19

— Reply to this email directly, view it on GitHub https://github.com/ashthespy/Vollibrespot/issues/13#issuecomment-1874473268, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALO5ROPOEV6YFDQBLO5EA2TYMRQDVAVCNFSM6AAAAAASM6UVJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZUGQ3TGMRWHA . You are receiving this because you authored the thread.Message ID: @.***>