# Music Assistant

> Play and control the music on your own Music Assistant server by voice from any Thalovant device, in any room, with the Thalovant Music Assistant skill.

Source: https://docs.thalovant.com/concepts/music-assistant/

---
The **Thalovant Music Assistant** skill lets you control your own [Music Assistant](https://music-assistant.io) server by voice from any [client](/concepts/clients/) of a hub: "Play Bohemian Rhapsody in the kitchen", "Pause the music", "Move the music to the bedroom". The music plays on your Music Assistant players, not on the Thalovant device that heard you.

Ready to set it up? If you use Home Assistant, [play Music Assistant through Home Assistant](/music-and-home/music-through-home-assistant/). If you don't, [turn Home media on by voice](/music-and-home/home-media/), or, to run a program on a machine of your own, [play it without Home Assistant](/music-and-home/music-assistant-without-home-assistant/). The Home Assistant and bridge pages have a picture for every step.

## What It Does

- Plays what you ask for from your Music Assistant library and streaming services, on the speaker you name or the one you mapped to the device that heard you.
- Controls the queue, the music volume, shuffle and repeat, groups speakers and says what is playing.
- Talks to your own server with a token you create, through a link your home opens to the hub or, on a hub of your own, directly. See below.

## What You Can Say

| You want | Say |
| --- | --- |
| Play something | "Play Bohemian Rhapsody." "Play some music by Queen." "Play my Discover Weekly playlist." "Tune the radio to BBC Radio 6." "Play album Abbey Road." |
| Pick the room | "Play Bohemian Rhapsody in the kitchen." "Play Abbey Road on the living room speaker." |
| Similar or favourites | "Play more music like this." "Shuffle the favorites." |
| Control playback | "Pause the music." "Resume the music." "Next song." "Previous song." "Restart this song." |
| Volume | "Turn the music up." "Turn the music down." "Set the volume of the music player to 40." "Mute the music player." |
| Shuffle and repeat | "Shuffle the music." "Loop this song." "Loop the music queue." "Turn repeat off." |
| Ask | "What's playing?" "Who sings this?" "Add this song to my favorites." |
| Queue | "Add Hotel California to the queue." "Play Hotel California next." "Clear the queue." |
| Rooms | "Move the music to the bedroom." "Play the music in every room." "Group the kitchen with the living room." "Ungroup the speakers." "Which speakers are playing?" |

Say these as written: the skill matches whole sentences, and a few look longer than everyday speech on purpose, so that the other skills (Volume, Home, the media skills) keep theirs. "Mute the music" is taken by another skill, so say "mute the music player".

Every answer is spoken in the speaker's language and says what really happened: the title that was queued, or why nothing was. The skill ships the same 65 language tags as the other Thalovant skills; translations are machine-made.

## How The Skill Reaches Your Server

A hub in the cloud can't open `http://192.168.x.x:8095`, so the skill has three ways in. The **Transport** setting picks one:

| Transport | How it gets to your server | Pick it when |
| --- | --- | --- |
| Home Assistant | Through your [linked Home Assistant](/manage/home-assistant/), which already connects out to your hub and has the Music Assistant integration. | You run Home Assistant. |
| Home bridge | Through [Home media](/music-and-home/home-media/), which a Thalovant device of yours hosts, or through a bridge you run yourself on a machine that stays on, which connects out to your hub. See [Play Music Assistant Without Home Assistant](/music-and-home/music-assistant-without-home-assistant/). | You run Music Assistant without Home Assistant. |
| Server address | The skill calls the server's address itself, with a token you enter in the skill's settings. | The hub belongs to your household alone. |
| Automatic | The home bridge if it is online, then Home Assistant if it is, then the server address for a device you listed. | Most people. It is the default. |

On the first two routes nothing is opened on your network and your Music Assistant token stays at home. Each household reaches its own bridge or Home Assistant and nobody else's, so they are the routes for a hub other people use. Home Assistant answers in its own words, in English or French. The bridge and the server address answer in the speaker's language.

The server address route is for a private hub only. A server address and token in the skill's settings serve every device on the hub, so a public hub refuses them, and a hub with them set can't be made public. Only the devices you put in **Allowed devices** can use it, and an empty list means nobody.

Some things only the server address route can do, because neither link carries them: adding the current song to your favorites, clearing the queue and restarting a song. Playing a whole genre is one of them: through the links "jazz" is searched as a name (a track, artist, album, playlist or radio station called jazz), not as a genre, so name something you have. With **Automatic** and a listed device, the skill falls back to the server address for these and for a speaker the link can't find. Otherwise it says it couldn't do that.

## Set Up The Server Address Route

1. **Create a token in Music Assistant.** Open your profile in the Music Assistant web interface and create a long-lived access token. Music Assistant 2.4 or newer needs one for every connection.
2. **Add the skill to your hub's runtime group** from the marketplace (see [Add a Skill to a Hub](/manage/add-a-skill-to-a-hub/)).
3. **Fill in its settings.** Set the route to **Server address**, then enter the server **URL** and the **token** (both stored as secrets), the devices in **Allowed devices**, and optionally a **Default player**, one `device=Player name` line per Thalovant device in **Device players**, and nicknames in **Player aliases**.
4. **Say "play some jazz".** On this route a genre works. If something is missing, the skill says what to do: the server is not set up, unreachable, or refused the token.

If the hub's runtime can't reach the server, it can't play. A server on the internet needs HTTPS and an authenticating proxy or tunnel: don't publish port 8095 without one. If your runtime's network policy blocks private addresses, it must allow the server's address and port. For a self-signed certificate on a LAN server, turn off **Verify TLS certificate**.

## Which Speaker It Uses

The device that spoke picks the room. From version 0.2.0 the order is: a room named in the sentence, your **Device players** entry, a Music Assistant player named after the speaking device, the **Default player**, then the only player there is. The device's name is matched almost exactly. Up to 0.3.0 that was its client name, client ID or site ID. From 0.4.0 it's the name the hub's own record gives the device, `client-` followed by its ID, or that ID alone, and the site ID no longer counts. A bare "resume" after "pause" is taken again, as long as music is really paused on that player. The rest of this paragraph still applies: "pause" acts on the player you mapped to that device, and "in the kitchen" is matched against your Music Assistant player names and your aliases. The left side of a `device=Player` line is the device's name in the console, or its client ID.

## A Thalovant Speaker As A Music Assistant Player

A Thalovant speaker can be a Music Assistant player of its own and play on its own speaker, with the music ducking under the assistant's voice. It is off by default. Your device's own guide shows how to turn it on, with your Music Assistant host and the client name the console shows for the device, so the player carries that name. See [Play Music Assistant on a Thalovant Speaker](/music-and-home/music-assistant-on-a-speaker/). Music Assistant finds it as a Squeezelite player with no setting on the server, and from skill 0.2.0 to 0.3.0 "play some jazz" said to that speaker plays there with no **Device players** entry, because the player is named after the device. From 0.4.0 that holds only when the player is named after the hub's own name for the device (`client-` followed by its ID); otherwise add a `<device>=<player name>` line to **Device players**. Your device's own guide also shows how to turn it off.

## "Volume Up" And The Volume Skill

The skill only claims sentences that say "music", "song", "queue" or "speakers". Bare "volume up", "mute", "pause" and "next" are taken only while Music Assistant is really playing on your device's player, checked live; otherwise the Volume skill and the other skills answer as before. OVOS offers bare commands to a skill only for a few minutes after you last spoke to it, so start the music by voice; "turn the music up" always works.

## Limits

- The hub must be able to get to your server one of the ways above.
- Audiobooks and podcasts are not searched in this version.
- The skill never says something played unless Music Assistant accepted the command.
