blueman | Blueman is a GTK+ Bluetooth Manager

It's because you are using the same binding.

In your ForEach, you are creating multiple TextEditors but they are editing the same variable like $otext. You need to create a struct that holds the text, and the array you use in the ForEach should be of type YourStruct. Then you pass the text to TextEditors.

indexOf requires an element. You can use find to get the element first and get the index next:

This is probably due to using a compositing manager like compton or picom. You can either try another compositing manager, update your graphics driver.

You can also try to start Awesome with --no-argb. This will disable some features like true transparency in the titlebars, but is closer to what other window manager use, so tends to trigger less bugs in the graphics driver or compositing managers.

hcitool and gatttool were some of the tools that were deprecated by the BlueZ project in 2017. If you are following a tutorial that uses them, there is a chance that it might be out of date. The correct tool to be using now is bluetoothctl.

If you are new to Bluetooth then using a generic Bluetooth Low Energy scanning and exploration tool like nRF Connect might be more helpful to understand what is going on. Reading up on how BLE GATT services work will help with the service > Characteristics information.

Once you can read and write with the characteristics, your next challenge will be to work out what the binary data that is being sent/received means as it looks like they are using a lot of custom characteristics.

Random drive-by idea that I am too lazy to test:

There are a number of layers that are used in the communication process and depending where you tap into that stack will depend what coding you need to do. The other complication is that BlueZ (the Bluetooth stack on linux) changed how it works over recent times leaving a lot of out of date information on the internet and easy for people to get confused.

With two Bluetooth devices, they need to establish a pairng. This is typically a one off provisioning step. This can be done with tools like Blueman or on the command line with bluetoothctl. Once you have a pairing established between your RPi and the M5Stack Stick, you shouldn't need to discover nearby devices again. Your script should just be able to connect if you tell it which device to connect to.

The M5Stack stick is advertising as having a Serial Port Profile (SPP). This is a layer on top of rfcomm.

There is a blog post about how this type of connection can be done with the standard Python3 installation: http://blog.kevindoran.co/bluetooth-programming-with-python-3/

My expectation is that you will only have to do the client.py on your RPi as the M5Stack Stick is the server. You will need to know its address and which port to connect on. Might be some trial and error on the port number (1 and 3 seem to be common).

Another library that I find helpful for SPP, is bluedot as it abstracts away some of the boilerplate code: https://bluedot.readthedocs.io/en/latest/btcommapi.html#bluetoothclient

So in summary, my recommendation is to use the standard Python Socket library or Bluedot. This will allow you to specify the address of the device you wish to connect to in your code and the underlying libraries will take care of making the connection and setting up the serial port (as long as you have already paired the two devices).

Example of what the above might look like with Bluedot

If you are running WSL 1 then then, you need to add following line to .bashrc in home: