Start with the documentation at misiektoja.github.io/spotify_monitor. Installation, Setup & First Run and Configuration cover most first-run problems, and Troubleshooting covers the rest.
The tool diagnoses itself. Run it before asking anything, and include its output when you do:
spotify_monitor --doctorIt checks the environment, configuration, credentials, notifications and connectivity, and names the reason for anything invalid.
An expired sp_dc cookie is the most common cause of sudden authentication failures, empty friend activity or a tool that worked yesterday and stopped today. Setup & First Run explains how to refresh it.
| You want to | Go to |
|---|---|
| Ask a question or discuss an idea | Discussions |
| Report something broken | Bug report |
| Request a capability | Feature request |
| Report a vulnerability | Private security advisory, never a public issue |
| Contribute a change | CONTRIBUTING.md |
Include the version, how you installed it (PyPI, manual script or Docker), your operating system, which authentication method you use and the --doctor output. Run the failing command with --debug and attach the relevant part of the log.
Never post your sp_dc cookie, SP_APP_CLIENT_ID or SP_APP_CLIENT_SECRET, SMTP passwords, webhook URLs, Last.fm API keys or a complete configuration file. Redact monitored usernames if they matter to you. See SECURITY.md.
This is a project maintained in spare time, so replies are best effort with no response time attached. Only the latest release receives fixes, as SECURITY.md describes, so reproduce the problem on the current version before reporting it.
If the project is useful to you, you can support its development through GitHub Sponsors or Buy Me a Coffee.