Need help with spotify-card?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

custom-cards
155 Stars 38 Forks Other 161 Commits 6 Opened issues

Description

Spotify playlist card for Home Assistant card

Services available

!
?

Need anything else?

Contributors list

hacs_badge spotify-card

Build

Home Assistant Spotify Lovelace Card

DISCLAIMER: This project is a private open source project and doesn't have any connection with Spotify.

This card supports listing the users currently available devices and the users playlists on Spotify. Choose an online media player and click on a playlist to play it on the device. This component will query the current playback from the Spotify Integration and tries to reflect the currently playing playlist.

The component uses the Spotify Integration and spotcast and both of them have to be installed for the card to function properly.

The forum thread can be found here

See release information on Github for release notes

Requirements

Spotify Integration and spotcast have to be installed (Spotcast is needed for many other things than playing on cast devices). This card should work in all newer major browsers. If it does not work for you please provide detailed reports in an issue ticket.

Installation

HACS users

Follow the HACS instructions when installing it.

Manually

Copy the content of the

dist
folder to
www/community/spotify-card/
in your Home Assistant configuration directory. Create these folders if they do not exist.

Then you have to add spotify card to your resources. This can be done via

Settings -> Lovelace Dashboards -> Resources
. Add this path:
  /local/community/spotify-card/spotify-card.js

If you do not have the

Resources
tab available, you have to enable the advanced mode for Lovelace. To do so, click on your username on your Home Assistant dashboard and enanble the setting.

Usage

Add the card via lovelace to your dashboard. All of the settings can be configured via the visual editor.

Advanced usage

If you want to hide specific devices, you can do so in the advanced tab of the visual editor. If you are not using the visual editor see YAML mode. You can enter as many regular expressions as you like, separated by a comma. If any of these rules apply to a device-name it will be hidden. The rules are evaluated against the whole device-name so

room
will not match
bedroom
. Here are a few examples:
  • .*room
    hides all devices ending with room
  • bath.*,kids.*
    hides all devices which start with bath or kids

YAML mode

If you are not using the visual configuration of Lovelace you can add the card like this:

  cards:
    - type: 'custom:spotify-card'
      account:  which account to use for spotcast. Defaults to "default"
      height: 
      limit: 
      device: 
      playlist_type:  Change type of playlists shown. Default are your normal playlists.
      always_play_random_song:  Set to start playlists from a random song.
      country_code: 
      hide_warning:  Hide warnings if they are displayed.
      name:  Custom title. Leave empty to hide.
      display_style:  Change default display style.
      grid_covers_per_row:  Number of covers per row (default 3) in Grid-view.
      spotify_entity:  Name of your spotify media player entity if it doesn't start with "spotify"
      default_device:  Name of your spotify connect or chromecast device, e.g. "Kitchen"
      filter_devices:  Hides devices which matches any array entry. The entries have to be regular expressions and are matched against the full device-name. The following are examples
        - .*room 
        - bath.*,kids.* 

Screenshots

General usage

This library can of course also be used on other websites or projects other than Home Assistant

CONTRIBUTING

Please contribute and help. Before creating a large PR make sure to sync about it with me.

License

This library is licensed under Apache 2.0, see LICENSE

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.