Your question seems to be based on shallow understanding of what Assist is and what it does, or it's misphrased. No offense, either way ๐
Assist in itself does not find anything media related. Assist simply provides one or more pipelines, each consisting of a wake word engine (optional), a Speech-To-Text (STT) engine (optional), a "conversation agent" (a tool which decides how to respond to text with text) and a Text-To-Speech (TTS) engine (optional). You can pick each component, using either local or cloud options.
Finding media comes with the following challenges (as far as I can tell):
- the name of the media needs to be in the same language as the pipeline, otherwise the single-language STT engine will probably not understand (e.g. "play Feuer Frei by Rammstein on the kitchen speaker"). This does not apply to text-only pipelines
- even if it's in the same language, the STT might not be robust enough to recognize the actual thing you tell it to play due to made up words in the media title or simply for mishearing you (e.g. "play Fuu-Gee-La by The Fugees")
- even if all these were properly transcribed, Assist does not handle the searching of media in a library. That's a job for another integration, which you can leverage via
service calls actions. If you do have this integration (e.g. Music Assistant), then the conversation agent in Assist can use it, but...
- there's no built-in intent in the default conversation agent for searching or playing media. You'd have to create your own custom intent or use a conversation agent which can do that