WTH is it so difficult to find the media_content_id in the media browser?

Month of "What the heck?!"
1

Hi all,
It’s really, really difficult to find the media id (with the auth string) so this can be used to play certain media in automations (e.g. play_media).
An idea could be to have a button (e.g. three dots?) to the right of each entry in the media browser to “see the content id/type”.
The content type is also required in automations, but this is sometimes simply ‘url’, but I guess that depends a bit.
Thanks!

2

I voted, as that’s a good idea.

But can’t you see the media_id in developer tools?

3

Well, supposedly you can start a new listener for an event, call the event… I spent 15 minutes and could not manage, and ended up opening a developer console in the browser and inspect the call itself.

4

Seems like relying on browser developer tools is exactly opposite all the work done to build a fancy Home Assistant browser UI. I mean, I was happy to do all my configuration in YAML, editing it with emacs, but I’m not the core demographic any longer it seems.

Ideally the UI used to build the service, er, action call would implement the browsing function of the media browser to discover the thing you want to play. But going to the media browser and hitting a “Copy media_content_id” button would be a big help.

I think maybe the URI appears in the browser ominisearch bar, but it’s embedded in the page URL and escaped all to hell.