Hi,
I'm unable to get this detected under hardware, lsusb shows:
Bus 002 Device 002: ID 0e0f:0003
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 004: ID 0a5c:21ec
Bus 002 Device 003: ID 0e0f:0002
Bus 002 Device 001: ID 1d6b:0001
Bus 002 Device 005: ID 0658:0200
The device is 0a5c:21ec and is listed here: https://github.com/winterheart/broadcom-bt-firmware
Is there anything I can do to get this working?
I've now purchased and tried 3 BT dongles without luck...
I'm running ESXI 6.7 and the device is attached to the VM (shows in console on boot).
@pvizeli is there anything I can do to workaround this, I'm pretty desperate :/
Thanks in advance.
Seems I need: BCM20702A1-0a5c-21e8.hcd
The device is actually BCM20702A0-0a5c-21e8.hcd, but it's a common issue on newer kernels that it actually wants to see BCM20702A1-0a5c-21e8.hcd in lib/firmware/bcrm rather than the expected BCM20702A0-0a5c-21e8.hcd
Did you solve problem with usb dongle. I have same problem with logitech dinovo mini.
Had no choice but to move to Debian 9, sadly...
Wish I came across this a couple of days ago. I have ESXi 6.7 running on a NUC and no dice with the built-in BT. The BT dongle I just received didn't work either. I'm assuming your running a Debian 9 VM on your ESXi host? Really dont want to give up HassOS if I can but might have too :-(
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@pvizeli Is this on your radar for HassOS? I would like to stay on HassOS if possible.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Just to add a 馃憤馃徏 to this closed issue. I'm moving off HassOS to Debian for the same reason. I'd love the ability to inject other firmware and drivers via the CONFIG USB
Please do something, I bought 3 dongle included wide used on linux pluggable BT4.0 without luck