Spotify Plugin
 
Notifications
Clear all

Spotify Plugin

4 Posts
3 Users
0 Reactions
26 Views
0
Topic starter

Spotify connection not working with Stream Control 2.4.10

Hi,

I am having a problem connecting Spotify to Hercules Stream Control with my Hercules Stream 100.

My setup:

  • Hercules Stream 100

  • Stream Control 2.4.10

  • Windows 11 64-bit

  • Spotify for Windows 1.2.98.301.gfcaeba72

  • Spotify Premium Duo

I created a Spotify Developer application following the Hercules instructions and configured the Web API and the required local callback address.

When I click "Connect to Spotify":

  1. Spotify opens normally.

  2. I log in and authorize the application.

  3. Spotify successfully redirects back to Stream Control.

  4. The authorization code is present in the callback URL.

  5. However, Stream Control does not complete the connection.

  6. The Spotify icon does not change to the connected state.

  7. No refresh token is saved.

I have already tried a completely clean reinstall of Stream Control, including removing the previous Stream Control configuration and reinstalling version 2.4.10.

I also regenerated the Spotify application credentials and tested the connection again, with exactly the same result.

I have verified that the local callback is reachable and that Stream Control has Internet access.

Has anyone experienced this problem with Stream Control 2.4.10 and Spotify recently?

Could this be related to a recent Spotify OAuth change, or is there a known issue with the Spotify integration?

Thanks!


4 Answers
0

I found a link, so that means you need a subscription now for it to work—unless the Linux developer comes up with a trick to bypass it.

here Link on news 

https://www.it-boltwise.de/spotify-verschaerft-regeln-fuer-entwickler-premium-pflicht-und-neue-api-limits.html


0
Topic starter
I have a subscription, so I don't know what you mean :(

0

Did you follow this exact guide?
https://support.hercules.cn/en/kb/1845-en/


0

Hello @GreyFoxM4k3uCry 

Spotify connectivity has been affected by an update to their developer API.
We are planning an update very soon that will also resolve this issue. It is only a matter of days.

Sorry for the inconvenience.

Théo