Power On Media Player entity when Selected in the Music Assistant UI #4359
Replies: 5 comments 5 replies
-
|
bueller |
Beta Was this translation helpful? Give feedback.
-
|
+1 usecase: WOL (remote machines that have docker based player) |
Beta Was this translation helpful? Give feedback.
-
|
You can hook up a power control to a player which can be any HA entity that support toggling. This is existing functionality |
Beta Was this translation helpful? Give feedback.
-
|
@2sheds and @cociweb ... what functionality do you need for your use cases? I'd like to have MA create and update an Entity for each Player so we can create automations that use those entities as triggers. I think that is more universal, and provides the most flexibility, for any/all automations. |
Beta Was this translation helpful? Give feedback.
-
|
I absolutely support the idea. I accidentally created a duplicate: https://github.com/orgs/music-assistant/discussions/4847. It would be great to have an easy power-off action that shuts down the streaming device after a delay. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
FR>> user option in the UI to power-on and off a media_player entity or an MA event (for automation trigger), or an MA entity that identifies the Player Selected (for automation trigger) when it is 'selected' or deselected in the MA UI
Workarounds = none. While most Media Player entities already have on/off capabilities in Home Assistant, Music Assistant doesnt have an exposed method that can be used as a trigger (an entity state = "player selected", etc); so there is no way to create a home assistant automation to do this.
Use Cases>>
AVR and amps take a few seconds to boot and be ready to receive/send audio. In order not to miss the music, the AVR/amp needs to be on prior to the audio stream starting
Many people have the audio device hidden in a cabinet or out of reach. Especially automation people since the automation should handle everything and the device should never need to be physically touched or a physical remote ever be used.
MA is extensive and elegantly done but this basic automation feature is missing, and would be a welcome addition to make it a true automated solution. Thank you
Beta Was this translation helpful? Give feedback.
All reactions