-
-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mopidy as a streaming target #418
Comments
I think this is the same issue as the one with OSMC... I didn't account for the player doing a HEAD request before the GET. |
Yeah, I saw the OSMC issue but was not sure it was actually the same issue. Will test the forthcoming point release. |
Unfortunately, 2022.6.2 doesn't fix it. Same errors. |
OK, too bad. In that case it needs more work to investigate. Perhaps it connects once to determine the stream details and connects again after that. The stream backend in MA sees that as a disconnected client and closes the stream task. I saw the same with DLNA clients but once I send some special headers they did no longer connect twice. |
It hits that line so the client must have been connecting twice somehow |
I just got it to work. There is a way to tell mopidy to not do stream metadata lookups! https://docs.mopidy.com/en/latest/ext/stream/#confval-stream-metadata_blacklist Here an example from my mopidy.conf :
|
Exactly just came to the same conclusion :) I used
|
I think it would be nice to provide this info in a small article in the FAQ section: https://github.com/music-assistant/hass-music-assistant/discussions/categories/q-a-faq |
Done: #439 |
I have added the metadate_blacklist, but where do I add my Mopidy player to MA? I don't see it as one of the player providers. Edit: |
I know mopidy is not a supported target, but I'd like to understand what could be the issue, here.
To be clear, this is about streaming to mopidy, not supporting the library side.
The key error on mopidy seems to be
Is MASS using a special protocol that has to be understood by mopidy?
Full HA log
Full mopidy log
The text was updated successfully, but these errors were encountered: