Repository navigation
Troubleshooting
Home > Troubleshooting
Contents: Not found · Empty library · No sound · Trigger does not run · Timing · Folder issues · Controls
- Confirm the server's UPnP/DLNA media service is enabled.
- Retry discovery once; the current source collects results after about nine seconds.
- Check that Homey and the server can communicate without guest-network isolation or blocked discovery traffic.
- Remember that the list contains media servers, not every UPnP speaker.
- Check the current discovery filter. HTTPS locations, hostnames, IPv6, or another advertised device type can be rejected.
Confirm the fix: your server appears in the pairing list and can be added. Another phone app finding it is helpful evidence, but not proof of this app's compatibility.
The community reports show why checking only a router's generic UPnP switch is not always enough.
- Verify that the server has scanned and published the folder.
- Try one small folder with a single ordinary MP3 file.
- Check IP Address, including the port. Restart the app after changing it.
- Check that you selected the actual file, or Play this folder inside the intended folder.
- Reselect entries after renaming folders or rebuilding the server's library.
- Review server endpoint and metadata compatibility.
Confirm the fix: the file selector offers your test sound and the direct-output action returns a usable Url.
Folder-selection mistakes and server-specific browsing errors appear in the community discussion; they do not all have the same cause.
- Check whether the card returned a Url, or only attempted a trigger event.
- For the direct-output action, keep Finish unchecked.
- Connect Url to the destination action's URL field and connect the execution path too.
- Make sure the destination can download that URL on its own network.
- Check the destination's supported audio format and response type.
- For a trigger-based Flow, see the next section.
Confirm the fix: the destination plays one short sound from the direct-output example.
A successful library request does not confirm playback. The app does not command a speaker solely by its IP address.
The current 1.2.14 source registers all three device triggers with a filter that expects an extra id argument and matching state. The published cards expose only the device argument, and the playlist manager does not supply that matching state.
A local check of the actual listener confirms that the advertised device-only arguments do not match. This affects Url trigger, Stopped, and Finished. It is a source limitation, not a missing setting you should search for.
For a file-playback test:
- Use Play a UPnP file in Advanced Flow's Then section.
- Leave Finish unchecked.
- Connect its own Url output directly to the destination.
Confirm the alternative: the destination receives the URL and starts playback without a separate trigger Flow.
Older trigger-based examples are retained as history with this limitation clearly marked. This manual does not change the app's runtime code; report the trigger issue if it affects your installation.
- Check the returned Duration. Its unit is milliseconds.
- If it is 0 or wrong, correct the media server's file metadata or try another known-good file.
- Increase the extra delay if the player starts slowly.
- Avoid overlapping requests to the same UPnP Player.
- Remember that this app does not receive actual player completion feedback.
Confirm the improvement: several manual tests finish in a sensible order. Exact synchronization still depends on the destination, network, and metadata.
If a waiting card never completes after another request starts, the newer request may have cleared its timer. Homey may eventually time out that waiting card.
- Select Play this folder, not a navigation-only folder entry.
- Use a folder containing direct files; nested folders are not gathered recursively.
- Reselect the folder if the media server rebuilt its library IDs.
- Start with Normal, not a random mode.
- Review the current random-mode edge cases.
Confirm the fix: a small ordered test selects every intended file once. A working URL-forwarding route is still required for folder cards to play those files on a destination.
Start an actual file or folder through a Flow before using Play. There is no saved current file to resume on a fresh player.
Previous has a capability-name mismatch in the current source; do not rely on it. Use a specific file-selection action instead.
Stopping this app only stops its timers. Use your destination app's own controls if the physical sound must stop.
Share the app version, Homey model, media-server software, destination app, selected card, and the step that failed. Say whether a direct URL output appeared. Avoid posting private file URLs or 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!