Replies: 1 comment
-
I think you could just give each container a name in the Shairport Sync config? Then the AirPlay name remains consistent and Music Assistant won't end up with duplicates during restarts etc. 😄 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi @mikebrady
What about using the airplay_device_id setting for airplay 1 too ?
A static airplay device id would be useful for containerized airplay instances, when the
network interface mac address is generated randomly.
Kind regards,
Ruben
Background
I'm currently testing shairplay-sync as airplay provider for music-assistant
I've about eight airplay-sync instances running in podman containers.
During testing I restarted the containers a lot and noticed that I had about 400 airplay instances
in music-assistant at the end, from which only 8 were functional.
The airplay provider for music-assistant seems to cache airplay devices, even when they have been unpublished from mDNS.
I noticed that the airplay containers generated a new airplay device id on every start because the mac address changes.
See also AirPlay 1 prefix generation. As a workaround I'm now assigning static mac addresses to the containers using the
--network
flag.Beta Was this translation helpful? Give feedback.
All reactions