12-06-2024, 11:52 AM
(12-05-2024, 08:02 PM)Tim Curtis Wrote:(12-05-2024, 06:08 PM)radu022003 Wrote: Hello,
I have faced the same problem as you using the MoOde version 9.1.5 on a raspberry pi 4.
My observation is that in version 9.1.5 the PA can not be enabled/disabled from the UI.
My approach was to comment out the line : #ExecStart=/usr/bin/bt-agent -c NoInputNoOutput inside /etc/systemd/system/bt-agent.service file.
Also in file: /var/www/daemon/worker.php I have commented out the same line that calls bt-agent.
My workaround is to start the bt-agent from command line whenever I need to add a new bluetooth device. Luckly for me should not happen often.
But adding the PairingAgent enable/disable in the web-ui would help a lot.
Thank you and best regards.
If the agent is stopped your your client may connect but Moode "Bluetooth Active" screen won't appear and bluealsa won't play any audio because bt-agent is needed to complete the client connection setup which results in bluealsa-aplay (the audio player) being started.
IIRC @TheOldPresbyope successfully tested PIN code pairing on his Android devices. My tests with IOS failed.
I totally believe you, but I tested this "process" with 3 different devices and it works. Today I tested with the fourth device (Android) and the android was not connecting to MoOde over bluetooth when connection was initiated from Android. When connection was initiated from MoOde, connection was successful. The previously paired devices are still working, when bt-agent is stopped.
Perhaps I have forgotten some steps ...
