I am using Moode 3.84 and tried today to get Spotify working, by doing
curl -sL https://dtcooper.github.io/raspotify/install.sh | sh
The script seemed to run correctly and I do see a new entry in my list of devices in the Spotify application on my Mac. However, when I select the Moode entry and hit play, it stops immediately without playing. Doing tail /var/log/daemon.log shows:
Nov 22 13:07:25 iqaudio librespot[9361]: WARN:mdns::fsm: error sending packet Error { repr: Os { code: 99, message: "Cannot assign requested address" } }
Does anyone know how to fix this? I'll be grateful for any assistance!
I checked this out the other day and it was still working on Jessie-lite (can't remember the Moode version, but also on plain Raspbian and a version with Squeezelite).
I have had no luck with Stretch, although the connection is established, I get no sound.
I presume you filled in your user name and password and did the restart correctly?
ronnie
Last edited:
@ jamont
Just to add to my previous posting.
I tried just now to install raspotify on MoOde 4, beta 9 and all is working fine.
@Onionhead
I too could not get Bluetooth to connect.
This morning it would not connect to my old Windows 8.1 'phone or my Windows 10 laptop.
After numerous attempts I reinstalled the Bluetooth part again and it would still not connect.
I then started playing with the other "Additional Components" and after several reboots of MoOde I tried again and this time it connected to the 'phone but not the laptop.
The laptop does not see the 'phone so I guess there is something wrong with BT on the laptop.
Ronnie
Just to add to my previous posting.
I tried just now to install raspotify on MoOde 4, beta 9 and all is working fine.
@Onionhead
I too could not get Bluetooth to connect.
This morning it would not connect to my old Windows 8.1 'phone or my Windows 10 laptop.
After numerous attempts I reinstalled the Bluetooth part again and it would still not connect.
I then started playing with the other "Additional Components" and after several reboots of MoOde I tried again and this time it connected to the 'phone but not the laptop.
The laptop does not see the 'phone so I guess there is something wrong with BT on the laptop.
Ronnie
The laptop does not see the 'phone so I guess there is something wrong with BT on the laptop.
Ronnie
Well, you know that saying "...learn something new, every day"
I learned today that my second hand Lenovo T430 does not have a Bluetooth card fitted.🙄
My older and much battered Thinkpad T61 does however, and connected straightaway to Moode Bluetooth. 🙂
As I don't use any BT stuff, perhaps I can be forgiven for not knowing about this, 😱
I have even less of an idea how one uses it.😱
Ronnie
Last edited:
Well, you know that saying "...learn something new, every day"
I learned today that my second hand Lenovo T430 does not have a Bluetooth card fitted.🙄
My older and much battered Thinkpad T61 does however, and connected straightaway to Moode Bluetooth. 🙂
As I don't use any BT stuff, perhaps I can be forgiven for not knowing about this, 😱
I have even less of an idea how one uses it.😱
Ronnie
My story is even worse! I struggled my @rse off to get the BT working only to realise that I was using the RPi2 and not the 3so it also does not have BT. I forgot that I was using the RPI3 for something else.
@Mars67
Well we all get to enjoy a bit of the old schadenfreude 😉
Good luck against the Azzurri on the weekend
Ronnie
Well we all get to enjoy a bit of the old schadenfreude 😉
Good luck against the Azzurri on the weekend

Ronnie
Hi Tim
Please pardon my ignorance but how is this issue resolved?
Thanks
Hi,
////////////////////////////////////////////////////////////////
//
// COMPONENT 9 - Allo Piano 2.1 Firmware
//
////////////////////////////////////////////////////////////////
cd ~
wget https://github.com/allocom/piano-firmware/archive/master.zip
sudo unzip master.zip
sudo rm ./master.zip
sudo cp -r ./piano-firmware-master/lib/firmware/allo /lib/firmware
sudo rm -rf ./piano-firmware-master
sudo reboot
-Tim
My story is even worse! I struggled my @rse off to get the BT working only to realise that I was using the RPi2 and not the 3so it also does not have BT. I forgot that I was using the RPI3 for something else.

Thanks for confirming with the correct hardware and software settings it should work. Maybe I just need to keep at it.
Hi Tim, now you have had it a few days, how are you enjoying the touchscreen?
I have been using Moode with a touchscreen for sometime and really like having the screen where I can control it without grabbing a phone or tablet.
I built my player using a SmartPi Touch case in a similar style to this one on the Audiophonics website, however I used an IQAudio Dac + I already had and didn't bother with an on / off button as I always leave it on.
RaspTouch LTE I-Sabre V2 Back side - Streamer touch Raspberry Pi & DAC ES90023 - Audiophonics
I am glad the local display option is becoming an official Moode feature.
Hi,
Its pretty cool for sure 🙂 Do you know if there is a way to pre-configure zoom and overlay scrollbars in Chrome without having to actually open the Browser up?
-Tim
Thanks for confirming with the correct hardware and software settings it should work. Maybe I just need to keep at it.
Hi,
After turning it on and rebooting run the cmd below to see if its functioning.
pi@rp3:~ $ hciconfig
hci0: Type: Primary Bus: UART
BD Address: B8:27:EB:43:2A:84 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN ISCAN
RX bytes:850 acl:0 sco:0 events:61 errors:0
TX bytes:4256 acl:0 sco:0 commands:61 errors:0
-Tim
Thanks. I will continue using exfat since I have a Mac and a Windows computer.It doesn’t really matter.
FAT works well because you can transfer data between computer types, ntfs works for a PC environment and Moode.
NTFS is more reliable, as a file system.
Hi, I want to connect my Bose AE2w Bluetooth Headphones to Moode 4.0b9, but no success.
I found no setup instructions for that, so that's what i did:
Configure / System ==> Integrated BT Adapter -> ON + SET
REBOOT
Configure / Audio / Renderers ==> Bluetooth speaker -> ON + SET
Configure / Audio ==> Configure Bluetooth
INITIALIZE Controller ==> ok.
SCAN for devices ==> ok. (BT Headphone was found once)
But I couldn't find how to pair the device to moode.
After several attempts the output of INITIALIZE Controller is:
*** Initializing Bluetooth controller
***
Waiting to connect to bluetoothd...
[bluetooth]# [NEW] Controller B8:27:EB:6D:13:17 Moode Bluetooth [default]
[bluetooth]# Agent registered
[bluetooth]# power on
[bluetooth]# discoverable on
[bluetooth]# pairable on
[bluetooth]# agent on
Agent is already registered
[bluetooth]# default-agent
[bluetooth]# quit
[bluetooth]# Agent unregistered
[bluetooth]# [DEL] Controller B8:27:EB:6D:13:17 Moode Bluetooth [default]
[bluetooth]# Waiting to connect to bluetoothd...
***
*** Controller initialized
The controller seems to be initialized ...
But: now the the result of 'Scan for devices' is:
*** Scanning for devices (20 secs)
***
*** Trusted devices
***
*** Scan complete
and:
pi@moode:~ $ hciconfig
hci0: Type: Primary Bus: UART
BD Address: B8:27:EB:6D:13:17 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN ISCAN
RX bytes:970 acl:0 sco:0 events:79 errors:0
TX bytes:3909 acl:0 sco:0 commands:77 errors:0
Does anybody know, what's going wrong here ?
Regards, Klaus
I found no setup instructions for that, so that's what i did:
Configure / System ==> Integrated BT Adapter -> ON + SET
REBOOT
Configure / Audio / Renderers ==> Bluetooth speaker -> ON + SET
Configure / Audio ==> Configure Bluetooth
INITIALIZE Controller ==> ok.
SCAN for devices ==> ok. (BT Headphone was found once)
But I couldn't find how to pair the device to moode.
After several attempts the output of INITIALIZE Controller is:
*** Initializing Bluetooth controller
***
Waiting to connect to bluetoothd...
[bluetooth]# [NEW] Controller B8:27:EB:6D:13:17 Moode Bluetooth [default]
[bluetooth]# Agent registered
[bluetooth]# power on
[bluetooth]# discoverable on
[bluetooth]# pairable on
[bluetooth]# agent on
Agent is already registered
[bluetooth]# default-agent
[bluetooth]# quit
[bluetooth]# Agent unregistered
[bluetooth]# [DEL] Controller B8:27:EB:6D:13:17 Moode Bluetooth [default]
[bluetooth]# Waiting to connect to bluetoothd...
***
*** Controller initialized
The controller seems to be initialized ...
But: now the the result of 'Scan for devices' is:
*** Scanning for devices (20 secs)
***
*** Trusted devices
***
*** Scan complete
and:
pi@moode:~ $ hciconfig
hci0: Type: Primary Bus: UART
BD Address: B8:27:EB:6D:13:17 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN ISCAN
RX bytes:970 acl:0 sco:0 events:79 errors:0
TX bytes:3909 acl:0 sco:0 commands:77 errors:0
Does anybody know, what's going wrong here ?
Regards, Klaus
moOde 4.0 Beta 9 - Stuck on Step #2
Following the build recipe for 4.0.
Everything goes as planned except for the pi will not reboot after completing all the way through instruction 4 on Step #2.
When rebooting I get the error:
"Kernel panic-not syncing: VFS: unable to mount root fs on unknown-block(179,2)"
I can't even hold down Shift and boot to get to a recovery mode.
Following the build recipe for 4.0.
Everything goes as planned except for the pi will not reboot after completing all the way through instruction 4 on Step #2.
When rebooting I get the error:
"Kernel panic-not syncing: VFS: unable to mount root fs on unknown-block(179,2)"
I can't even hold down Shift and boot to get to a recovery mode.
Hi,
////////////////////////////////////////////////////////////////
//
// COMPONENT 9 - Allo Piano 2.1 Firmware
//
////////////////////////////////////////////////////////////////
cd ~
wget https://github.com/allocom/piano-firmware/archive/master.zip
sudo unzip master.zip
sudo rm ./master.zip
sudo cp -r ./piano-firmware-master/lib/firmware/allo /lib/firmware
sudo rm -rf ./piano-firmware-master
sudo reboot
-Tim
Thank you yet again Tim. Problem sorted!
What would cause the files to get "nuked"?
@Mars67
Well we all get to enjoy a bit of the old schadenfreude 😉
Good luck against the Azzurri on the weekend
Ronnie
Thanks Ronnie. Our National Rugby is a bit of a sore point at the moment!!!😡
Hi, I want to connect my Bose AE2w Bluetooth Headphones to Moode 4.0b9, but no success.
Does anybody know, what's going wrong here ?
Regards, Klaus
I was under the impression that the Bluetooth speaker functionality is to be able to stream audio to Moode from a Bluetooth enabled device such as a cellphone and not the other way around?
Tested right now....I could be doing something wrong, but bot with Lumin App on Ipad and Linn Kazoo on Mac Tidal is not available....Ohradio is the ability to play Radio through the control point.
If you are using Kazoo there should be a radio option , in there should be a couple of radio stations that are already defined in Moode, this is not the list in the web front end though.
What you are doing is switching between sources.
I think Kazoo does this automatically, not sure about lumin. On android you must use BubbleDS and change source in the menu when you switch between play lists and Radio.
On Kazoo I got the message "Tidal is not available. Your DS needs to be running Davaar 23 or later"
Thanks. I will continue using exfat since I have a Mac and a Windows computer.
Mac and Windows both read ntfs. With an app, Mac can write it too.
Does anybody know, what's going wrong here ?
First of all, Moode works as a BT sink not as a source.
The whole stuff is not straight forward and all but well documented.
It took me a while to get it properly going.
Since there are not many more (if any) RPI BT Audio implementations
as done in Moode out there, you'll be pretty much on your own to get
things going.
Good luck with that. I'm sure you'll manage. 😉
Thanks Ronnie. Our National Rugby is a bit of a sore point at the moment!!!😡
My son in law is a Saffer from Durban - we’re not allowed to discuss 😉
Tested right now....I could be doing something wrong, but bot with Lumin App on Ipad and Linn Kazoo on Mac Tidal is not available....
On Kazoo I got the message "Tidal is not available. Your DS needs to be running Davaar 23 or later"
Could be an issue that SWIZZLE reported a couple of days ago with the permissions on the UPMPDCLI config file.
ssh to your Pi and try the below command.
sudo chmod 644 /etc/upmpdcli.conf
reboot.
- Home
- Source & Line
- PC Based
- Moode Audio Player for Raspberry Pi