Repository navigation
Server Compatibility and Timing
Home > Server compatibility and timing
Contents: What the app does · Server requirements · Duration · Security · Advanced details
Universal Media Player browses the media server and returns the server's file URL. It does not convert the audio, upload your music to a cloud music service, or directly control arbitrary DLNA speakers.
The destination app and device decide which formats can play. Sonos, Chromecast, a television, and Homey's speaker do not necessarily support the same formats or playback actions.
The community discussion specifically explains that retrieving a URL is different from commanding a DLNA client. A speaker without a suitable Homey app or other controllable URL input is not automatically supported.
- A working UPnP/DLNA media library, not just a shared filesystem folder.
- HTTP access from Homey to the server's IPv4 address and port.
- Media files and library entries returned in a structure the app can read.
- File URLs reachable by the actual destination, not only by Homey.
Discovery applies a specific media-server filter. A phone discovering your server does not prove that this app accepts the same advertisement or server endpoint.
The 2021 community guide mentions Synology and router-based servers. Later posts report discovery and folder issues, and the developer reported a Synology fix. Treat those reports as history, not a guarantee for every model, firmware, or server.
Duration is read from the server's media metadata and converted to milliseconds. For example, a two-second sound has a duration of about 2000.
The app schedules:
estimated duration + extra device delay
- Single-file selection schedules a finish timer.
- Multi-file folder modes schedule a next-file timer.
- Missing or unreadable duration becomes 0, so the next event can happen after only the extra delay.
- The app receives no real end-of-track feedback from your speaker.
- Starting another request or stopping the player clears the current timers.
This means a slow player, an unavailable URL, a paused destination, or incorrect server metadata can all make the timing differ from what you hear.
When Finish is checked on the Advanced Flow action, its output tags arrive after that estimated wait. Leave it unchecked when the next card needs the URL to start the sound.
Keep the media server on your trusted home network. You do not need to expose it to the internet for ordinary local playback.
File URLs may reveal library paths or contain access information. Do not post a private URL, credentials, or an unredacted diagnostic log publicly.
The app logs file and browsing details. If support needs diagnostics, use the app's normal diagnostic-sharing process and explain the symptom separately.
The current browsing implementation sends UPnP ContentDirectory requests to:
http://YOUR-IP-AND-PORT/ContentDirectory/control
This is a source detail, not a URL to paste into a playback card. A server using a different control path may be discovered but fail when browsing.
The parser expects one usable media resource per returned file. Multiple resource representations or missing URL metadata can lead to unusable results. Artwork and duration are optional server data, not information the app independently measures.
For a failed browse, include your media-server product, software version, and whether discovery or file selection failed when reporting the problem. Do not include credentials.
Support development - If Universal Media Player is useful to you, you can support its
continued development through GitHub Sponsors,
Patreon,
PayPal, or
bunq.
Thank you!