Bramus
April 26, 2024, 11:53am
103
Have the same issue, did you find a solution?
myhades
May 12, 2024, 1:06pm
104
No i haven’t. xD
Can anyons help me?
Hello, i’m having issues, recently the add-on stopped working, it shows up in spotify but i can’t play anything on it. It will through an invalid token when i try to re-authorize spotify. Any idea on wha’ts happening?
Any one a fix or anything that is working?
out of curiosity are you on a Spotify Family plan too ?
Because i’ve found an article about an issue in owntown not beeing able to receive the token back from spotify family:
opened 07:13AM - 30 Jan 25 UTC
closed 06:51PM - 04 Feb 25 UTC
bug
version of owntone **28.11**
platform **Ubuntu 22.04.5 LTS**
docker container **… docker.io/owntone/owntone:latest**
Spotify Account **Premium Family**
I have a new install of Owntone that I have been having some weird problems with. I am experiencing the same issue with being able to authenticate, browse and search my Spotify account within Owntone, but am (mostly) unable to play anything. This appears to be very similar to this issue [[#1842](https://github.com/owntone/owntone-server/issues/1842)].
After much toubleshooting I seem to be able to replicate the problem and have discovered that Owntone works as expected with the Spotify being able to read, search and stream tracks as long as I have used my 'main' Spotify account. As mentioned above, I have a 'premium family' account and if I attempt to authenticate Spotify within Owntone on another (I tried on 2 different family member accounts) family account I can not stream any tracks, although I am able to see all the playlists from that specific account and use the Spotify search function within Owntone (but not stream any of the results). I have switched back and forth between my main account and other family member accounts and this is 100% reproducible.
In all cases once the Spotify account is authenticated in Owntone the username appears correctly in the "access granted" field of Owntone's web interface. Also the "Manage Apps" page of the individual Spotify account shows the 'owntone-server' app.
The error I receive on the Owntone web interface when I attempt to stream a song with a 'family' account is:
`Request failed (status: 500 Internal Server Error http://owntone.local:3689/api/queue/items/add?clear=true&playback=start&playback_from_position=0&shuffle=false&uris=library:playlist:15)
`
I would normally guess that this is a Spotify API issue and not an Owntone issue, but I am fairly certain that my previous install of Owntone on RaspbianOS was able to authenticate to Spotify with another family member's account and function properly. Unfortunately I do not still have the previous server with Owntone still functioning, but I think I may be able to revive it to confirm my suspicion.
On a side note, it seems the same family accounts with the above issue also have the issue of being unable to complete the authentication process without restarting Owntone. I am able to resolve owntone.local to my local owntone installation, but when I attempt to use one of the 'family' accounts to authenticate Spotify I receive an "Invalid Token" message on the Owntone Webpage after I press the "Authorize Web API Access" button. If I refresh the web page I then see a "Could not find access token in Spotify reply (see log)" message. If I then navigate back to the Owntone online-services page, I see the "Authorize Web API Access" button again. If at this point I restart the server and return to the online-services page the "Authorize Web API Access" button is gone and I can see the correct authorized user, but am unable to stream anything from Spotify. I do not experience any of this 'weirdness' when I use my main account.
Here is the log file from authenticating a 'family' account until the "Invalid Token" web page, and then from 06:49 is refreshing the browser and seeing the "Could not find access token in Spotify reply (see log)" message on the Owntone webpage.
I hope this is helpful, and if you'd like me to attempt to resurrect my previous server with Owntone (that I'm pretty sure didn't have this issue) please let me know.
Thanks again for all your time and work on this project.
```
OwnTone | [2025-01-30 06:47:01] [DEBUG] web: OAuth request '/oauth/spotify?code=x' in worker thread 346
OwnTone | [2025-01-30 06:47:01] [DEBUG] spotify: Received OAuth code: x
OwnTone | [2025-01-30 06:47:01] [DEBUG] http: Parameters in request are: grant_type=authorization_code&code=x&redirect_uri=http%3A%2F%2Fowntone.local%3A3689%2Foauth%2Fspotify
OwnTone | [2025-01-30 06:47:01] [ INFO] http: Making request for https://accounts.spotify.com/api/token
OwnTone | [2025-01-30 06:47:01] [DEBUG] spotify: Token reply: {"access_token":"x","token_type":"Bearer","expires_in":3600,"refresh_token":"x","scope":"playlist-read-private playlist-read-collaborative streaming user-library-read user-read-private"}
OwnTone | [2025-01-30 06:47:01] [DEBUG] db: Running query 'INSERT OR REPLACE INTO admin (key, value) VALUES ('spotify_refresh_token', 'x');'
OwnTone | [2025-01-30 06:47:01] [DEBUG] spotify: Making request to 'https://api.spotify.com/v1/me'
OwnTone | [2025-01-30 06:47:01] [ INFO] http: Making request for https://api.spotify.com/v1/me
OwnTone | [2025-01-30 06:47:01] [DEBUG] spotify: Got JSON response for request to 'https://api.spotify.com/v1/me'
OwnTone | [2025-01-30 06:47:01] [DEBUG] spotify: User 'heritagehouseinteriors', country 'CA'
OwnTone | [2025-01-30 06:47:01] [ LOG] web: Could not parse Spotify OAuth callback '/oauth/spotify?code=x': Invalid token
OwnTone | [2025-01-30 06:49:05] [DEBUG] web: OAuth request '/oauth/spotify?code=x' in worker thread 346
OwnTone | [2025-01-30 06:49:05] [DEBUG] spotify: Received OAuth code: x
OwnTone | [2025-01-30 06:49:05] [DEBUG] http: Parameters in request are: grant_type=authorization_code&code=x&redirect_uri=http%3A%2F%2Fowntone.local%3A3689%2Foauth%2Fspotify
OwnTone | [2025-01-30 06:49:05] [ INFO] http: Making request for https://accounts.spotify.com/api/token
OwnTone | [2025-01-30 06:49:05] [DEBUG] spotify: Token reply: {"error":"invalid_grant","error_description":"Invalid authorization code"}
OwnTone | [2025-01-30 06:49:05] [ LOG] spotify: Could not find access token in reply: {"error":"invalid_grant","error_description":"Invalid authorization code"}
OwnTone | [2025-01-30 06:49:05] [ LOG] web: Could not parse Spotify OAuth callback '/oauth/spotify?code=x': Could not find access token in Spotify reply (see log)
```
reexas
January 16, 2026, 5:31pm
110
Could you please update librespot? The current authorization methods with spotify don’t work anymore.
Xaphier
March 3, 2026, 6:26am
111
I can’t find the add-on anymore, the link to the add-on in first page is broken. Is the add-on brought down?
vin-w
June 30, 2026, 4:22pm
112
After HomePod Connect addon not working for a while, I found out about SpotConnect and SpotConnectDocker — it lets you use HomePods as Spotify Connect devices through AirPlay directly, with no dependency on OwnTone.
I've made a simple HAOS addon so you can install it straight from the Add-on Store:
Add this repo in HA: Settings → Add-ons → Add-on Store → ⋮ → Repositorieshttps://github.com/vin-w/hass-spotconnect-addons
Install SpotConnect, set mode to raop, and start it
Your HomePods will show up as Spotify Connect devices in the Spotify app
Happy to help if anyone runs into issues.
alexbabel
August 6, 2026, 9:33pm
113
Hi everyone!
It’s been a while since I made an update to my add-on. In the meantime, I’ve moved on to Music Assistant, and I can recommend it as a great alternative to my add-on!
I did find the time for a major update to this project, though: the Docker image is now built on the official OwnTone image and librespot (the Rust implementation), since neither linuxserver/daapd nor librespot-java is maintained anymore. I tested it on my local setup and it works as before. It is now live and can be installed as described in my initial post.
Happy spotifying again with HomePod Connect
DISCLAIMER: I used Claude to make this update possible. The code was reviewed by me and tested in my local setup.
