Another huge update today! Some advanced configuration options and one breaking change with script variables. I have had multiple users reach out to me with some extremely advanced setups and this release adds some optional advanced config options to give a ton of flexibility.
New Features
Music Assistant Entity Association
You can now associate the Music Assistant Entity with its source entity to show them in a single chip in the main entity config options. For my personal setup, this solves the issue where I have to add both the main entity and the duplicated Music Assistant entity as separate items on my instance of YAMP. I can now combine them into a single entity in the card and my dashboard is much cleaner now!
- Basic Configuration: Associate a Music Assistant entity with any media player
- Jinja Template Support: Dynamic entity selection using jinja logic
- Automatic Entity Switching: Card switches between main and Music Assistant entities based on active playback
New Volume Entity Configuration Option
Added Jinja Template Support to the Volume Entity as well. This gives you some flexibility on which volume entity will be controlled in various scenarios. For example, if you have an action setup that targets a specific area and you want to control it from a single chip, you can now set logic up for both the Music Assistant Entity and the Volume Entity to follow the music.
Script Variables
Enhanced script variable passing for the new entity types:
yamp_entity: Current active playback entity (already existed, but logic changed. See breaking change below)yamp_main_entity: Main configured entityyamp_playback_entity: Resolved playback entity (main or Music Assistant)
Breaking Changes
Script Variable Behavior
If you have previously used the yamp_entity variable in scripts and want to target the main configured entity, you may want to switch to yamp_main_entity. The yamp_entity variable now represents the currently active playback entity (which may be the Music Assistant entity if it's actively playing), while yamp_main_entity always refers to the main configured entity.