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