OpenVoiceOS / OpenVoiceOS/raspOVOS
librespot builtin mDNS is in conflict with avahi-daemon
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 52
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Tried out the image raspOVOS-bookworm-arm64-lite-2024-12-27, and it mostly worked fine.
I tried using the Spotify skill, but realized that I couldn't detect the running librespot instance. After reading https://github.com/librespot-org/librespot/wiki/librespot,-mDNS,-networking-and-containers I disabled the avahi-daemon and now I can detect it.
So maybe avahi-daemon needs to be disabled by default, or librespot must be build with support for avahi?
I still can't make "mycroft" start music playback on the librespot instance, but now it is detectable from the Spotify app on my phone...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the raspOVOS-bookworm-arm64-lite-2024-12-27 image, librespot, and avahi-daemon enabled. Read the linked librespot mDNS and networking guidance, then determine whether the image should disable avahi-daemon or provide librespot with avahi support; done means Spotify can detect the instance without manual daemon changes and playback behavior is clarified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, raspberry-pi
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100