The Owntone integration allows you to control your OwnTone (previously forked-daapd) server from Home Assistant. This integration can control the Owntone outputs (zones) with limited playback control (play/pause, previous/next track) and media info support. Playlist manipulation is not supported.
The Owntone integration requires an OwnTone server built with libwebsockets enabled, version >= 27.0.
Adding Owntone to your Home Assistant instance can be done via the user interface, by using this My button:
Owntone can be auto-discovered by Home Assistant. If an instance was found, it will be shown as “Discovered”, which you can select to set it up right away.
If there wasn’t any discovered automatically, don’t worry! You can set up a manual integration entry:
Once the Owntone integration is set up, outputs will automatically be loaded from the server and added to HA in real-time.
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.
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.
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. You should log in with the same Spotify account for both the Owntone server and the Home Assistant Spotify integration.