Nice - that did the trick. Thanks! It now fully works with both Airplay, Spotify (after recompile as instructed in another post) and with Bluetooth.
However one small thing with Bluetooth (and don't know why this changed). To get it to connect I need to manually choose "connect" from the webinterface. Choosing connect from the phone (iPhone) will not make a connection (it fails after trying for a few seconds). Connecting from the webinterface works fine and it can then play through the Mojo.
It's actually the same thing as described here: http://moodeaudio.org/forum/showthread.p...=bluetooth (not the 3 second thing, but the "reverse connection")
What can be the reason for that?
Edit:
And to answer that - it was because the bluetooth device wasn't trusted when added.
That also showed up in the log.
Adding the address as trusted with bluetoothctl makes it possible to connect from the phone.
Now I think the final thing is getting the pi to automatically do bluetooth connect during "power on" would make it complete (though this might not always be wanted behaviour).
However one small thing with Bluetooth (and don't know why this changed). To get it to connect I need to manually choose "connect" from the webinterface. Choosing connect from the phone (iPhone) will not make a connection (it fails after trying for a few seconds). Connecting from the webinterface works fine and it can then play through the Mojo.
It's actually the same thing as described here: http://moodeaudio.org/forum/showthread.p...=bluetooth (not the 3 second thing, but the "reverse connection")
What can be the reason for that?
Edit:
And to answer that - it was because the bluetooth device wasn't trusted when added.
That also showed up in the log.
Code:
moode bluetoothd[794]: Authentication attempt without agent
moode bluetoothd[794]: Access denied: org.bluez.Error.RejectedAdding the address as trusted with bluetoothctl makes it possible to connect from the phone.
Now I think the final thing is getting the pi to automatically do bluetooth connect during "power on" would make it complete (though this might not always be wanted behaviour).
