diff --git a/source/_integrations/forked_daapd.markdown b/source/_integrations/forked_daapd.markdown index ddc8bda9275..47c8a932c8a 100644 --- a/source/_integrations/forked_daapd.markdown +++ b/source/_integrations/forked_daapd.markdown @@ -1,13 +1,13 @@ --- -title: forked-daapd -description: Instructions on how to integrate a forked-daapd server into Home Assistant. +title: Owntone +description: Instructions on how to integrate an Owntone server into Home Assistant. ha_category: - Media Player -ha_release: '0.110' +ha_release: "0.110" ha_iot_class: Local Push ha_domain: forked_daapd ha_codeowners: - - '@uvjustin' + - "@uvjustin" ha_config_flow: true ha_zeroconf: true ha_platforms: @@ -15,22 +15,26 @@ ha_platforms: ha_integration_type: integration --- -The `forked_daapd` integration allows you to control your [OwnTone (previously forked-daapd)](https://github.com/owntone/owntone-server) server from Home Assistant. This integration can control the forked-daapd outputs (zones) with limited playback control (play/pause, previous/next track) and media info support. Playlist manipulation is not supported. +The Owntone integration allows you to control your [OwnTone (previously forked-daapd)](https://github.com/owntone/owntone-server) 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. ## Requirements -The `forked_daapd` integration requires a OwnTone server built with libwebsockets enabled, version >= 27.0. +The Owntone integration requires an OwnTone server built with libwebsockets enabled, version >= 27.0. {% include integrations/config_flow.md %} ## Outputs -Once the `forked-daapd` integration is set up, outputs will automatically be loaded from the server and added to HA in real time. +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 forked-daapd server to autostart pipes and name your librespot-java pipe "librespot-java" (accompanying metadata is also supported through forked-daapd via a metadata pipe named"librespot-java.metadata"). The `forked-daapd` integration will find the librespot-java pipe in the database and will set it up as a source. +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 `forked-daapd` 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 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](/integrations/spotify). 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](https://owntone.github.io/owntone-server/integrations/spotify/#spotify). You should log in with the same Spotify account for both the Owntone server and the Home Assistant [Spotify integration](/integrations/spotify).