I was on my way to open a bug, but it seems to be the same as this one.

Same problem here, but just cannot see bluetooth devices at all. Same bluetooth chip (BCM20702A0), on Asus Z97 motherboard.

$ dmesg
[    1.416918] usb 3-2: New USB device found, idVendor=0b05, idProduct=17cf
[    1.416920] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.416921] usb 3-2: Product: BCM20702A0
[    1.416922] usb 3-2: Manufacturer: Broadcom Corp
[    1.416923] usb 3-2: SerialNumber: 54271EFB4038
...
[    8.150565] Bluetooth: Core ver 2.21
[    8.150576] NET: Registered protocol family 31
[    8.150577] Bluetooth: HCI device and connection manager initialized
[    8.150579] Bluetooth: HCI socket layer initialized
[    8.150581] Bluetooth: L2CAP socket layer initialized
[    8.150585] Bluetooth: SCO socket layer initialized
[    8.150927] ACPI Warning: SystemIO range 0x000000000000F000-0x000000000000F01F conflicts with OpRegion 0x000000000000F000-0x000000000000F00F (\_SB_.PCI0.SBUS.SMBI) (20150930/utaddress-254)
[    8.150932] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    8.159476] usbcore: registered new interface driver btusb
[    8.164258] Bluetooth: hci0: BCM: chip id 63
[    8.175807] wl: module license 'MIXED/Proprietary' taints kernel.
[    8.175810] Disabling lock debugging due to kernel taint
[    8.178181] wl: module verification failed: signature and/or required key missing - tainting kernel
[    8.180377] Bluetooth: hci0: pc-dsktp-3
[    8.181377] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[    8.183471] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0b05-17cf.hcd failed with error -2
[    8.183473] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not found

I have similar problem with Asus BT400 Bluetooth USB dongle widely sold in consumers shops

===========================
[ 2409.677929] Bluetooth: hci0: BCM: chip id 63
[ 2409.694922] Bluetooth: hci0: BCM20702A
[ 2409.696939] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[ 2409.696996] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0b05-17cb.hcd failed with error -2
[ 2409.697004] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cb.hcd not found
===========================

To file this problem, I had to: 

- download the MS Windows version of the patch from the Asus site: http://dlcdnet.asus.com/pub/ASUS/wireless/USB-BT400/UT_USB_BT400_6516000.zip
- convert it form hex to hcd using hex2hcd included in bluez rpm
- then copy the resulting file in /usr/lib/firmware/brcm
(See https://workingninja.com/blog/installing-asus-bt400-raspberry-pi-raspbian-wheezy )

To improve Fedora user experience I suggest to insert this patch in the linux-firmware or an other firmware rpm...

(In reply to Didier G from comment #2)
> I have similar problem with Asus BT400 Bluetooth USB dongle widely sold in
> consumers shops
> 
> ===========================
> [ 2409.677929] Bluetooth: hci0: BCM: chip id 63
> [ 2409.694922] Bluetooth: hci0: BCM20702A
> [ 2409.696939] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
> [ 2409.696996] bluetooth hci0: Direct firmware load for
> brcm/BCM20702A1-0b05-17cb.hcd failed with error -2
> [ 2409.697004] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cb.hcd not
> found
> ===========================
> 
> To file this problem, I had to: 
> 
> - download the MS Windows version of the patch from the Asus site:
> http://dlcdnet.asus.com/pub/ASUS/wireless/USB-BT400/UT_USB_BT400_6516000.zip
> - convert it form hex to hcd using hex2hcd included in bluez rpm
> - then copy the resulting file in /usr/lib/firmware/brcm
> (See
> https://workingninja.com/blog/installing-asus-bt400-raspberry-pi-raspbian-
> wheezy )
> 
> To improve Fedora user experience I suggest to insert this patch in the
> linux-firmware or an other firmware rpm...

Unfortunately, the license stated in the .pdf file in the zip forbids us from doing so.  We cannot include this firmware in Fedora unless broadcom releases it in a format already usable and under a license that permits redistribution of unmodified binaries.

I'll mark this as FutureFeature in the very slight chance that they do this.

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.