[GH-ISSUE #793] Cannot use librespot if there are multiple librespot devices on the same network with discovery enabled. #413

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

Originally created by @ghost on GitHub (Jun 9, 2021).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/793

My current setup is:

  • one raspberry pi with librespot connected to my speakers
  • another raspberry pi with librespot connected to my headphones

Both devices are on the same network and both devices have discovery enabled and no credentials provided.

When I have both devices online and one is playing music, I am unable to switch playing to the other. I can see it in the spotify app as an available device, but as soon as I choose it, it starts playing for a second, then automatically switches back to the previous device.

I have to shutdown the first device to have the other device start playing successfully.

I can provide more info if anyone tells me what you need.

Thanks!

Originally created by @ghost on GitHub (Jun 9, 2021). Original GitHub issue: https://github.com/librespot-org/librespot/issues/793 My current setup is: - one raspberry pi with librespot connected to my speakers - another raspberry pi with librespot connected to my headphones Both devices are on the same network and both devices have discovery enabled and no credentials provided. When I have both devices online and one is playing music, I am unable to switch playing to the other. I can see it in the spotify app as an available device, but as soon as I choose it, it starts playing for a second, then automatically switches back to the previous device. I have to shutdown the first device to have the other device start playing successfully. I can provide more info if anyone tells me what you need. Thanks!
kerem 2026-02-27 19:30:28 +03:00
Author
Owner

@roderickvd commented on GitHub (Jun 9, 2021):

Cannot reproduce. Tested here:

1x instance named X running on RPi
1x instance named Y running on macOS

Running 0.2.0-dev. Connected to the same switch. Zeroconf enabled, no credentials.

Starting playback on X. Switching to Y -- seamless transition without jumping back. Switching to X - as expected. Y - again.

<!-- gh-comment-id:857955286 --> @roderickvd commented on GitHub (Jun 9, 2021): Cannot reproduce. Tested here: 1x instance named X running on RPi 1x instance named Y running on macOS Running `0.2.0-dev`. Connected to the same switch. Zeroconf enabled, no credentials. Starting playback on X. Switching to Y -- seamless transition without jumping back. Switching to X - as expected. Y - again.
Author
Owner

@JasonLG1979 commented on GitHub (Jun 10, 2021):

I can't reproduce either. I run 2 or 3 simulations instances, sometimes on the same machine all the time while testing things and never have any trouble.

Purely anecdotal but some routers don't play well with mDNS. I had nothing but trouble with my wifi router to the point that I ended up just getting a cheap standalone router/switch and just using it as a wireless AP. If you have an old router laying around that's a different brand or can barrow one you might try switching it out to see if it clears things up. At the very least I would check with Google to see if anyone else has had mDNS issues with your router.

<!-- gh-comment-id:858195558 --> @JasonLG1979 commented on GitHub (Jun 10, 2021): I can't reproduce either. I run 2 or 3 simulations instances, sometimes on the same machine all the time while testing things and never have any trouble. Purely anecdotal but some routers don't play well with mDNS. I had nothing but trouble with my wifi router to the point that I ended up just getting a cheap standalone router/switch and just using it as a wireless AP. If you have an old router laying around that's a different brand or can barrow one you might try switching it out to see if it clears things up. At the very least I would check with Google to see if anyone else has had mDNS issues with your router.
Author
Owner

@roderickvd commented on GitHub (Jun 14, 2021):

Cannot reproduce and no further replies.

<!-- gh-comment-id:860566393 --> @roderickvd commented on GitHub (Jun 14, 2021): Cannot reproduce and no further replies.
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#413
No description provided.