ANNOUNCEMENT: Pi Musicbox v0.7.0RC5


#1

I don’t know where the last few months went but please find the latest version at https://github.com/pimusicbox/pimusicbox/releases/tag/v0.7.0RC5

The two headline changes are:

  • Firewall is now optional and is DISABLED by default
  • Added Spotify Connect functionality

Please provide any feedback, particularly any problems using Spotify Connect. I’ve had a report that it doesn’t work if the firewall is enabled so be wary of that; if anyone wants to help fix this then there’s a good example of what to do here.


#2

#3

Hi,

I just installed the new version of Pi MusicBox.
I’ve been using it happily for some time now, mainly with bubbleupnp.

I was exited when I saw that it finally supports Spotify connect.
I had to reboot my Pi3 several times, enabling and disabling the Spotify connect option. It dit not work right away, the musicbox showed up in the Spotify app, I tried to connect. It said “connecting” however I was not able to play any music. After some time the musicbox simply disappeared from the list…
Now it is working like a charm. Hope this will stay that way :slight_smile:

So thanks a lot for the good work!
All the best
Paul


#4

Greetings! Upgraded from v.0.7.0RC3 to v 0.7.0RC5. I am having an issue with the stream audio stopping. Looking at the MusicBox gui it shows the station streaming. I am using a PI 3 hard wired. It is my understanding the 7.orc5 has the auto reconnect. With that said we have another 7.0RC3 Pi 2 that never misses a beat.

I operate an Internet Radio Station and use the MusicBox for monitoring and love the ease of the software. Would appreciate any ideas here!

Best wishes…


#5

The auto reconnect (mpd-watchdog) should only really come into play if the stream stops, which you say yours isn’t doing. There is very little difference between those two versions in that department. Could you look at the log in /var/log/mopidy/mopidy.log?


#6

I’m having similar issues as Keith_Angstadt.
Some streams play sound, others don’t although the station information is displayed on the gui.
I’ve tried the Dutch radio station 3FM, which is part of the pre-installed playlist
That link doesn’t play sound in v0.7rc5. The link worked great with Musicbox v0.6, like it does with any other program

Copied from mopidy.log:

2017-09-16 19:54:31,764 - WARNING Download of ‘http://icecast.omroep.nl/3fm-bb-mp3’ failed: HTTPConnectionPool(host=‘icecast.omroep.nl’, port=80): Max retries exceeded with url: /3fm-bb-mp3 (Caused by NewConnectionError(’<urllib3.connection.HTTPConnection object at 0x3343c30>: Failed to establish a new connection: [Errno -2] Name or service not known’,))

Thanks for digging in to it.
Regards,


#7

Hi kingosticks ! :slight_smile:

A BIG THANKS YOU FOR YOUR WORK ! :smile:

I had a MusicBox 0.6 for 2 years. I even build a case for it : https://www.thingiverse.com/thing:2587032
I use the AUDIOPHONICS DAC Sabre ES9023 (working with “Hifiberry_DAC” option).

And now ? SPOTIFY CONNECT ? Wow !!!

My Pi Musicbox v0.7.0RC5 works like a charm !

I tested :

  • MPDClient : “MPDroid” : Ok, “M.A.L.P.” : Ok
  • HttpClient : “Remotedy” : Ok
  • Spotify connect : My account : Ok !!! Another account on same wifi : Ok !!!
  • Defaut web client : Ok as always
  • Mopify web client : So fucking ok !
  • UPnP/DLNA : “BubbleUPnP” : Ok

I just have a problem with Spotify Connect sound volume…
EDIT : Solved : Pi Musicbox volume control (for Amp hat) not working with Spotify Connect

So thanks you again !
Clément.


#8

I’m a little late but thank you for this latest update. Spotify Connect is working nicely!


#9

Hi kingosticks !

After a week with v0.7.0RC5 a have some issues :

  • Sometimes, “Spotify Connect” disappear and I must reboot the Pi to get it back. (Seems DLNA/AirPlay disappear at the same time)
  • HTTP / MPD client seems to be slower than the 0.6 version.

Don’t hesitate to ask if you want some logs or anything.

Waiting for a correction, is there a way to just restart Spotify Connect plugin ?

Clément.


#10

There is currently no way to restart just Spotify Connect from the web interface. You can do it from the command line by running

/opt/librespot/librespot -n <server_name> <spotify_username> <spotify_password> 320 --onstart "/usr/bin/mpc stop" &

I can’t think why the clients, particularly the MPD client, would be any slower.

Can you log into the system once Spotify Connect disappears and see if the other services are still running?

service shairport-sync status
service upmpdcli status

Maybe the monit log at /var/log/monit.log might be interesting.


#11

Hi,

When my Spotify Connect disappear, this is what i have :

root@MusicBox:~# service shairport-sync status
[ ok ] shairport-sync is running.
root@MusicBox:~# service upmpdcli status
[FAIL] upmpdcli is not running ... failed!
root@MusicBox:~# cat /var/log/monit.log
[BST Jul 27 23:43:14] info     : Starting monit daemon
[BST Jul 27 23:43:14] info     : Monit start delay set -- pause for 300s
[GMT Jan  7 03:56:14] info     : monit daemon with pid [2376] killed
[GMT Jan  7 03:56:14] info     : 'system_MusicBox' Monit stopped
[BST Oct 17 14:24:05] info     : Starting monit daemon
[BST Oct 17 14:24:05] info     : Monit start delay set -- pause for 300s
[BST Oct 17 14:28:33] info     : monit daemon with pid [2946] killed
[BST Oct 17 14:28:33] info     : 'system_MusicBox' Monit stopped
[GMT Jan  7 03:56:44] info     : Starting monit daemon
[GMT Jan  7 03:56:44] info     : Monit start delay set -- pause for 300s
[BST Jul 28 00:08:30] info     : monit daemon with pid [2411] killed
[BST Jul 28 00:08:30] info     : 'system_MusicBox' Monit stopped
[GMT Jan  7 03:56:41] info     : Starting monit daemon
[GMT Jan  7 03:56:41] info     : Monit start delay set -- pause for 300s
[BST Jul 28 00:18:50] info     : monit daemon with pid [2428] killed
[BST Jul 28 00:18:50] info     : 'system_MusicBox' Monit stopped
[GMT Jan  7 03:56:41] info     : Starting monit daemon
[GMT Jan  7 03:56:41] info     : Monit start delay set -- pause for 300s
[BST Jul 28 00:35:16] info     : monit daemon with pid [2329] killed
[BST Jul 28 00:35:16] info     : 'system_MusicBox' Monit stopped
[GMT Jan  7 03:56:41] info     : Starting monit daemon
[GMT Jan  7 03:56:41] info     : Monit start delay set -- pause for 300s
[BST Jul 28 00:54:16] info     : monit daemon with pid [2328] killed
[BST Jul 28 00:54:16] info     : 'system_MusicBox' Monit stopped
[BST Oct 17 14:59:08] info     : Starting monit daemon
[BST Oct 17 14:59:08] info     : Monit start delay set -- pause for 300s
[BST Oct 17 15:04:08] info     : 'system_MusicBox' Monit started
[BST Oct 17 15:06:15] error    : 'mopidy' failed protocol test [HTTP] at INET[localhost:6680] via TCP -- HTTP: Error receiving data -- Resource temporarily unavailable

[BST Oct 17 15:08:20] error    : 'mopidy' failed protocol test [HTTP] at INET[localhost:6680] via TCP -- HTTP: Error receiving data -- Resource temporarily unavailable

[BST Oct 17 15:08:20] info     : 'mopidy' trying to restart
[BST Oct 17 15:08:20] info     : 'mopidy' stop: /etc/init.d/mopidy
[BST Oct 17 15:08:50] info     : 'mopidy' start: /etc/init.d/mopidy
[BST Oct 17 15:10:51] info     : 'mopidy' connection succeeded to INET[localhost:6680] via TCP
[BST Oct 17 15:34:11] info     : monit daemon with pid [2527] killed
[BST Oct 17 15:34:11] info     : 'system_MusicBox' Monit stopped
[GMT Jan  7 03:56:41] info     : Starting monit daemon
[GMT Jan  7 03:56:41] info     : Monit start delay set -- pause for 300s
[BST Oct 17 16:25:10] info     : monit daemon with pid [2334] killed
[BST Oct 17 16:25:10] info     : 'system_MusicBox' Monit stopped
[GMT Jan  7 03:56:41] info     : Starting monit daemon
[GMT Jan  7 03:56:41] info     : Monit start delay set -- pause for 300s
[BST Jul 28 05:28:38] info     : monit daemon with pid [2390] killed
[BST Jul 28 05:28:38] info     : 'system_MusicBox' Monit stopped
[GMT Jan  7 03:56:41] info     : Starting monit daemon
[GMT Jan  7 03:56:41] info     : Monit start delay set -- pause for 300s
[BST Jul 28 07:12:41] info     : monit daemon with pid [2393] killed
[BST Jul 28 07:12:41] info     : 'system_MusicBox' Monit stopped
[GMT Jan  7 03:56:41] info     : Starting monit daemon
[GMT Jan  7 03:56:41] info     : Monit start delay set -- pause for 300s
[BST Jul 28 07:27:30] info     : monit daemon with pid [2397] killed
[BST Jul 28 07:27:30] info     : 'system_MusicBox' Monit stopped
[GMT Jan  7 03:56:41] info     : Starting monit daemon
[GMT Jan  7 03:56:41] info     : Monit start delay set -- pause for 300s
[BST Jul 28 07:45:57] info     : monit daemon with pid [2387] killed
[BST Jul 28 07:45:57] info     : 'system_MusicBox' Monit stopped
[GMT Jan  7 03:56:41] info     : Starting monit daemon
[GMT Jan  7 03:56:41] info     : Monit start delay set -- pause for 300s
[BST Oct 23 09:11:25] info     : monit daemon with pid [2394] killed
[BST Oct 23 09:11:25] info     : 'system_MusicBox' Monit stopped
[GMT Jan  7 03:56:41] info     : Starting monit daemon
[GMT Jan  7 03:56:41] info     : Monit start delay set -- pause for 300s
[BST Aug  9 11:00:03] info     : monit daemon with pid [2399] killed
[BST Aug  9 11:00:03] info     : 'system_MusicBox' Monit stopped
[GMT Jan  7 03:56:41] info     : Starting monit daemon
[GMT Jan  7 03:56:41] info     : Monit start delay set -- pause for 300s
[BST Aug 10 13:22:59] info     : monit daemon with pid [2395] killed
[BST Aug 10 13:22:59] info     : 'system_MusicBox' Monit stopped
[GMT Jan  7 03:56:41] info     : Starting monit daemon
[GMT Jan  7 03:56:41] info     : Monit start delay set -- pause for 300s
[BST Oct 25 07:59:36] info     : monit daemon with pid [2405] killed
[BST Oct 25 07:59:36] info     : 'system_MusicBox' Monit stopped
[GMT Jan  7 03:56:41] info     : Starting monit daemon
[GMT Jan  7 03:56:41] info     : Monit start delay set -- pause for 300s
[BST Aug 12 11:16:32] info     : monit daemon with pid [2394] killed
[BST Aug 12 11:16:32] info     : 'system_MusicBox' Monit stopped
[GMT Jan  7 03:56:41] info     : Starting monit daemon
[GMT Jan  7 03:56:41] info     : Monit start delay set -- pause for 300s
[BST Aug 12 13:05:20] info     : monit daemon with pid [2401] killed
[BST Aug 12 13:05:20] info     : 'system_MusicBox' Monit stopped
[BST Oct 25 09:49:35] info     : Starting monit daemon
[BST Oct 25 09:49:35] info     : Monit start delay set -- pause for 300s
[BST Oct 25 09:54:35] info     : 'system_MusicBox' Monit started
[GMT Oct 29 21:10:40] info     : monit daemon with pid [2596] killed
[GMT Oct 29 21:10:40] info     : 'system_MusicBox' Monit stopped
[GMT Jan  7 03:56:41] info     : Starting monit daemon
[GMT Jan  7 03:56:41] info     : Monit start delay set -- pause for 300s
root@MusicBox:~#

And indeed, if I use the following command, Spotify Connect show up and work perfectly.

/opt/librespot/librespot -n <server_name> <spotify_username> <spotify_password> 320 --onstart "/usr/bin/mpc stop" &

It seems that append only if I use Spotify (MPD version) a lot.

Remark :

Is better to use this command with nohup otherwise Spotify Connect log into console :
nohup /opt/librespot/librespot -n <server_name> <spotify_username> <spotify_password> 320 --onstart "/usr/bin/mpc stop" &

Other question, have this command an option to set the sound volume ? To start it at 50% for instance.


#12

The airplay service is clearly still running so really should still be available. The UPnP/DLNA service isn’t but it wasn’t killed by monit, which is odd as that’s usually very robust.

No.


#13

Is there a link between UPnP/DLNA service and Spotify Connect service ?

By the way, I have no Apple product so I can’t tell you if AirPlay is working or not.


#14

No link at all.

You said in your earlier post

But I guess you actually meant to say that just DLNA disappears at the same time. So my next question, is it actually the same time or would it be more accurate to say that Spotify Connect becomes unavailable and then when you check DLNA you find that is suddenly also unavailable, or that DLNA is unavailable but it might have happened at some other earlier time and is entirely unrelated?


#15

Exactly, I wrote “DLNA/AirPlay” but I wanted to say “DLNA/UPnP”, sorry.

Exaclty again ! :blush:
Actually it happend once every few days so It’s not easy for me to clarify it.

By the way, I wrote that “HTTP / MPD client seems to be slower than the 0.6 version.” but now I think that is false. Only related to the client I use.


#16

Hi, me again,

I finaly have a performance issue. After a moment, my PiMusicBox become very slow, and when I do a “top”, I have this :

If you need more log, don’t hesitate to tell me !


#17

I guess it would be somewhat helpful to know the exact actions you take to get in this state so that I might reproduce it. Else I have no idea where to start.


#18

I will try to find it out but for now I only use Spotify (Connect and MPD).


#19

My pimusicbox running on a raspi 1 model B is very slow on startup.

I found out this is caused by loading my spotify playlists. (I have a larger number of Spotify playlists). The pimusicbox is always loading a small number of playlist entries, after that the web intercafe shows “Loading data from Musicbox…”, until the next few playlists are loaded. This happens many times. The whole loading process takes more than 20 minutes and during this time my musicbox is very very slow and nearly unusable.

Is there a way to prevent Mopidy from loading all the spotify playlists on startup? I don’t need them because “Spotify Connect” is running fine for me.


#20

so disable the spotify plugin.