I’m trying to get Hype SDK ( https://hypelabs.io/iot/ ) to work on a Ubuntu 18.04-based container, but I’m running into issues.
Problem:/var/run/sdp socket is not created in the container by bluetoothd. This socket is needed by the Hype framework.
I tried to fix it by configuring /etc/systemd/system/dbus-org.bluez.service in the container to start the daemon in --compat mode, but it had no effect. (Based on these instructions: https://bbs.archlinux.org/viewtopic.php?id=201672 )
I suspect that this is due to the fact that the Bluetooth daemon is magically running on the host OS? Threads like RPi3 running bluetoothd with --experimental flag suggest it. Unfortunately, this is a little bit over my head now (tried SSHing into the supervisor and could not locate the Bluetooth service), so I would appreciate someone’s help on the topic…
Best wishes,
Konrad
PS: One more question, if it is true that the Bluetooth daemon is running on host OS, is there any point in installing BlueZ on the container OS?
Oh, interesting! It turns out that resin_supervisor accessible via sudo resin local ssh and “Host OS” accessible via the Dashboard are two different things!
When I actually log in to the Host OS via the dashboard I see promising results:
root@d379470:/# ps | grep bluetooth
1084 root 5440 S /usr/libexec/bluetooth/bluetoothd --experimental
30244 root 5628 S /usr/lib/bluetooth/bluetoothd --compat
30533 root 2864 S grep bluetooth