You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To the best of my understanding, this blueprint tries to find a matching media_player entity looking into the list of entities provided by the Music Assistant integration. While this is generally working as expected it doesn't respect if the entity has been exposed to Assist (set via Settings -> Voice Assistants -> Expose) or not, nor does it check for the Aliases.
The text was updated successfully, but these errors were encountered:
I think an issue here is that Automations/Scripts aren't able to use Device Aliases from what I remember. Think this has been an ongoing request in HA, as I have seen others try to write scripts and automations like this expecting Aliases to work.
As far as checking if the device is exposed to voice assist or not, I don't really see a way to check that from an automation or script. There's no attribute I can see on media_player entity that tells you this information.
EDIT: Just to add to the above, if anyone knows a way to accomplish these we'd very much like to hear about it! I just personally haven't seen a solution to this within automations/scripts, and searches I have performed to look into it aren't yielding many answers unfortunately. As far as I can tell, only Intent Scripts seem to have awareness of Aliases and whether or not something is exposed to assist.
Yes, that is correct. Only the built in intents or custom sentences are able to use the aliases. It would be great if we could have access the aliases as well using templates.
To the best of my understanding, this blueprint tries to find a matching media_player entity looking into the list of entities provided by the Music Assistant integration. While this is generally working as expected it doesn't respect if the entity has been exposed to Assist (set via Settings -> Voice Assistants -> Expose) or not, nor does it check for the Aliases.
The text was updated successfully, but these errors were encountered: