Spotify integration not working. Bug if credentials are entered incorrectly the first time?
gbmhunter opened this issue · 8 comments
I am running Volumio on a RaspberryPi B+. I have entered my Spotify username and password correctly on the setting screen (this is after creating a "password" for 3rd party devices on spotify.com as I signed up to Spotify using Facebook, this could be something that is mentioned on the website!).
I have even updated the WebUI, first by using the WebUI update button (which didn't seem to work), and then by running webuiupdate.sh in /home/volumio/ through SSH (which did seem to work). This didn't fix the issue.
I have reset the device many times, and tried toggling the Spotify button on/off multple times also (as well as rebooting inbetween toggles).
Still no luck, there is no mention of Spotify if I click "Browse" (just "Web Radio").
Where and which log files should I be looking at to try and fix this bug?
Could it have something to do with this error I found in "/var/log/nginx/error.log"?
2014/12/28 21:17:39 [notice] 2405#0: start worker process 2406
2014/12/28 21:19:39 [error] 2406#0: *23 FastCGI sent in stderr: "PHP message: >>>>> cfgdb_update(cfg_engine,dbh,spotify,1) >>>>>
UPDATE cfg_engine SET value='1' where param='spotify'" while reading response header from upstream, client: 192.168.1.50, server: , request: "POST /settings.php HTTP
/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "volumio.local", referrer: "http://volumio.local/settings.php"
O.K., so the full error is here, I have masked out my actual username and password with myUsername and myPassword.
2014/12/28 21:43:09 [notice] 2396#0: start worker process 2398
2014/12/28 21:44:31 [error] 2398#0: *3 FastCGI sent in stderr: "PHP message: >>>
>> cfgdb_update(cfg_engine,dbh,spotusername,myUsername) >>>>>
UPDATE cfg_engine SET value='myUsername' where param='spotusername'
PHP message: >>>>> cfgdb_update(cfg_engine,dbh,spotpassword,myPassword) >>>>>
UPDATE cfg_engine SET value='myPassword' where param='spotpassword'
PHP message: >>>>> cfgdb_update(cfg_engine,dbh,spotify,1) >>>>>
UPDATE cfg_engine SET value='1' where param='spotify'" while reading response he
ader from upstream, client: 192.168.1.50, server: , request: "POST /settings.php
HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "volumio.local", referre
r: "http://volumio.local/settings.php"
O.K., so after a fresh install of Volumio, and entering in my username/password correctly the first time (I didn't do that last time) it now works. This could be a bug in where if you get your username and password incorrect the first time, you can't fix it?
Yes, that could be the issue. Thanks for reporting!
Date: Sun, 28 Dec 2014 14:10:55 -0800
From: notifications@github.com
To: Volumio-WebUI@noreply.github.com
Subject: Re: [Volumio-WebUI] Spotify integration not working. Added correct username and password, have reset multiple times. (#58)
O.K., so after a fresh install of Volumio, it now works. This could be a bug in where if you get your username and password incorrect the first time, you can't fix it?
—
Reply to this email directly or view it on GitHub.
=
I'm using Volumio 1.55 on the Raspberry Pi B. Added my Spotify details into the WebUI, and entered the password incorrectly. I edited the password a couple of times (to the correct password), restarting after each change. This didn't work.
I spotted the information over at:
https://volumio.org/forum/spotify-not-working-t2272.html
This mentioned the "/etc/spopd.conf" file. I noticed that the password was still the incorrect one from the first time I entered it.
I edited the file by SSH'ing onto the Pi (with "PuTTY") with the default Raspbian username/password (pi/raspberry) and using the following command:
sudo nano /etc/spopd.conf
Then I changed the password in the file to the correct one and saved the file: "Ctrl + X", "Y", Enter
Once I restarted the Pi again, the "Spotify" Section was available on the "Browse" tab
Hope that helps someone else ... :-)
DanStephens, thank you! That was my exact problem. Now up and running!
Michelangelo do you know if this was ever fixed?
I just installed a fresh version of Volumio and encountered the same bug -- so apparently, this has not been fixed yet.