I have set up the docker container “openhab/openhab:latest-debian” on my openSuSE 15.1. I already integrated an MQTT-bridge, which is working for the best. Now I wanted to integrate an bluetooth-dongle.
My suse host can handle it:
robotron:~ # lsusb
…
Bus 003 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
…
robotron:~ # hcitool dev
Devices:
hci0 00:1A:7D:DA:71:08
robotron:~ #
But inside the container I cannot configure it. I installed the “Bluetooth Binding”, went to “Inbox” -> “Bluetooth Binding” -> “Add manually” > “Bluetooth blueZ Adapter” and added the address, I got from the host system.
Finaly the the dongle is not working in state: “UNINITIALIZED - HANDLER_INITIALIZING_ERROR”.
Since there are not any bluetooth tool inside the container, I’m asking whether it is possible to get this running inside a container?
Did you pass the device to the container in the docker run command? Is the user inside the container (openhab, 9001 by default I think but you can set it using a passed in environment variable) a member of what ever group has permissions to read/write to that device (on debian Linux variants that group is usually dialout or tty)?
In the host, I added openhab to the groups:
robotron:~ # grep openhab /etc/group
tty:x:5:openhab
dialout:x:16:lirc,openhab
openhab:x:455:falk,openhab
robotron:~ #
But the error remains. Below /dev I can’t find a device node for that, but do bluetooth devs have one?
I don’t use the BT binding so I’ll be of limited help. But if that bug fix is the source of a problem, you need to run OH 2.5 M4 (or any version of OH after June of this year).