Re: [SlimDevices: Plugins] [Announce] Spotty 2.0.0 - Spotify Connect for your Squeezebox
Hi everyone, I just registered here in order to say Thank You Michael! I'm running Spotty on a CentOS7-based LMS and it's working great. Only (small) issue so far is with synced players, where music simply doesn't start. I quickly searched through the thread and couldn't find any solution to that. Is there anything I can provide in order to help troubleshooting ? Also, I see that the helper program is always started with "--bitrate 96" and wondered if this shouldn't match the configured quality (or if it is normal to have it always started with this low bitrate). Regards! flashpaz's Profile: http://forums.slimdevices.com/member.php?userid=67942 View this thread: http://forums.slimdevices.com/showthread.php?t=108561 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Spotty 4.7.0
Hi, and first of all thanks for this great plugin. I am running the docker image from lmscommunity/logitechmediaserver:stable on a Linux x86-64 host Today it means Server version 8.2.1 and Spotty 4.7.2. I also have a Spotify family account. I have 4 Spotify accounts configured and my problem is that I can only see my SB players from the Spotify apps of the first configured account (tested on the web Spotify player for Chrome and Android App). Other accounts from the family don't see any player, even though they have been successfully added to the plugin config (via explicit credentials and not authorization which doesn't work). By investigating the network, I can see that all the devices are requesting spotify-connect._tcp.local via mDNS/5353 and getting no reply. I have seen many posts suggesting to map port 5353/udp to the container but as far as I can tell, no process actually *binds* to this port (and I checked that it is free and not already used by another host process or container). Anyway, port is mapped and it doesn't help. So I think my question is: which process is supposed to bind to this port ? slimserver.pl or spotty-x86_64 ? From the code, I think it's libresport which actually binds to this port so it should be spotty-x86_64, right ? As far as I can tell, it doesn't bind to 5353 (tested with and without auto-discover). Also, I don't explain why the first account (and only this one) can see the players, even though mDNS doesn't work... Thanks a ton for your hints! flashpaz's Profile: http://forums.slimdevices.com/member.php?userid=67942 View this thread: http://forums.slimdevices.com/showthread.php?t=115592 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Spotty 4.7.0
mherger wrote: > > By investigating the network, I can see that all the devices are > > requesting spotify-connect._tcp.local via mDNS/5353 and getting no > > reply. I have seen many posts suggesting to map port 5353/udp to the > > container but as far as I can tell, no process actually *binds* to > this > > port (and I checked that it is free and not already used by another > host > > process or container). Anyway, port is mapped and it doesn't help. > > It's my understanding that the helpers would not "bind" to that port but > > listen to UDP broadcasts on that port. And those broadcasts don't make > it through to the container. From what I understand most solved this > problem using Docker's host mode networking. Thanks, it is starting to make sense. By further investigating, I also realize that by default a host doesn't receive the mDNS multicast traffic (IP 224.0.0.251). Typically, a Linux host first have to start the avahi-daemon and this triggers a "registration" to tell the whole networks "hey, please also send me mDNS queries". I therefore see two options: 1) Have avahi running on the docker host and have the container use "host" networking 2) Have the container use a dedicated LAN IP (using macvlan or ipvlan docker networks) and have avahi running *inside* the container. I'll make some further tests and report here. Cheers! flashpaz's Profile: http://forums.slimdevices.com/member.php?userid=67942 View this thread: http://forums.slimdevices.com/showthread.php?t=115592 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Spotty 4.7.0
flashpaz wrote: > Thanks, it is starting to make sense. By further investigating, I also > realize that by default a host doesn't receive the mDNS multicast > traffic (IP 224.0.0.251). Typically, a Linux host first have to start > the avahi-daemon and this triggers a "registration" to tell the whole > networks "hey, please also send me mDNS queries". I therefore see two > options: > 1) Have avahi running on the docker host and have the container use > "host" networking > 2) Have the container use a dedicated LAN IP (using macvlan or ipvlan > docker networks) and have avahi running *inside* the container. > > I'll make some further tests and report here. > > Cheers! OK, so this took some time. I haven't been able to get a working docker/mDNS setup with a "sidecar" avahi container (reflector). As mentioned, the easiest option is to have the container running with a dedicated IP on the network. MACVLAN is the de facto option but as it creates a dedicated MAC address, it doesn't work if the docker host is a VMware guest with the default security settings, because they forbid MAC address forgery. Instead, I went down the IPVLAN route and this works fine. Also, I have a common backend network between this container and an haproxy container, because I also want to have the UI on TLS (the players are still doing plaintext http on port 9000, though). I created the IPVLAN network with this command: Code: docker network create -d ipvlan --subnet a.b.c.0/24 --ip-range a.b.c.64/28 --gateway a.b.c.1 -o parent=eth0 myipvlan And this is my docker-compose file Code: version: '3.8' services: lms: image: lmscommunity/logitechmediaserver:stable container_name: lms restart: unless-stopped logging: driver: journald options: tag: lms volumes: - ./config:/config - /mnt/music:/music - ./playlist:/playlist - /usr/share/zoneinfo/Europe/Zurich:/etc/localtime:ro environment: - PUID=1000 - PGID=1000 networks: myipvlan: ipv4_address: a.b.c.64 haproxy_back: ports: - 9000:9000/tcp - 9090:9090/tcp - 3483:3483/tcp - 3483:3483/udp networks: myipvlan: external: name: myipvlan haproxy_back: external: true Cheers and thanks for the hints! flashpaz's Profile: http://forums.slimdevices.com/member.php?userid=67942 View this thread: http://forums.slimdevices.com/showthread.php?t=115592 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
