Spotify Connect device not showing
If your Spotycast or spotifyd device does not appear in the Spotify app, the root cause is usually Zeroconf discovery, network isolation, Docker network mode, firewall rules, or a broken spotifyd configuration.
Quick answer
A Spotify Connect device that does not show up is usually not an audio problem yet. It is most often a discovery problem. Before touching codecs or Icecast, verify that spotifyd is running, that your host is reachable on the LAN, and that Zeroconf is not blocked by Docker or firewall rules.
Typical symptoms
Device missing in Spotify app
The Spotycast / spotifyd target never appears in the list of available playback devices.
Device appears then disappears
Discovery is unstable, often because of mDNS filtering, VLAN separation or container networking.
Service is running but invisible
spotifyd is alive locally, but discovery packets do not reach the controller device.
Common causes
- Docker bridge networking instead of host mode
- mDNS / Zeroconf packets blocked or filtered on the LAN
- Phone and host on different networks, SSIDs or VLANs
- Firewall rules blocking local discovery or device reachability
- spotifyd misconfiguration, invalid credentials, wrong device_name or backend issues
- Service crash / restart loop making the device unavailable intermittently
Step-by-step fix
1. Confirm that spotifyd is actually running
Check the process or service first. A missing device can simply mean the service never started.
systemctl status spotifyd journalctl -u spotifyd -n 100 --no-pager
2. If running in Docker, prefer host networking
Zeroconf discovery is much more reliable in host mode than in bridged container networking.
network_mode: host
3. Make sure the controller and the host are on the same LAN
The Spotify app on your phone, tablet or desktop must be able to discover the host directly.
- Same subnet if possible
- No guest Wi-Fi isolation
- No client isolation on the access point
- No mDNS filtering between SSIDs or VLANs
4. Review spotifyd configuration
Invalid auth, a broken backend or a malformed config can keep the service alive but not usable.
device_name = "Spotycast" backend = "pulseaudio" bitrate = 320 zeroconf_port = 0
5. Restart the stack cleanly
After config or network changes, restart spotifyd and the related audio stack to republish the device.
systemctl restart spotifyd systemctl restart pulseaudio
What to collect in logs
If the issue persists, collect the smallest possible diagnostic bundle before changing anything else.
journalctl -u spotifyd -n 200 --no-pager docker logs <container_name> --tail 200 ip addr ip route
How Spotycast fits into the fix
Spotycast is designed to provide a more predictable path once Spotify playback is available on the host. It does not eliminate the need for Spotify Connect discovery, but it reduces complexity on the playback side by exposing a stable HTTP / Icecast stream for Roon, LMS, Volumio and similar players.
When this is probably not a discovery issue
Frequently asked questions
Why does Spotify Connect not show my device?
In most cases, the reason is discovery failure: Zeroconf or mDNS packets do not reach the Spotify controller, or the service is not publishing the device correctly.
Does Docker bridge mode break Spotify discovery?
It often makes discovery less reliable. For this use case, host networking is usually the safest and most predictable option.
Can firewall rules prevent the device from appearing?
Yes. Local discovery and reachability can both be affected by firewall policies, guest Wi-Fi isolation and VLAN separation.
Can Spotycast work with Roon or LMS after discovery is fixed?
Yes. Once Spotify playback is available on the host, Spotycast exposes it as a standard HTTP / Icecast stream that can be consumed as a radio URL by Roon, LMS / Lyrion and other compatible players.