Spotify Connect Not Showing? Fix Discovery Issues First
If your Spotycast or spotifyd device does not appear in the Spotify app, the root cause is usually discovery and network visibility: mDNS / Zeroconf, Docker network mode, firewall rules, client isolation, or a spotifyd publish issue.
Quick answer
A Spotify Connect device that does not appear is usually not an audio-path issue yet. It is most often a local discovery issue. Before touching codecs, outputs, or Icecast behavior, verify that spotifyd is running, the host is reachable on the LAN, and Zeroconf discovery is not blocked by Docker, Wi-Fi isolation, VLANs, or firewall rules.
Typical symptoms
Device missing in Spotify app
The Spotycast or spotifyd target never appears in the list of available playback devices.
Device appears then disappears
Discovery is unstable, often because of mDNS filtering, subnet separation, or unreliable container networking.
Service looks alive but stays invisible
spotifyd is running locally, but discovery packets do not reach the controller device correctly.
Why Spotify Connect devices stop appearing
Spotify Connect discovery depends on a clean local-network path between the publishing service and the controller device. If multicast discovery is filtered, the device may be healthy on the host but still invisible in the Spotify app.
- Docker bridge networking can interfere with discovery visibility
- mDNS / Zeroconf packets may be blocked or not forwarded correctly
- Phone and host on different SSIDs, VLANs, or subnets may prevent discovery
- Guest Wi-Fi or AP client isolation can stop local device visibility
- Firewall rules may block local reachability or discovery traffic
- spotifyd misconfiguration can prevent correct device publication
- Restart loops or backend failures may make the device appear intermittently
How to diagnose the issue
1. Confirm that spotifyd is actually running
A missing device can simply mean the publishing service never started or is restarting continuously.
systemctl status spotifyd journalctl -u spotifyd -n 100 --no-pager
2. If running in Docker, prefer host networking
For Spotify device discovery, host mode is usually much more predictable than 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 publishing host directly.
- Prefer the same subnet
- Avoid guest Wi-Fi isolation
- Disable AP client isolation if active
- Check that mDNS is not filtered across SSIDs or VLANs
4. Review spotifyd publishing settings
Broken auth, a backend mismatch, or invalid config can leave the service alive but unpublished or unusable.
device_name = "Spotycast" backend = "pulseaudio" bitrate = 320 zeroconf_port = 0
5. Restart the stack cleanly after changes
After config or network updates, restart spotifyd and the related audio stack so the device gets republished cleanly.
systemctl restart spotifyd systemctl restart pulseaudio
What to collect in logs
If the issue persists, collect a compact diagnostic bundle before changing more variables.
journalctl -u spotifyd -n 200 --no-pager docker logs <container_name> --tail 200 ip addr ip route
When this is not just a discovery problem
- Use Spotify Connect Not Working for the broader workaround and recovery path
- Use No audio if the stream is visible but silent
- Use Dropouts if playback stutters or cuts
- Use Metadatas if titles are missing or stale
Frequently asked questions
Why does Spotify Connect not show my device?
In most cases, the reason is a discovery failure: mDNS or Zeroconf packets do not reach the Spotify controller correctly, or spotifyd is not publishing the device as expected.
Does Docker bridge mode break Spotify discovery?
It often makes discovery less predictable. For this use case, host networking is usually the most reliable option.
Can firewall rules prevent the device from appearing?
Yes. Discovery visibility and host reachability can both be affected by firewall policy, guest Wi-Fi isolation, or subnet segmentation.
What if the device appears but playback still fails?
Then discovery is no longer the main issue. Move to the broader guide at Spotify Connect Not Working, or use the dedicated troubleshooting pages for no audio or dropouts.