Universal media player can not browse media
See original GitHub issueThe problem
When I select a universal media player based destination in the media browser, I get an error that this player doesn’t support browsing. When I directly select the configured chromecast child player, it works.
What version of Home Assistant Core has the issue?
Core-2022.2.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Universal media player
Link to integration documentation on our website
https://www.home-assistant.io/integrations/universal/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Logger: homeassistant.components.media_player
Source: components/media_player/__init__.py:1181
Integration: Media player (documentation, issues)
First occurred: 15:52:47 (3 occurrences)
Last logged: 15:53:18
media_player.woonkamer allows media browsing but its integration (universal) does not
Additional information
No response
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:7
Top Results From Across the Web
[Solved] Can't get 10.20.0 working. - Universal Media Server
For some reason I can't get 10.20.0 working. Version 10.19.0 runs without problem (serving audio FLAC files on my pc, mediaplayer Sangean ...
Read more >Roku Media Player - Connect fast forward or reward...
If I use the Media Player app on Roku to steam videos from Universal Media Server, the videos play, but I cannot fast...
Read more >How to Access Media from UPnP or DLNA using VLC
Open up VLC Media Player. · Go to View > Playlist [CTRL + L]. · On the left under Local Network, click on...
Read more >universal-media-server - Google Code
ID Status Summary
98 New MKV playback Type‑Defect Priority‑Medium
95 New Cant play MP4 movie Type‑Defect Priority‑Medium
90 New UMS ps3 no renderers Type‑Defect Priority‑Medium
Read more >Universal Media Server 10.21.1 - freshcode.club
Universal Media Server is a DLNA-compliant UPnP Media Server, which is ... detected as Digital Video (dv) browsing on some renderers tsMuxeR not...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Ah, seems there is an open issue for my problem: I’ve created a universal mediaplayer in order to have on/off action trigger sending IR signal to the physical player. In my case the single underlying child squeezelite does support media browsing fine. However when I want to browse media in the ‘parent’ universal player then it says it does not support media browsing.
Find it strange the issue does not attract more attention as universal media player is filling a need.
Adding to the original issue, this has become a showstopper problem for my particular use case of universal media player due to this additional change: “Starting with Home Assistant 2022.5, the TTS say service will set the media content ID to be a media source URI. These need to be resolved inside the media player using the media source integration.” I was using universal media player to pass through media_content_id to the the Android TV media player (by running an adb command “am start -a android.intent.action.VIEW -d {{ media_content_id }} -t audio/mp3” from the play_media command). This no longer works for TTS say service since the media source is no longer resolved to the actual mp3 url. This may or may not be a problem for a chromecast child media player, but wouldn’t this now be a problem for any child media player that doesn’t have a ‘native’ play_media service?