Missing firmware has nothing to do with bluez. Plus those "Bluetooth" log messages are from the kernel, not bluez.
It appears the linux-firmware package contains some related firmware, but just not the right one...
/lib/firmware/ar3k/AthrBT_0x01020001.dfu
/lib/firmware/ar3k/AthrBT_0x01020200.dfu
/lib/firmware/ar3k/AthrBT_0x01020201.dfu
/lib/firmware/ar3k/AthrBT_0x11020000.dfu
/lib/firmware/ar3k/AthrBT_0x11020100.dfu
/lib/firmware/ar3k/AthrBT_0x31010000.dfu
/lib/firmware/ar3k/AthrBT_0x31010100.dfu
/lib/firmware/ar3k/AthrBT_0x41020000.dfu
So a fix would either come in the 'linux-firmware' package or in the kernel itself ('linux').
Missing firmware has nothing to do with bluez. Plus those "Bluetooth" log messages are from the kernel, not bluez.
It appears the linux-firmware package contains some related firmware, but just not the right one... ar3k/AthrBT_ 0x01020001. dfu ar3k/AthrBT_ 0x01020200. dfu ar3k/AthrBT_ 0x01020201. dfu ar3k/AthrBT_ 0x11020000. dfu ar3k/AthrBT_ 0x11020100. dfu ar3k/AthrBT_ 0x31010000. dfu ar3k/AthrBT_ 0x31010100. dfu ar3k/AthrBT_ 0x41020000. dfu
/lib/firmware/
/lib/firmware/
/lib/firmware/
/lib/firmware/
/lib/firmware/
/lib/firmware/
/lib/firmware/
/lib/firmware/
So a fix would either come in the 'linux-firmware' package or in the kernel itself ('linux').