Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Feature Request] Expose Spotify Connect devices
See original GitHub issueThank you for this component, it’s extremely useful!
It would be helpful to have an exposed sensor.spotify_connect_devices entity, much like sensor.chromecast_devices.
Having the ability to fetch this list, including each device’s Spotify unique ID would be useful.
My goal: to be able to fetch a combined list of all devices (Connect and Chromecast) with their Spotify unique IDs, and feed that back as data: spotify_unique_id: [] to an action call service.spotcast.
Thank you
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’ve gone back and tried again with device names, and managed to get it working no trouble.
It seems the Spotify device ID (the numbers referenced in my Reddit post and here) only work if they’re one of the last 3 devices used by Spotify. It must use the same developer API referenced in my post.
Device names on the other hand seem to work (so far) as long as Spotify can see them on the network. Mine drop in and out sometimes.
Not sure why the names didn’t work before but it seems a better method (so far anyway).
Thanks for this, it was pretty cool before with just my Chromecasts, but now I can cast Spotify anywhere with a Lovelace button or automation.
Closing this as it works as wxpected