Releases: 19EB/spicetify-websocket-client
Release list
1.1.0
Run without Spicetify
This release adds a standalone way to run the websocket client. A small host program
starts Spotify with its remote debugging port enabled, injects the client, and prints
Spotify's log output to a terminal window. Spicetify is not involved and no Spotify
files are modified, so there is nothing to re-apply after a Spotify update.
The Spicetify extension is unchanged and still works exactly as before. Both use the
same websocket API, so existing integrations need no changes.
Getting started
- Download the archive for your platform below and unzip it.
- Open
websocket-client.iniand set the address, port and endpoint of your
websocket server. - Run
start.cmdon Windows, orspotify-ws-hoston macOS and Linux.
Spotify installed from spotify.com is required. The Microsoft Store version is
sandboxed and will not accept the launch flag the host needs. Nothing else has to be
installed, the host is a single self-contained executable.
On first run the host closes and reopens Spotify. Spotify only accepts the remote
debugging flag when it launches and allows one instance at a time, so playback stops
for a few seconds. Set restart = false under [spotify] if you would rather it stop
with an error than restart Spotify for you.
Also in this release
- Automatic reconnect, in both the Spicetify extension and the standalone build.
If the websocket server goes away, for example when Streamer.bot restarts, the client
retries on its own with an increasing delay, up to 30 seconds between attempts, and
resends the initial player state once reconnected. Configurable with the new
Reconnect automatically,Reconnect delayandMax reconnect delaysettings. - Requesting the current track or player state while nothing is playing now returns a
proper error response instead of failing silently. - The extension no longer fails to load entirely if Spotify's internal APIs cannot be
resolved. The settings page and the play bar button still appear.
Notes
- While the host runs, Spotify listens on a local debug port,
127.0.0.1:9223by
default. It is not reachable from other machines, but any program on your computer
could use it to control Spotify. Change it withdebugPort, or close the terminal
window when you are done. - Your existing extension settings are preserved. The new reconnect settings take
their defaults.
Checksums for the archives are in SHA256SUMS.txt below.