Qualify Music Assistant to Bronze Quality Level

[OzGav]

Proposed change

Make required changes and provide justification to promote the Music Assistant integration to the Bronze Level.

• action-setup - Service actions are registered in async_setup
  

  core/homeassistant/components/music_assistant/__init__.py

  Line 52 in 78338f1

  async def async_setup(hass: HomeAssistant, config: ConfigType) -> bool:

• appropriate-polling - If it's a polling integration, set an appropriate polling interval
  status: exempt
  comment: Integration is local push.

• brands - Has branding assets available for the integration
  https://github.com/home-assistant/brands/tree/master/core_integrations/music_assistant

• common-modules - Place common patterns in common modules
  https://github.com/home-assistant/core/tree/dev/homeassistant/components/music_assistant

• config-flow-test-coverage - Full test coverage for the config flow
  https://github.com/home-assistant/core/blob/78338f161f8dbfa2bde3bd10fed76f5539fdc8ad/tests/components/music_assistant/test_config_flow.py

• config-flow - Integration needs to be able to be set up via the UI
  https://github.com/home-assistant/core/blob/dev/homeassistant/components/music_assistant/config_flow.py

  • Uses data_description to give context to fields
    See updated strings.json as part of this PR
  • Uses ConfigEntry.data and ConfigEntry.options correctly
    

    core/homeassistant/components/music_assistant/config_flow.py

    Line 129 in 6a01249

    data={

• dependency-transparency - Dependency transparency
  https://pypi.org/project/music-assistant-client/
  https://github.com/music-assistant/client

• docs-actions - The documentation describes the provided service actions that can be used
  https://www.home-assistant.io/integrations/music_assistant/#actions

• docs-high-level-description - The documentation includes a high-level description of the integration brand, product, or service
  https://www.home-assistant.io/integrations/music_assistant/

• docs-installation-instructions - The documentation provides step-by-step installation instructions for the integration, including, if needed, prerequisites
  https://www.home-assistant.io/integrations/music_assistant/#configuration

• docs-removal-instructions - The documentation provides removal instructions
  https://www.home-assistant.io/integrations/music_assistant/#removing-the-integration

• entity-event-setup - Entities event setup
  

  core/homeassistant/components/music_assistant/__init__.py

  Line 137 in 8200c23

  mass.subscribe(handle_player_removed, EventType.PLAYER_REMOVED)

• entity-unique-id - Entities have a unique ID
  

  core/homeassistant/components/music_assistant/entity.py

  Line 62 in 6a01249

  def unique_id(self) -> str | None:

• has-entity-name - Entities use has_entity_name = True
  

  core/homeassistant/components/music_assistant/entity.py

  Line 23 in 78338f1

  _attr_has_entity_name = True

• runtime-data - Use ConfigEntry.runtime_data to store runtime data
  

  core/homeassistant/components/music_assistant/media_player.py

  Line 145 in 6a01249

  mass = entry.runtime_data.mass

• test-before-configure - Test a connection in the config flow
  

  core/homeassistant/components/music_assistant/config_flow.py

  Line 74 in 6a01249

  except CannotConnect:

• test-before-setup - Check during integration initialization if we are able to set it up correctly
  

  core/homeassistant/components/music_assistant/__init__.py

  Line 66 in 78338f1

  try:

• unique-config-entry - Don't allow the same device or service to be able to be set up twice
  

  core/homeassistant/components/music_assistant/config_flow.py

  Line 67 in 78338f1

  await self.async_set_unique_id(

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[arturpragacz]

This needs #155963 and #156263 to be merged first.

I also still need to review rules above bronze.