Squeezebox (Lyrion Music Server)

The Squeezebox integration allows you to control music players from the Lyrion Music Server (LMS) ecosystem. Lyrion Music Server was formerly known as Logitech Media Server.

This integration connects to an existing LMS server and provides both media players and sensors for monitoring server status.

The Squeezebox music player ecosystem, which can be controlled through this integration, includes hardware audio players from Logitech, including Squeezebox 3rd Generation, Squeezebox Boom, Squeezebox Receiver, Transporter, Squeezebox2, Squeezebox and SLIMP3, and many software emulators like Squeezelite, SqueezeSlave, SoftSqueeze and SqueezePlay.

Supported devices

The integration supports any Squeezebox compatible hardware or software players and both Lyrion Music Servers and Logitech Media Servers.

Prerequisites

1. One or more Squeezebox compatible hardware or software players.
2. One or more Lyrion Music Servers or Logitech Media Servers (LMS) with the Squeezebox players connected to these servers.

Configuration

To add the Squeezebox (Lyrion Music Server) integration to your Home Assistant instance, use this My button:

Squeezebox (Lyrion Music Server) can be auto-discovered by Home Assistant. If an instance was found, it will be shown as Discovered. You can then set it up right away.

When the LMS cannot be discovered, it can be manually configured.

The Logitech Transporter which have two digital inputs can be activated using a script. The following example turns on the Transporter and activates the toslink input interface:

# Turn on Transporter and activate toslink interface
transporter_toslink:
  sequence:
    - action: homeassistant.turn_on
      target:
        entity_id: media_player.transporter
    - action: media_player.play_media
      target:
        entity_id: media_player.transporter
      data:
        media_content_id: 'source:toslink'
        media_content_type: 'music'

Options

Options for Squeezebox (Lyrion Music Server) can be set via the user interface, by taking the following steps:

• Browse to your Home Assistant instance.
• Go to Settings > Devices & Services.
• If multiple instances of Squeezebox (Lyrion Music Server) are configured, choose the instance you want to configure.
• Select the integration, then select Configure.

Announce

The Squeezebox media player entity supports the “announce” parameter in the media_player.play_media action. When media is played with announce:true, the current state of the media player is saved, the media is then played, and when playing is finished, the original state is restored. For example, if the media player is on and playing a track, once the announcement is finished, the track will resume playing at the same point it was paused by the announcement. If the media player was off, it will be turned off again after playing the announcement.

Extra Keys

The following extra keys are available to modify the announcement

These extra keys are optional. If announce_volume is unspecified, the announcement will play at the current volume of the player. If announce_timeout is unspecified, the announcement will play until completion.

Examples

Playing a local file as an announcement:

action: media_player.play_media
target:
  entity_id: media_player.squeezebox
data:
  media_content_type: music
  media_content_id: media-source://media_source/local/doorbell.mp3
  announce: true

Playing a local file as an announcement with volume of 20 and timeout of 60 seconds:

action: media_player.play_media
target:
  entity_id: media_player.squeezebox
data:
  media_content_type: music
  media_content_id: media-source://media_source/local/doorbell.mp3
  announce: true
  extra:
    announce_volume: 0.2
    announce_timeout: 60

Announcements and Text to Speech (TTS)

When using the “Text-to-speech (TTS): Speak” action, Home Assistant automatically sets the announce parameter as true, and the announcement features, such as pausing current playback, will be used.

However, the “Text-to-speech (TTS): Speak” action doesn’t support the extra keys described above. If you wish to use announce_volume and/or announce_timeout with TTS, you need to use media-source://tts/(tts_provider) to construct media_content_id as shown below.

Example

Play announcement using Text-to-speech (TTS) action

action: tts.speak
data:
  media_player_entity_id: media_player.squeezebox
  message: There's someone at the door
  cache: false
target:
  entity_id: tts.google_translate_en_co_uk

Play announcement using TTS media-source with announce_volume and announce_timeout

action: media_player.play_media
target:
  entity_id: media_player.squeezebox
data:
  media_content_type: music
  media_content_id: media-source://tts/tts.google_translate_en_co_uk?message="There's someone at the door"
  announce: true
  extra:
    announce_volume: 0.2
    announce_timeout: 60

Supported functionality

Entities

The integration provides the following entities.

Binary sensors

• Needs restart

  • Description: Server Service needs to be restarted (typically, this is needed to apply updates).

• Library rescan

  • Description: The music library is currently being scanned by LMS (depending on the type of scan, some content may be unavailable).

Buttons

