Currently I have two USB Bluetooth dongles connected to HA. These are enumerated as hci0 and hci1.
hci0 is long range bluetooth adapter and used to connect to flic buttons around the house. The flic daemon runs separately from HA, and by default uses hci0. This can be overridden.
When HA starts BT device tracking (not LE) it tries to discover devices but throws an error because hci0 is already in use. It then tries hci1 (perhaps default behaviour of the BT stack?) and it succeeds however continues to throw errors in the log, every time it scans.
Is it possible to allow specifying a device in the config, either as hciX or perhaps BT address? If not that, then can the discovery error be supressed?
Log excerpt
17-04-17 12:56:58 ERROR (Thread-4) [homeassistant.components.device_tracker.bluetooth_tracker] Error looking up bluetooth device!
Traceback (most recent call last):
File "/storage/config/deps/bluetooth/bluez.py", line 31, in discover_devices
lookup_class=lookup_class, device_id=device_id)
_bluetooth.error: (16, 'Device or resource busy')
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/andrew/.local/lib/python3.5/site-packages/homeassistant/components/device_tracker/bluetooth_tracker.py", line 72, in update_bluetooth
for dev in discover_devices():
File "/home/andrew/.local/lib/python3.5/site-packages/homeassistant/components/device_tracker/bluetooth_tracker.py", line 38, in discover_devices
lookup_class=False)
File "/storage/config/deps/bluetooth/bluez.py", line 34, in discover_devices
raise BluetoothError ("error communicating with local "
bluetooth.btcommon.BluetoothError: error communicating with local bluetooth adapter
Thanks
Andrew