07-15-2020, 04:05 PM
(This post was last modified: 07-15-2020, 04:07 PM by TheOldPresbyope.
Edit Reason: added parenthetical
)
@Ikke4
I thought this reconnection "just worked" but I was able just now to repro your issue. However, it seemed to be only momentary.
System - moOde 6.6.0 on an RPi3A.. Bluetooth renderer enabled and Bluez Config screen used to scan for, pair with, and connect to a JBL Flip 2 Bluetooth speaker. The Config screen shows the connection and the JBL emits its annoying beep sequence to indicate something has connected to it. [Note, the Pairing agent is not germane here. It deals with incoming pairing, not outgoing.]
Radio station is playing over the JBL.
Now reboot moOde. (I left the JBL powered on; I suppose switching it off and on again should be another test.)
After moOde has restarted, the JBL once again beeps as if something has connected to it. The Bluez screen shows it's still in MPD audio output -> Bluetooth mode but now doesn't show any Bluetooth devices (which leads to the error message you mentioned.) There's no audio output and various command line queries show no Bluetooth connection.
However, in the process of opening the moOdeUI in a new browser instance, the JBL beeped yet again and now it really is connected. I can again play a radio station over the JBL without having made any manual adjustment in the Bluez config screen.
I'm not sure what's going on here. I'm thinking the next step is to modify the bluealsa.service file to enable logging. This may turn up something useful (or may just confuse me further
).
Meanwhile, how about trying the same hack of closing the existing moOdeUI instance in your browser and opening another. Does it lead to the same auto-magical reconnection?
Regards,
Kent
I thought this reconnection "just worked" but I was able just now to repro your issue. However, it seemed to be only momentary.
System - moOde 6.6.0 on an RPi3A.. Bluetooth renderer enabled and Bluez Config screen used to scan for, pair with, and connect to a JBL Flip 2 Bluetooth speaker. The Config screen shows the connection and the JBL emits its annoying beep sequence to indicate something has connected to it. [Note, the Pairing agent is not germane here. It deals with incoming pairing, not outgoing.]
Radio station is playing over the JBL.
Now reboot moOde. (I left the JBL powered on; I suppose switching it off and on again should be another test.)
After moOde has restarted, the JBL once again beeps as if something has connected to it. The Bluez screen shows it's still in MPD audio output -> Bluetooth mode but now doesn't show any Bluetooth devices (which leads to the error message you mentioned.) There's no audio output and various command line queries show no Bluetooth connection.
However, in the process of opening the moOdeUI in a new browser instance, the JBL beeped yet again and now it really is connected. I can again play a radio station over the JBL without having made any manual adjustment in the Bluez config screen.
I'm not sure what's going on here. I'm thinking the next step is to modify the bluealsa.service file to enable logging. This may turn up something useful (or may just confuse me further
).Meanwhile, how about trying the same hack of closing the existing moOdeUI instance in your browser and opening another. Does it lead to the same auto-magical reconnection?
Regards,
Kent