• Preset 1 … Preset 6

  • Description: Play media stored in Preset 1 to Preset 6 on Squeezebox.

• Brightness up, Brightness down

  • Description: Adjust the brightness on Logitech Squeezebox players
  • Available on: Logitech hardware players with built-in screen, such as Radio and Boom.

• Bass up, Bass down

  • Description: Adjust the bass on Logitech Squeezebox players, such as Radio and Boom.
  • Available on: Logitech hardware players such as Radio, Duet and Boom.

• Treble up, Treble down

  • Description: Adjust the treble on Logitech Squeezebox players, such as Radio and Boom.
  • Available on: Logitech hardware players such as Radio, Duet, and Boom.

Sensors

• Last scan

  • Description: Date of the last library scan.

• Player count

  • Description: Number of players on the service.

• Player count off service

  • Description: Number of players not on this service.

• Total albums

  • Description: Total number of albums currently available on the service.

• Total artists

  • Description: Total number of artists currently available on the service.

• Total duration

  • Description: Duration of all tracks in service (HHHH:MM:SS).

• Total genres

  • Description: Total number of genres used in current service.

• Total songs

  • Description: Total number of music files currently in service.

Actions

The integration provides the following actions.

Action call_method

Call a custom Squeezebox JSON-RPC API.

See documentation for this interface on http://HOST:PORT/html/docs/cli-api.html?player= where HOST and PORT are the host name and port for your Lyrion Music Server.

This action can be used to integrate any Squeezebox action to an automation.

It can also be used to target a Squeezebox from IFTTT (or Dialogflow, Alexa…).

For example, to play an album from your collection, create an IFTTT applet like this:

• Trigger: Google Assistant, with sentence: I want to listen to album $
• Action: JSON post query with such JSON body: { "entity_id": "media_player.squeezebox_radio", "command": "playlist", "parameters": ["loadtracks", "album.titlesearch="] }

This can work with title search and basically any thing. The same wouldn’t have worked by calling directly Squeezebox server as IFTTT cannot escape the text field.

When specifying additional parameters in the Visual Editor, each parameter must be preceded by a hyphen and a space to correctly populate the array:

For example, to create an automation to mute playback, use the command mixer and the parameter muting:

resulting in the YAML:

# Toggle the muting state of the specified player
action: squeezebox.call_method
metadata: {}
data:
  command: mixer
  parameters:
    - muting

Where a parameter is an increment or decrement, it is necessary to place the value in double quotes.

For example, to increase the playback volume, use the command mixer and the parameters volume and the amount to increment:

resulting in the YAML:

# Increment the playback volume of the specified player by five percent
action: squeezebox.call_method
metadata: {}
data:
  command: mixer
  parameters:
    - volume
    - '+5'

Action call_query

Call a custom Squeezebox JSON-RPC API. The result of the query will be stored in the ‘query_result’ attribute of the player.

See documentation for this interface on http://HOST:PORT/html/docs/cli-api.html?player= where HOST and PORT are the host name and port for your Lyrion Music Server.

This action can be used to integrate a Squeezebox query into an automation. For example, in a Python script, you can get a list of albums available by an artist like this: hass.services.call("squeezebox", "call_query", { "entity_id": "media_player.kitchen", "command": "albums", "parameters": ["0", "20", "search:beatles", "tags:al"] }) To work with the results: result = hass.states.get("media_player.kitchen").attributes['query_result']

Data updates

The integration uses pollingData polling is the process of querying a device or service at regular intervals to check for updates or retrieve data. By defining a custom polling interval, you can control how frequently your system checks for new data, which can help optimize performance and reduce unnecessary network traffic. [Learn more] to receive updates from the Lyrion Music Server (LMS). It uses the web interface of the LMS to send commands. The default port of the web interface is 9000. It is the same port that you use to access the LMS through your web browser.

Known limitations

The LMS API, which is used by this integration, does not currently provide the ability to override or control fade-in & crossfade settings. This means that if you have enabled Play or Resume fade-in duration within the player’s audio settings, this fade-in will be applied to any announcement played. This could potentially lead to the start of an announcement being missed as it fades in. You should, therefore, consider a short Play or Resume fade-in duration or preferably disabling this feature if you make use of announcements.

Removing the integration

This integration follows standard integration removal. No extra steps are required.

To remove an integration instance from Home Assistant

1. Go to Settings > Devices & services and select the integration card.
2. From the list of devices, select the integration instance you want to remove.
3. Next to the entry, select the three-dot menu. Then, select Delete.