balena-labs-projects / bluetooth Goto Github PK

Block restarts without error being thrown.

On the main blocks page icons next to audio and bluetooth blocks look larger compared to other blocks.

Here's the logo file as defined in balena.yml:
https://raw.githubusercontent.com/balenablocks/audio/master/logo.png

And here's correctly looking one from fbcp:
https://raw.githubusercontent.com/balenablocks/fbcp/master/logo.png

The logos have different size and proportions. Fbcp could be used as a reference.

Recent releases of balenaOS will "remember" connected devices in /var/lib/bluetooth.

balena-os/meta-balena@3815e42

I've confirmed this on the following device:

ID="balena-os"
NAME="balenaOS"
VERSION="2.60.1+rev1"
VERSION_ID="2.60.1+rev1"
PRETTY_NAME="balenaOS 2.60.1+rev1"
MACHINE="raspberrypi3"
VARIANT="Development"
VARIANT_ID="dev"
META_BALENA_VERSION="2.60.1"
RESIN_BOARD_REV="a28e387"
META_RESIN_REV="9aed19a"
SLUG="raspberrypi3"

However, this bluetooth block does not reconnect to devices automatically after a power cycle. I suspect this is something that can be added via this block, but if balenaOS changes are required we can open a new issue there.

Note that this was previously fixed in balenaSound before it started using this bluetooth block.

balena-io-experimental/balena-sound@78a727a

Not sure if the same fix would apply to this block since it looks like we are now relying on the host OS for more components.

Is there a simple example that shows how to use the bluetooth block to implement a simple communication between for example a raspberry pi 4 and a laptop or phone?

Currently, there is no documented way to interact or control the Bluetooth block from inside or outside the container. It would be quite helpful to issue commands to the Bluetooth block from the outside to perform functions like:

1. Scan for Bluetooth devices
2. Turn on/Turn off Bluetooth
3. Connect to device

The Bluetooth block could expose an API endpoint to send requests to perform these functions or more from other containers in the application. While, if there is a tool being used to get the Bluetooth running inside the container some documentation can be linked about that tool for folks to use & control the Bluetooth block (programatically) from inside the container. Thanks for creating this! 💟

Add support for other applications to consume metadata and send commands.
I think we have dbus MPRIS iirc in balenaOS?

Play sound when bluetooth devices connect/disconnect.
Should integrate seamlessly with balenaAudio primitive.

Emit events when devices connect/disconnect.

We have seen problems when trying to re-pair devices: balena-io-experimental/balena-sound#526

To reproduce (pi3, android phone, oneplus 7T):

1. pair phone to pi
2. unpair
3. When my pi3's containers came back online, I was unable to pair to it from my phone, getting couldn't pair with balenaOS 0687 because of an incorrect pin or passkey error.
4. I ssh'd into the bluetoothcontainer and with bluetoothctl paired-devices i saw: Device 48:01:C5:7B:61:78 OnePlus 7T - so the device was listing my phone as paired, when they were not paired.
5. I then removed my phone from the bluetooth blocks paired devices list with bluetoothctl remove 48:01:C5:7B:61:78 - I then was able to pair my phone to the pi again!

So it seems like there's a problem with the balena device retaining the other device as being paired, even when its not, which causes some funkyness when that other device tries to re-pair

https://github.com/balenablocks/bluetooth/blob/03c6941f18444698abdae3ebec9e4e3568d95c9a/Dockerfile.template#L10

If we use the hostOS bluetoothd, do we need to install bluez in the container?

An interface that gets configured by the block will keep it's configuration until told otherwise.
Restarting the block with a different BLUETOOTH_HCI_INTERFACE value will configure the new one but keep the old one configured. So both interfaces will be configured and broadcasting.

To avoid that we need to restart/turn off all interfaces at block startup.