OwnTone
The OwnTone integration allows you to control your OwnTone (previously forked-daapd)
Requirements
The OwnTone integration requires an OwnTone server built with libwebsockets enabled, version >= 27.0.
Configuration
To add the OwnTone integration to your Home Assistant instance, use this My button:
OwnTone 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.
Manual configuration steps
If it wasn’t discovered automatically, don’t worry! You can set up a manual integration entry:
-
Browse to your Home Assistant instance.
-
In the bottom right corner, select the
Add Integration button. -
From the list, select OwnTone.
-
Follow the instructions on screen to complete the setup.
Outputs
Once the OwnTone integration is set up, outputs will automatically be loaded from the server and added to HA in real-time.
Pipes
As OwnTone supports playing audio input via a pipe, this integration supports the forwarding of basic player controls (play, pause, next track, previous track) directly to the pipe’s source. Currently, only the pipe source librespot-java is supported. To use this, configure your OwnTone server to autostart pipes and name your librespot-java pipe “librespot-java” (accompanying metadata is also supported through OwnTone via a metadata pipe named “librespot-java.metadata”). The OwnTone integration will find the librespot-java pipe in the database and will set it up as a source.
Playlists
The OwnTone integration will treat playlists in the database as sources. The number of playlists shown as sources can be set in the integration’s configuration options.
Spotify
The OwnTone integration supports media browsing via the Spotify integration. However, to play Spotify content, your OwnTone instance must be logged in with Spotify. This can be done through OwnTone’s own web interface. For more details, see OwnTone’s notes on Spotify