(09-24-2021, 12:09 AM)Tim Curtis Wrote: (09-23-2021, 10:27 PM)TheOldPresbyope Wrote: @Tim Curtis
Turns out I lied. I found an RPi2B 1.1 hiding in a carton I unwrapped just this afternoon.Trying the same test, I get:
Code:
pi@moode:~ $ sudo hcitool dev
Devices:
But wait, there's more. The System Info popup declares
Code:
Onboard WiFi = None
Onboard BT = None
and the System Config screen doesn't offer the option of turning either service off/on. Looks like moOde can already detect the absence of a physical interface.
Regards,
Kent
Maybe. Below is from my notes from way back when.
Code:
- Bluetooth device detection ?
- hcitool dev | grep hci
- NOTE: this actually doesnt detect the presense of the adapter, only whether an adapter is enabled.
Tim, If you are looking at fixing this quirk, it appears to me that there are three use cases that can cause the issue:
- The Native Bluetooth adapter is Not Present: I think that moOde already detects this condition because the /Configure/ System panel doesn't have the option to enable it.
- The Native Bluetooth adapter is present but turned OFF:
My problem arose because I had Configure/ Audio/ Audio Renderers/ Bluetooth Renderer set to Moode Bluetooth and I then went into System Config and turned the Bluetooth Adapter OFF!!!
I know that you have a fix planned in v7.40 which may fix this ...
- The Native Bluetooth Adapter is Not Present but a USB Bluetooth Adapter is attached:
In this case, I used the Configure/ Audio/ MPD Config/ Audio Output EDIT button to direct the MPD Audio Output to the "Wireless Music Adap"
In this case, if the USB Bluetooth adapter is disconnected or un-Paired, the Audio Output resets to Pi Headphone Jack or Pi HDMI, whichever was previously selected. I think this is working as designed.
I hope this is reasonably lucid. Let me know if you need me to do any testing. Thanks, Robin