Add media browser to Yoto

[piitaya]

Proposed change

Needs #172753

Adds library browsing and targeted playback to the Yoto media player.

Users can open the media browser from a Yoto entity and navigate their card library. Cards expand into chapters, chapters into tracks, and any node can be played directly. The browser uses a yoto://card/<card_id>/<chapter_key>/<track_key> URI scheme, and play_media resolves the URI to the right play_card call. The card segment namespaces the identifier so groups can be added later without breaking existing URIs.

Two small UX choices keep the tree compact:

• Single-chapter cards expand straight to their tracks, skipping a redundant submenu.
• Single-track chapters aren't expandable; clicking plays the track directly.

Playing a chapter starts from its first track. Targeted plays (chapter or track) always start from the beginning, while a bare card play preserves the card's own resume setting.

Library view

Card view

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 Document Yoto media browser home-assistant.io#45601
• This PR is related to issue:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• 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.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

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 diff between library versions and ideally a link to the changelog/release notes 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.

[home-assistant]

Hey there @cdnninja, mind taking a look at this pull request as it has been labeled with an integration (yoto) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of yoto can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant mark-draft Mark the pull request as draft.
• @home-assistant ready-for-review Remove the draft status from the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign yoto Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant update-branch Update the pull request branch with the base branch.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the pull request.

[Copilot]

Pull request overview

Adds media browser support and yoto:// URI-driven targeted playback for the Yoto media player integration.

Changes:

• Implement async_browse_media to expose the user’s Yoto card library (cards → chapters → tracks) with compact navigation rules.
• Implement async_play_media to resolve yoto://card[/chapter[/track]] URIs into play_card calls.
• Extend test coverage and snapshots to validate browse/play behavior and updated supported features.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
homeassistant/components/yoto/media_player.py	Adds browse/play media support and yoto:// URI parsing/building.
homeassistant/components/yoto/strings.json	Adds new translated exception messages for browse/play validation and failures.
tests/components/yoto/conftest.py	Expands mock card data to include chapters/tracks for browse/play tests.
tests/components/yoto/test_media_player.py	Adds tests for play_media routing, validation, and browse tree behavior.
tests/components/yoto/snapshots/test_media_player.ambr	Updates snapshots for new supported feature flags.

[Copilot]

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.