10-14-2024, 05:04 PM
(10-09-2024, 01:37 PM)slowdown Wrote: Yes and no. I deactivated the network lock, Spotify discovered the RPi, and then I reactivated the network lock. The RPi now appears on the list of devices that I can connect to in Spotify. Strange. It also appears on another device on the same VPN that I did not deactivate the network lock on. In any case, it seems to work now. Thanks.
Once Spotify identifies a remote speaker (e.g. your RPi), it will continue to know about it for an interval of time (on the order of hours), even if it stops receiving direct advertisements, as long as both endpoints individually can maintain contact with the Spotify servers on the Internet which associate (for a time) both devices with your account.
Looking at your narrative, I'm going to guess that when your VPN ("network lock" is on, you will lose sight of the RPi eventually after your Spotify client stays disconnected for an hour or so. E.g. when you come back the next day and turn on the Spotify client, it will not see the RPi until you again temporarily deactivate your "network lock."
You can use Wireshark running on the same machine as your official Spotify client to monitor whether that machine is currently receving advertisements from the RPi. Choose the right interface and type "mdns" in the display filter line at the top.
In my experience, it is very hard to get wifi (wireless access points) to handle mdns messages. Get your system working reliably between Spotify client and Moode player when both are on the same wired subnet. If you need to introduce wifi, get familiar with what the network traffic looks like on a wired LAN, then introduce wifi with knowledge the the wireless AP or router configuration is the problem if it is not working, and knowing what to look for in the network without needing to use the spotify client as your test.
