@marccie appreciate it but that’s ok - I’m a tea guy anyway 
The gesture is more than enough for me, I enjoy doing this! In case you need any help with a website, domain or e-mail I’d happy to assist you with my company https://pendo.nl. Cheers! 
New release has just been approved (v1.3.1) compared to the latest version in the app store, these features can be used now:
- v1.3.1 2025/12/14
Added an “Add to queue” flow chart that adds a song to the active queue rather than instantly playing it (like the play card does)
- v1.3.0 2025/12/14
Adds a currently playing flow card that returns tokens with the current album, artist, trackname, total length (secs), progress (secs), progress (percentage) and an isPlaying boolean
- v1.2.0 2025/12/14
Adds a widget that allows you to search songs, artists, playlists and albums and start playback instantly (by pushing the song to the top of the queue)
- v1.1.0 2025/12/14
Adds flowcharts to start playback of a selected song, artist, album or user playlist.
1 Like
TL;DR
I’m trying to get this to work: “Play song […] on speaker [Spotify Connect Speaker]” and if that failed due to a “Device not found” error I want to activate a “Wakeup [Spotify Connect Speaker] via LAN” card that loops back to playing the song after awaking the device.
So far I have had a good result on waking up a Librespot (Raspberry pi Spotify Connect speaker) but haven’t been able to switch playback to that device after.
Long version:
So I’ve been testing a way to wake up a Spotify Connect device inspired by the HomeAssistant plugin and Librespot (software to turn a Raspberry Pi into a Spotify Connect device). I’m not fully aware of what happens exactly but so far I managed to follow what Claude (AI) told me.
Right now I have an option to discover local Spotify Connect devices on my network. It finds my laptop, my Sonos (still unsupported via the API), my Librespot speaker and my phone. Claude also setup javascript code to reverse engineer the network handshake that happens when Spotify wakes up a device and that works with the Librespot speaker but not yet with my laptop client. And while it says it woke up the Librespot speaker I cannot get it to play yet, not via the Homey app nor via the Spotify client itself.
I get the idea that there is a working solution in this method and it’s slowly progression with tiny steps each time.
Yesterday I had good success with porting the HomeAssistant Danfoss plug-in and I’m trying to get Claude to use that plug-in as basis for Homey now. It seems that trying to dismantle the exact handshake/technique from just Librespot isn’t working and Claude has to guess to many things.
I’ll keep you updated on this.
Enough for today and probably for the next few days too unfortunately.
I have a semi-working example with my Librespot device where the “Play song” card does an underwater check if the device is available. If not it tries to activate it and if that fails it tries to awake it. The activation works, but that’s kind of expected since that means the device is listed under my active devices.
Awaking it works… a bit? I’ve had it happen a few times that the device was connected to my friends phone (another spotify account) and running the code would in fact take over the speaker and disconnect her phone. I even noticed the song changing but playback didn’t start yet. None of the follow up tests worked, but it turns out that my Librespot speaked has a dynamic port to be discovered on. Right now I have device settings where the host+port can be set for a device but I need discovery and activation based of the mDNS data to bypass dynamic ports.
At least I’m still at a point where I believe Claude and I can get this to work!
1 Like
Sorry, I have to interrupt here.
I installed the official Spotify app for Homey and also Spotify Connect. I have my credentials and can log in.
I use DENON HEOS speakers and they are integrated by the DENON HEOS app for homey. But sadly I can’t control any of these speakers.
I installed everything and then I try to add a new device. Sadly I can find just one of my 5 speakers. OK, I add this one to test everything!
I can see a new device everywhere and yes, I can add a flow for this device.
But how can I add more devices and why I can add just this specific one speaker? I can’t see other speakers at all.
Thanks a lot!
So if I understand correctly you do see 1 out of 5 speakers? And that one speaker is identical to the other 4? Just to make sure there is no brand our type difference.
Yes, I see one out of 5 speakers.
- The first one is called “bath”
- The second “office”
- The third one “living room”
- number 4 “Maya” - the name of one child
- number 5 “Sleeping Room”
After installing everything I just see the speaker “office” - The German word is “Büro” as indicated by the following screenshot. OK, now I see also my “iPhone” but this will not appear when I try to do everything on my PC with the web version of Homey!
Shouldn’t I see all speakers? Or is this the point where I should by a HomePod?
And yes, all devices are DENON HEOS speaker. Most of the Home 150 and two devices are Home 250. All of them are in the HEOS app for Homey!
My guess is that the speaker in your office has been the latest active speaker in your account. Try switching playback (via the app) to any of the other 4 speakers en try connecting a few seconds after.
This is a limitation in the spotify API - we can only discover active devices. So you’d have to activate them and then add them to your system.
And then there’s the next issue: once it goes inactive there is no option yet to awake the device via cards and start playback. Only when you activate it manually you can use the Homey apps.
I’m currently exploring options based on the HomeAssistant’s SpotifyPlus app to see if I can awake devices and get them listed back under your accounts active devices. But no success yet.
1 Like
Thanks, I’ll try that. Would it be an option to configure the speakers so they don’t switch to energy-saving mode, or is that irrelevant since – due to Spotify’s limitations – you can only ever control the last active speaker?
OK, I added the speaker in the office again and yes, I found it. Sadly I see a red exclamation mark now. Does this indicate that the speaker is offline or in power-saving mode?
EDIT:
I did exactly as you suggested. I controlled a different speaker in the Spotify app. I was then able to add it to Spotify Connect. As soon as it was added, the speaker in the office went offline again – indicated by the red exclamation mark.
Consequently, only the last speaker that was active can be active at any given time. This means that if I create a Flow that, for example, plays a song in the living room every morning at 8 a.m., the Flow won’t work if another speaker in the house has been active in the meantime. Have I understood this correctly?
For now, unfortunately, yes. I’ve had best success with a separate Spotify account but I can totally understand that’s not what we want. And even then I would sometimes connect my main account and made the speaker unavailable to Homey.
I hope my quest on getting the awake/activate method working - but I’m heavily relying on my AI coding partner for explanation and solutions as I’m getting a bit out of my comfort zone. As said, there’s been a few small success so far and it’s definitely heading in the right direction but I have absolutely no clue how far from the actual solution I am.
Thanks a lot for all you work and support! I appreciate this really.
What I know so far: if I buy a HomePod or HomePod Mini it’s possible to connect all speakers and also work with Siri to address them.
I’ve never seen it in action but that’s what I’ve read in several blogs and pages.
If HomePod can address these speakers (in my case Denon) there should be a solution, or? Otherwise a HomePod couldn’t also address an inactive speaker.
I don’t know how HomePod is doing this but maybe that’s a direction to check out how it works with a HomePod. Sadly I have none but maybe I can buy one and explain how it works with such a bridge. Would this help you?
The issue lies in the Spotify Connect API.
For starters not all brands are supported via the Spotify Connect API even while you can use Spotify on those speakers. Google and Sonos for example can’t be controlled using the Spotify Connect API.
And second there is the “active devices” part, these are speakers we can control via the API. And these are the devices recently used or the ones actively being controlled by your account. As far as I know after an hour of inactivity the devices disappears from the active devices list.
Getting them back in the active list requires awaking them (that’s essentially what you’re doing when selecting the speaker from within the app to start playback). That can’t be done via the API unfortunately, that requires searching the network for available speakers and sending an encrypted request to the speaker. If that is successful the speaker gets attached to your account and the API can see the device in the active list.
There are technical differences across many brands and the Homepod controller Denos probably means that the Homepod knows how to awake the speakers or it uses a different method then Spotify Connect (bluetooth, network, their own integration, etc.).
I think it’s a waste of money looking into other speakers as this integration is dependent on the Spotify Connect API and the issue is clear (devices get inactive) as well as the solution (awaking them via the network). So let’s hope AI or me can crack the last pieces anytime soon!
1 Like
I tried the configuration in the initial post, but I can’t add a new app in the Spotify Developer portal.
It looks like they are changing the authentication for it:
Are you aware of this change? It looks like Spotify is still working on it, since this is their last blog post: Reminder: OAuth Migration - 27 November 2025 | Spotify for Developers
I guess for now, I just have to wait and can’t connect Spotify Connect in Homey yet?
Hmm afraid so, I have multiple apps on there and can’t create a new one as well.
The Spotify gods sometimes are a pain … but it’s in their hands really.
Same here too, we can’t do more than wait. Meanwhile I’ll take a look if these changes affect this app and if they do see what I can do to prevent disruption before the changes are made effective at Spotify’s end.
1 Like
