Comment 52 for bug 1748565

WRT comment #46: Installing brcm/BCM20702A1-0b05-180a.hcd from winterheart had no effect on this or any other Bluetooth anomalies I've observed except eliminating the "Direct firmware load" error.

WRT comment #51: in my environment this co-occurs with Bluetooth functioning "correctly", i.e. the only issue I see is this error message. (However, I am only using LE, not audio/BR/EDR.)

I suspect it may be related to mixing HCI-based and D-Bus-based bluetooth control within or across applications, or to an application not properly stopping discovery before it shuts down. Or both.

Issuing a "power off" "power on" sequence from bluetoothctl stops the error message. Getting from "unhealthy Bluetooth" to "working Bluetooth" may involve a power cycle, fixing multiple problems.