Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Yes. Home Assistant can browse albums and control playback from its dashboard or media browser, so a phone app is not required as the controller. The limitation is support: the selected media-player integration must expose browsing, not merely basic play, pause, and volume controls. For a unified library, Music Assistant adds a server, provider accounts, search, album and artist browsing, and richer queueing actions on top of Home Assistant. You still need a Home Assistant interface for setup and access, such as a browser, wall tablet, or desktop dashboard.
How can Home Assistant browse albums and control music without a phone?
Home Assistant represents speakers and other playback endpoints as media_player entities. When an integration supports media browsing, the entity exposes a navigable media tree containing the content that provider makes available. The dashboard media controls can then start, pause, seek, stop, or change volume, while the media browser lets you move through artists, albums, playlists, and other categories.
Browsing is not guaranteed for every player. An integration may provide reliable transport controls but no album tree, or it may expose only some content types. Home Assistant’s media_player.browse_media action uses the IDs and content types supplied by the player, so the available folders and identifiers differ by integration. If browsing is absent, that is usually a provider-capability issue rather than a requirement to use a phone.
What does Music Assistant add to Home Assistant?
Music Assistant separates your music library and provider accounts from the individual speaker integrations. You run a Music Assistant server, connect music providers and player providers to it, and then add its official Home Assistant integration. Music Assistant players appear as Home Assistant media-player entities that can be placed on dashboards, used in automations and scripts, or addressed by voice.
#1 Best Overall
- The new acoustic architecture replaces Move's single tweeter with two, unlocking a higher-fidelity stereo soundstage with crisp vocals and detailed instruments. With deep, dynamic bass powered by the precision-tuned woofer, you'll feel the emotional charge of a live performance.
- With automatic Trueplay tuning, Move 2 continually optimizes the sound for its surroundings. So, no matter where you are or what you play, you get the best listening experience.
- Listen twice as long as with the previous generation. All the acoustic updates work in concert for increased efficiency, giving you up to 24 hours of playback on a single charge.
- Shock absorbent materials protect against accidental drops, and the IP56 rating ensures spills, splashes, rain, dirt, and dust don't dampen your listening experience.
- Use the built-in handle to bring your music from one place to the next. When the battery needs a boost, set Move 2 on the included Wireless Charging Base, upgraded with a detachable power cable and more compact adapter. Charge on the go with any USB-PD power supply.
The server is required before the Home Assistant integration can work. The official integration documentation requires Music Assistant server version 2.4 or later. Its library layer supports searching and browsing albums and artists, while its playback actions can play or enqueue an album and can optionally turn on radio mode.
The project lists sources such as Spotify, YouTube Music, Qobuz, and Tidal, and playback ecosystems including Sonos, Chromecast, AirPlay, DLNA, and Squeezebox. Those are ecosystem-level examples, not a promise that every model or every feature is available. The exact player provider determines whether browsing, queueing, grouping, and other functions appear.
Which approach should you use?
The best route depends on whether you need a unified library, already have a compatible integration, or only want one streaming service.
| Approach | What you get | Requirements | Best fit |
|---|---|---|---|
| Native Home Assistant media-player integration | Dashboard controls and, when supported, a media browser for that player | A configured player integration that exposes browseable media | One or a few speakers whose existing integration already shows albums |
| Music Assistant plus Home Assistant integration | Provider search, album and artist browsing, queueing, radio mode, dashboards, automations, scripts, and voice control | Music Assistant server 2.4 or later, configured music and player providers, and the official Home Assistant integration | A consistent library across multiple services or playback ecosystems |
| Spotify Home Assistant integration | Spotify playback control and media-library browsing through Home Assistant | Active Spotify Premium account, compatible playback source, and a Spotify Developer application | A Spotify-focused setup where the account and developer prerequisites are acceptable |
Before choosing hardware, check the current provider page for your exact speaker model. A brand can support several transport features while a particular model or firmware version lacks browsing or queue operations.
How do you set up Music Assistant for phone-free album browsing?
Use this order so that each layer is working before you move to the next one.
1. Confirm the host and player
Keep your existing Home Assistant host if it can run the Music Assistant app. The documented installation can also use a separate Docker container, so a new mini PC is not automatically necessary. Confirm that your speakers or playback endpoints are supported by the relevant Music Assistant player provider, and note that capability can vary by model.
2. Run the Music Assistant server
Install the Music Assistant app on a supported Home Assistant installation, or deploy the documented Docker option. Open the Music Assistant interface and verify that the server is running version 2.4 or later. The Home Assistant integration cannot create players until this server is reachable.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- Precision-engineered drivers produce size-defying clarity and bass
- Ultra compact and lightweight so you can bring Sonos sound anywhere
- Durable, IP67 waterproof and dustproof, and ready for outdoor adventures
- Rechargeable battery gives you up to 10 hours of listening time
- Automatic Trueplay fine-tunes the sound for each new environment
3. Add music providers
In Music Assistant, configure the services that contain your music. Sign in or authorize each provider as required, then wait for its library and search index to become available. A provider may expose albums and artists but not every playlist or playback operation, so test the content you actually use.
4. Add player providers
Configure the speaker ecosystems and endpoints that Music Assistant should control. If a player is discovered more than once, identify the Music Assistant player entity you intend to use rather than mixing it with a separate native Home Assistant entity. This avoids selecting an entity that has controls but no Music Assistant library context.
5. Add the official Home Assistant integration
In Home Assistant, open Settings → Devices & services, choose Add integration, and select Music Assistant. Discovery normally finds a running server automatically. If it does not, use the integration’s manual server-address option and enter the address of the Music Assistant instance. After setup, the Music Assistant players should appear as Home Assistant media-player entities.
6. Test one player and one album
Place a Music Assistant media-player card on a dashboard, open its media browser, search for an album, and start playback. Test pause, seek, volume, and queue behavior before building automations. If the album is visible but playback fails, the problem is usually the player provider or account authorization rather than the dashboard.
How do you browse an album and start playback from a dashboard?
Open the dashboard that contains the media-player card, select the Music Assistant player, and choose the browser or media-library control. Navigate through the provider’s categories, or use search when the integration offers it. Select an album and choose play; where the player supports it, you can add the album to the queue instead of replacing the current item.
Home Assistant’s media browser is entity-specific. Selecting a different speaker can show a different tree, even when both speakers are in the same room. If you need a common library, browse the Music Assistant entity rather than switching among unrelated native player entities.
Music Assistant’s Play media action can be configured from the Home Assistant action editor without writing YAML. Choose the target player, select the album or other media type, and choose whether the item should play immediately or be queued. The action also offers radio mode where the provider supports it, which can continue with related tracks after the selected item.
Rank #3
- The information below is per-pack only
- Dual angled tweeters and a powerful midwoofer deliver rich, balanced stereo sound with deep bass.
- The perfect start or addition to your system, Era 100 SL makes Sonos sound more accessible.
- Stream over WiFi, pair via Bluetooth, or connect a turntable and more with line in.
- Go from unboxing to incredible sound in minutes with a quick plug-in and the Sonos app
Can automations and voice control replace the phone?
Yes. Once the player entity is present, the same controls used by the dashboard are available to scripts and automations. A routine can start an album at a scheduled time, enqueue music when a scene is activated, or stop playback when a condition changes. For library-aware actions, use Music Assistant’s search, library, and Play media actions rather than assuming a provider-specific URI will work on every player.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteVoice control is another interface, not a separate music library. Music Assistant’s Home Assistant integration makes its players available to Home Assistant voice features, but recognition and playback still depend on the configured provider and the target player. Keep a dashboard available for choosing an obscure album, checking a queue, or recovering from an authorization error.
How does the Spotify integration differ?
Spotify has its own Home Assistant integration for playback and media-library browsing. At publication, its documented prerequisites are an active Premium account, a compatible playback source, and a Spotify Developer application. These requirements are separate from Music Assistant’s server requirement.
Choose the Spotify route when your library is primarily Spotify and you do not need Music Assistant to combine several providers. Follow Spotify’s current Home Assistant setup instructions to create the developer application and authorize the account, then add the integration and select a compatible playback source. Account policies and authorization screens can change, so verify the current prerequisites during setup.
A Spotify-capable speaker is not automatically browseable through Home Assistant. The integration must expose the library and the speaker must be an accepted playback source. If Spotify tracks play from another app but no albums appear in Home Assistant, check the integration’s supported source list and account authorization first.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Why can you control a speaker but not browse its albums?
Playback controls and library browsing are separate capabilities. The following symptoms point to different fixes.
- Play, pause, and volume work, but there is no Browse button: the player integration may not implement browsing. Try the Music Assistant entity or another provider that explicitly supports library browsing.
- The browser opens but contains only a few categories: the provider is exposing a limited media tree. Check the provider’s documented capabilities and whether the account has access to the missing library.
- An album appears but will not play: verify the player provider, account authorization, and output endpoint. Test a single track before retrying a full album or queue.
- Music Assistant is not discovered: confirm that the server is running, reachable from Home Assistant, and on version 2.4 or later. Add it manually with the server address if automatic discovery fails.
- Two entities represent the same speaker: use the entity created by the route you intend to automate. Native and Music Assistant entities can have different browse trees and supported actions.
- Spotify setup stops at authorization: confirm Premium status, the developer application, and a compatible playback source; all three are listed prerequisites for the integration.
What hardware and accounts are actually required?
You need a Home Assistant installation, at least one playback endpoint supported by the chosen integration, and the relevant music-service account. Music Assistant adds a server process, but that process can run as a Home Assistant app or in a separate Docker container. Therefore, the phone-free experience does not inherently require buying another computer.
Rank #4
- Dual angled tweeters and a powerful midwoofer deliver rich, balanced stereo sound with deep bass.
- The perfect start or addition to your system, Era 100 SL makes Sonos sound more accessible.
- Stream over WiFi, pair via Bluetooth, or connect a turntable and more with line in.
- Go from unboxing to incredible sound in minutes with a quick plug-in and the Sonos app
- Trueplay fine-tunes Era 100 SL for the unique acoustics of the room.
| Component | Minimum practical requirement | What to verify |
|---|---|---|
| Home Assistant interface | Dashboard, browser, wall tablet, or another Home Assistant client | You need an interface for setup and day-to-day selection, even when no phone is used |
| Music Assistant server | Running server version 2.4 or later | Supported installation mode and network reachability from Home Assistant |
| Music provider | An account configured in Music Assistant, or Spotify’s separate account path | Library permissions, sign-in status, and provider-specific limits |
| Playback endpoint | A player supported by the selected provider | Exact model capability for browsing, queueing, grouping, and playback |
How should you choose between native browsing and Music Assistant?
Use native Home Assistant browsing when one integration already exposes the albums you need and you prefer the fewest moving parts. Add Music Assistant when you want one search and queue workflow across several services or speaker ecosystems, or when the native integration exposes controls but no useful library browser.
- Choose native integration first if you have one supported player and no need to merge providers.
- Choose Music Assistant if provider search, album browsing, queue management, radio mode, automations, or voice control are central to the setup.
- Choose the Spotify integration if Spotify is the only library you need and you can meet its Premium, playback-source, and developer-application requirements.
In every case, verify the exact player-provider documentation before purchasing a speaker or redesigning a dashboard. Broad ecosystem support does not establish feature parity for each model.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →What is the simplest phone-free operating pattern?
- Leave Home Assistant running on its existing host.
- Run Music Assistant there as an app, or in a separate Docker container if that better matches your installation.
- Configure one music provider and one player provider first.
- Add the official Music Assistant integration and confirm the new media-player entity.
- Pin that entity’s media browser to a dashboard on a wall tablet or desktop browser.
- Use the Play media action for repeatable albums, queues, and automations; use the browser for ad-hoc discovery.
This arrangement keeps the phone optional: it can still be used as another client, but the library, playback controls, and automations remain available from Home Assistant.
Frequently Asked Questions
Can I use a wall-mounted tablet instead of a phone for music control?
Yes. Any device that can open your Home Assistant dashboard can serve as the controller, including a wall-mounted tablet or desktop browser. The tablet is only the interface; the server, provider accounts, and speaker integrations continue running independently.
Do all albums from a subscribed service appear in Home Assistant?
Not necessarily. The provider integration decides which library categories and identifiers are exposed, and account permissions can limit what is returned. Check the provider capability notes when a playlist, album, or artist is missing rather than assuming the speaker is defective.
Can I switch providers without rebuilding my dashboards?
Usually, if you use Music Assistant entities and generic Home Assistant media actions. You can add or remove providers in Music Assistant while keeping the dashboard card and automation targets, although individual media identifiers may need to be selected again.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Why does an automation work for one speaker but fail for another?
Player providers expose different action sets, even within the same broad ecosystem. Compare the two entities’ supported media types and queue features, then target the entity whose provider advertises the action you are using.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
