Replies: 9 comments 10 replies
|
Use the touchSupportDisabled card option. You should set this option to true if you have issues while trying to click on a media browser content tile and nothing happens. This will disable the addition of @touchstart and @touchend even handlers, even if touchscreen events are supported. It will force the addition of @click, @mousedown, and @mouseup event handlers to be added instead. These events are utilized to enable the "click and hold" / "tap and hold" / "long-press" functionality of media browser content tile items. It can also be set via the card editor ui: |
|
When you mentioned touchsupport, I realized I am actually staring at a Surface Book, so I simply touched the item and it works. Doh 'Cause I have more devices without touch than with touch, so I guess if I have to decide between those two modes, I'll have to go without touch. |
|
@ovizii |
|
@thlucas1 - This player looks extremely promising. After some trial and error with oauth credentials, I believe I have downloaded and installed into HA. I see the integration within HA but can't do much more. I restarted HA and I don't see the SpotifyPlus card as an available option. I do have the standard Spotify integration also in place however that is using a different clientID and secret key. |
|
@justinstauffer601 What kind of speakers / devices are you going to control with it? I ask, as there is some extra SpotifyPlus Integration setup for Sonos and Chromecast devices. More info on that configuration can be found in the wiki docs. Hope it helps! |
|
I think you might be talking about the Spotify Card in your post. SpotifyPlus Card is different. https://github.com/thlucas1/spotifyplus_card/wiki/Configuration-Options#card-picker |
|
@justinstauffer601 I asked asbout the The SpotifyPlus Card is configured mostly thru the card configuration editor, with some aspects being on the file system (images, some types of user presets, etc). SpotifyPlus Card configuration will look like this: Based on your HACS Custom Repositories screenshot above, you do have the SpotifyPlus Card installed. To create a card, just edit your dashboard of choice and select the the |
|
Sorry, forgot to tell you how to turn it on ... Just click the blue power button in the player section of the card: Or you can use the standard I also forgot to mention the polling scan interval ... You can adjust the SpotifyPlus Integration Spotify Polling Scan Interval configuration option. Note that the HA Spotify uses a scan interval of 30 seconds (same as SpotifyPlus default interval). This option specifies the polling scan interval (in seconds) used to query Spotify Player playstate. Value entered must be in the range of 4 to 60 (seconds). If not specified, the polling interval is set to 30 seconds. It is highly recommended that you use the default value (e.g. 30 seconds) for this option; use a lower value (e.g. 5 seconds) if you control the Spotify Player from another application besides Home Assistant (e.g. Spotify Mobile) and want Home Assistant to recognize Spotify Player state changes faster. A higher value equates to slower detection of Spotify player updates made outside of Home Assistant, but also decreases network bandwidth. As an example, let's say you set the value to 30 seconds (same as HA Spotify integration). This would generate 2,880 requests per day to the Spotify Web API for player updates (e.g. 2 requests per minute; 120 requests per hour; 2,880 requests per day). A lower value equates to faster detection of Spotify player updates made outside of Home Assistant, but also increases network bandwidth. It could also get you rate-limited by Spotify, depending on how much other data you are retrieving via the Spotify Web API. As an example, let's say you set the polling scan interval to 5 seconds. This would generate 17,280 requests per day to the Spotify Web API for player updates (e.g. 12 requests per minute; 720 requests per hour; 17,280 requests per day). |
|
Thanks again! I'll review when I am back at my desk. I sincerely appreciate the level of detail you have put into your responses too!
…________________________________
From: T Lucas ***@***.***>
Sent: Friday, May 23, 2025 3:29:12 PM
To: thlucas1/spotifyplus_card ***@***.***>
Cc: justinstauffer601 ***@***.***>; Mention ***@***.***>
Subject: Re: [thlucas1/spotifyplus_card] Need some help debugging (Discussion #60)
Sorry, forgot to tell you how to turn it on ... Just click the blue power button in the player section of the card:
image.png (view on web)<https://github.com/user-attachments/assets/c81fd9a6-d29f-460e-b212-492e292da654>
Or you can use the standard media_player.turn_on service call in scripts / automations if you like:
action: media_player.turn_on
data: {}
target:
entity_id: media_player.spotifyplus_todd_l
I also forgot to mention the polling scan interval ... You can adjust the SpotifyPlus Integration Spotify Polling Scan Interval<https://github.com/thlucas1/homeassistantcomponent_spotifyplus/wiki/Device-Configuration-Options#spotify-polling-scan-interval> configuration option. Note that the HA Spotify uses a scan interval of 30 seconds (same as SpotifyPlus default interval).
This option specifies the polling scan interval (in seconds) used to query Spotify Player playstate. Value entered must be in the range of 4 to 60 (seconds). If not specified, the polling interval is set to 30 seconds. It is highly recommended that you use the default value (e.g. 30 seconds) for this option; use a lower value (e.g. 5 seconds) if you control the Spotify Player from another application besides Home Assistant (e.g. Spotify Mobile) and want Home Assistant to recognize Spotify Player state changes faster.
A higher value equates to slower detection of Spotify player updates made outside of Home Assistant, but also decreases network bandwidth. As an example, let's say you set the value to 30 seconds (same as HA Spotify integration). This would generate 2,880 requests per day to the Spotify Web API for player updates (e.g. 2 requests per minute; 120 requests per hour; 2,880 requests per day).
A lower value equates to faster detection of Spotify player updates made outside of Home Assistant, but also increases network bandwidth. It could also get you rate-limited by Spotify<https://developer.spotify.com/documentation/web-api/concepts/rate-limits>, depending on how much other data you are retrieving via the Spotify Web API. As an example, let's say you set the polling scan interval to 5 seconds. This would generate 17,280 requests per day to the Spotify Web API for player updates (e.g. 12 requests per minute; 720 requests per hour; 17,280 requests per day).
—
Reply to this email directly, view it on GitHub<#60 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BH6QA4PGV6FVSMJ355YYON3275ZIRAVCNFSM6AAAAAB3XAJPQOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMRVGA2DMMI>.
You are receiving this because you were mentioned.
|











Uh oh!
There was an error while loading. Please reload this page.
Most of the time, I start playback on my phone via the spotify app and just use the play/pause buttons of the card, so I didn't realize that some short or long time ago, something broke on my side and the card does only allow me to use the player controls, but I cannot click or click-hold anything else.
Say I search for an artist, I get the results but clicking on them does nothing.
I'm pretty sure this is a “me-problem” so I'd appreciate any pointers.
All reactions