v0.6.0-b1

Music Assistant Queue Actions v0.6.0-b1

🚀 Enhancements

• Add favorite to queue items @droans (#35)

v0.6.0

Music Assistant Queue Actions v0.6.0

🚀 Enhancements

• Add favorite to queue items @droans (#35)
• Add icons, strings @droans (#36)
• Add unfavorite action

v0.5.0

Music Assistant Queue Actions v0.5.0

Breaking Changes

mass_queue.send_command now requires that the config_entry_id for the Music Assistant Queue Actions integration is passed. If you are using this action in any of your scripts or automations, please ensure it is updated with the applicable ID.

What's New

Support for multiple Music Assistant instances

Initially, this integration would always select the first Music Assistant integration on your system. While this worked fine for most people, this would cause errors for anyone with multiple instances (even if all but one were disabled). With this change, it no longer matters - the actions will work no matter how many instances you have installed.

🚀 Enhancements

• Add support for multiple Music Assistant instances @droans (#31)

🧰 Maintenance

• Return queue items for grouped players @droans (#32)

v0.4.2

Music Assistant Queue Actions v0.4.2

🐛 Bug fixes

• Handle when player doesn't have active queue or active queue index is None @droans (#28)

v0.4.1

Music Assistant Queue Actions v0.4.1

🐛 Bug fixes

• Fix for null index @droans (#27)

v0.4.0

Music Assistant Queue Actions v0.4.0

New Action - mass_queue.send_command

Send any command to Music Assistant and receive back the response (if any). Find existing commands and data schemas by searching themusic_assistant/server repository for @api_command.

✨ New features

• Add send command @droans (#20)

🐛 Bug fixes

• Fix @droans (#24)

🚀 Enhancements

• Update get queue items action @droans (#6)
• Add send command @droans (#20)
• Update service yaml @droans (#21)

🧰 Maintenance

• Update readme @droans (#5)
• Update readme @droans (#15)
• Linting @droans (#18)
• Linting @droans (#19)
• Update service yaml @droans (#21)
• Add Pre-Release Release Drafter @droans (#23)
• Fix @droans (#24)

v0.3.0 - Add to HACS Default

Only changes made since v0.3.0 was correcting some action data. This release is a requirement to add to HACS Default Repo. v0.3.0 release notes below.

Music Assistant Queue Actions v0.3.0

New Features:

• Added new parameters for mass_queue.get_queue_items:
  • limit_before: Limit the number of items to display before current active item.
  • limit_after: Limit the number of items to display after the current active item.

Keep in mind that when limit_before is used, offset is ignored. When limit_after is used, limit is ignored.

Full Changelog: v0.3.0...v0.3.0-hacs

v0.3.0

Music Assistant Queue Actions v0.3.0

New Features:

• Added new parameters for mass_queue.get_queue_items:
  • limit_before: Limit the number of items to display before current active item.
  • limit_after: Limit the number of items to display after the current active item.

Keep in mind that when limit_before is used, offset is ignored. When limit_after is used, limit is ignored.

v0.2.0 - Events, Controller, and Performance Improvements

Music Assistant Queue Actions v0.2.0

NOTE: This version is required in order to use Music Assistant Queue Card v0.6.0. Please ensure you update this integration first.

New Features

Events: Events are now sent to Home Assistant for various changes. Two different event_types are now sent:

• music_assistant: Events received from Music Assistant. Events include queue_updated, queue_items_updated, and player_updated.
• mass_queue: Changes to the queues stored by the integration. Events include player_added, player_removed, player_updated, queue_added, queues_added, queue_updated, and queue_removed.

While the two events are similar, they are not exactly the same. The music_assistant event is sent when Music Assistant updates the queues, queue items, and players. The mass_queue events are sent when this integration updates the stored queues and players. Basically, if you want an automation to run as soon as the queue changes, use music_assistant. If you need the automation to get the queue items or otherwise need it to run when integration updates the queue, use mass_queue.

Big Change - Queue Controller

This integration now uses a controller to manage the queue states. This will help speed up mass_queue.get_queue_items calls in many instances.

With this release, all queues are requested when the integration is first loaded. Updated queues are then requested when a change is reported by Music Assistant. Previously, each time a queue was requested, the integration would ask Music Assistant to send a new queue. This could cause issues and slow down the responses, especially if Music Assistant wasn't running on the same machine.

What's Changed

• Use controller, add events by @droans in #2

Full Changelog: v0.1.0...v0.2.0

v0.1.0

Initial Release