Finally put everything together, but could not get spotifyd to connect at all — editing the beocreate-installer with the latest spotifyd build made it work. The one in the script was from January(!).
Date
Votes
10 comments
-
HiFiBerry team Hi,
we're already in the process of preparing a new version. I hope it will be avilable within about a week.
Best regards,
Daniel -
6515cg After a fresh installation with the latest image of beocreate-20180703.zip there is still no Spotify Connect possible although the menu installation grey option looks like it's installed. So it's only Bluetooth or Airplay. It's fine for me but why is it offered while it's not working?
-
HiFiBerry team Hi,
it is working here. Not sure what's wrong in your setup. Can you login and check if Spotifyd is running?
Best regards,
Daniel -
6515cg Hello, it seems that Spotify is running and in Spotify the icon of the Beo CX50 is showing as Spotify Connect. Choosing it shows 'connecting...' and then after some seconds it fails and only Airplay & Bluetooth is possible.
The command systemctl status spotify.service shows:
● spotify.service - Spotify Connect
Loaded: loaded (/lib/systemd/system/spotify.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2018-07-17 10:17:50 UTC; 3min 2s ago
Main PID: 802 (spotifyd)
CGroup: /system.slice/spotify.service
└─802 /opt/spotifyd/spotifyd -c /etc/spotifyd.conf --no-daemonJul 17 10:17:50 beo-cx50 systemd[1]: Started Spotify Connect.
Jul 17 10:17:50 beo-cx50 spotifyd[802]: 10:17:50 [INFO] Using alsa volume controller. -
6515cg Did a second (wired) installation and it seems to work now. The first attempt was with WIFI. I think because of connection loss, the installation was not completed. Thanks.
-
6515cg But this second attempt worked for one day. After playing some Spotify numbers with Spotify Connect, it suddenly stops.
Now no Bluetooth, Airplay or Spotify Connect. Restarting the Beo has no results. I don't know what I'm doing wrong but it's not very stable.
The command systemctl status spotify.service shows:
● spotify.service - Spotify Connect
Loaded: loaded (/lib/systemd/system/spotify.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2018-07-18 12:53:53 UTC; 5min ago
Main PID: 527 (spotifyd)
CGroup: /system.slice/spotify.service
└─527 /opt/spotifyd/spotifyd -c /etc/spotifyd.conf --no-daemonJul 18 12:53:53 bocx50 systemd[1]: Started Spotify Connect.
Jul 18 12:53:57 bocx50 spotifyd[527]: 12:53:57 [INFO] Couldn't read configuration file, continuing with default confi
Jul 18 12:53:57 bocx50 spotifyd[527]: 12:53:57 [INFO] Using software volume controller.
Jul 18 12:53:57 bocx50 spotifyd[527]: 12:53:57 [INFO] No backend specified, defaulting to: alsa. -
HiFiBerry team That's strange. Airplay and BT Audio were working before?
Best regards,
Daniel -
6515cg Yes, only SSH was available.
Just did a third installation on a new SD cart. All source services are running now.
-
HiFiBerry team Maybe it was an defective SD card. We've seen all kinds of strange behaviour with corrupted SD cards. Often they do not just fail, but the system behaves strangely.
Best regards,
Daniel -
Louis Perez Hello,
Sharing my own experience on Spotifyd:
I tried several time to re-install drom source as described in some of this forum's posts but still the spotify connectivity was not working.
Then I downloaded the beocreate-tools repository from Hifiberry's Github and I ron the install-spotify script. Spotify is now working fine.
Louis
Please sign in to leave a comment.