core: Media browser support for forked_daapd gives error
The problem
I access the media-player page, select ‘forde-daapd server’ (bottom right) to try and play media via my owntone (forked-daapd) integration and I get spinning blue icon indefinitely, or “Integration does not support browsing media”. forked-daapd server is working fine when accessed via own web interface, and shows up fine as media player in HA.
What version of Home Assistant Core has the issue?
2022.4.3
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
forked-daapd
Link to integration documentation on our website
https://github.com/home-assistant/core/pull/67564
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
N/A
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 18 (7 by maintainers)
hi there, I also have the same problem. Is there a way to enable media browsing with this implementation?
Hopefully we can sneak this PR in before the beta cut, but since it’s a bug fix it can always be added in a patch release. It’s too late to submit and get approval on a PR to add the rest of the media browsing support, but hopefully we can get that in by the 2022.10 release. In the meantime you can check https://community.home-assistant.io/t/forked-daapd-and-media-player-services/217126. I’ll leave a message there when I add more updates over the next week, and you can run it as a custom component until the additional PRs are merged. @ddppddpp Which TTS component are you using? It still works for me with google_translate, but if your forked_daapd instance cannot access the internal HA url then it won’t work (for TTS this can be worked around with the
base_urlsetting, but this does not work for other media sources. This is a broader HA issue).Let me see if we can get this back on track