Skip to content

Add documentation for Android Media Controls feature#1304

Open
FletcherD wants to merge 1 commit into
home-assistant:masterfrom
FletcherD:master
Open

Add documentation for Android Media Controls feature#1304
FletcherD wants to merge 1 commit into
home-assistant:masterfrom
FletcherD:master

Conversation

@FletcherD
Copy link
Copy Markdown

@FletcherD FletcherD commented Mar 24, 2026

Proposed change

I wanted to be able to control a media player entity natively on Android without having to open the app or navigate to a widget. So I added a feature to expose a Home Assistant media_player entity as native Android Media Controls in the notification shade, the same UI used by other media players on Android. That PR can be found here.

Type of change

  • Document existing features within Home Assistant Companion App
  • Document new or changing features for which there is an existing pull request elsewhere
  • Spelling or grammatical corrections, or rewording for improved clarity
  • Changes to the backend of this documentation
  • Remove stale or deprecated documentation

Checklist

  • I have read and followed the documentation guidelines.
  • I have verified that my changes render correctly in the documentation.

Additional information

- **Play/pause** — start or pause playback
- **Next/previous track** — skip to the next or previous track
- **Seek** — scrub to a specific position in the current track
- **Progress bar** — shows playback progress, even for entities that don't support seeking
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean by even for entities that don't support seeking


## Setup

1. In the Home Assistant app, go to **Settings** > **Companion App** > **Media controls**.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could make a deeplink to that. @jpelgrom did we consider doing deeplinks to settings?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants