Skip to content
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

Error handling message: player_queues/play_media: Resource not found #3155

Open
1 task done
sunjaxx opened this issue Nov 9, 2024 · 4 comments
Open
1 task done

Comments

@sunjaxx
Copy link

sunjaxx commented Nov 9, 2024

What version of Music Assistant has the issue?

2.4.0b4

What version of the Home Assistant Integration have you got installed?

2024.11.2

Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

  • Yes

The problem

I get the error "Error handling message: player_queues/play_media: Resource not found" in the log when playing some tracks. For example track 4 of a specific album. Note that the track plays when using directly Jellyfin or VLC.

How to reproduce

Play a specific track

Music Providers

Jellyfin

Player Providers

Any (same error happens when using chromecast or DLNA)

Full log output

music-assistant.log

Additional information

No response

What version of Home Assistant Core are your running

2024.11.1

What type of installation are you running?

Home Assistant Supervised

On what type of hardware are you running?

Linux

@sunjaxx sunjaxx added the triage label Nov 9, 2024
@OzGav
Copy link
Contributor

OzGav commented Nov 9, 2024

Please supply the automation or script you are using which causes this.

@OzGav
Copy link
Contributor

OzGav commented Nov 10, 2024

@Jc2k There are a bunch of Jellyin invalid tracks in the log which I am going to guess is the reason for the resource not found later?

@OzGav OzGav added the Jellyfin label Nov 23, 2024
@Jc2k
Copy link

Jc2k commented Nov 23, 2024

The jellyfin error in that log could indicate the user lacks the download permission (We stream the download url).

If the user definitely has that permission then there is something else going on that means the jellyfin api isn't returning enough information to construct a url. That's not something I've seen happen before, so I'm currently more leaning towards a permission issue.

@OzGav
Copy link
Contributor

OzGav commented Nov 28, 2024

@sunjaxx based on the above please look into whether there is a permissions problem here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants