On Linux, SimpleBLE cannot find or use the services of peripherals which are based on the Feasycom FSC-BT986 Bluetooth module (https://www.feasycom.com/fsc-bt986). Peripheral.services() returns an empty list and Peripheral.notify(...) (with known-correct UUIDs) throws RuntimeError: Service with UUID ... not found.
UUIDs for Feasycom modules:
Service UUID: 0000fff0-0000-1000-8000-00805f9b34fb
Notify UUID: 0000fff1-0000-1000-8000-00805f9b34fb
Write or Write without Response UUID: 0000fff2-0000-1000-8000-00805f9b34fb
This is apparently a SimpleBLE issue because both bluetoothctl and Bleak can find and use the services of these peripherals.
Currently, I am unsure of the cause or extent of the issue. SimpleBLE does work on Linux for at least some peripherals based on other hardware.
System specs:
SimpleBLE version: Tested with 0.7.3
OS: Tested on Debian Bookworm, Debian Trixie, and Manjaro
Bluetooth adapter: Tested with several. The issue is present with most adapter chipsets, including Intel AX200, Intel AX201, and Realtek RTL8761BUV. Interestingly, the issue is not present with Broadcom BCM43456, which is used in some ARM systems such as Raspberry Pi 400 and PineBook Pro.
[Edit: Updated bullet point on Bluetooth adapters tested]
[Edit: Added UUIDs]
On Linux, SimpleBLE cannot find or use the services of peripherals which are based on the Feasycom FSC-BT986 Bluetooth module (https://www.feasycom.com/fsc-bt986).
Peripheral.services()returns an empty list andPeripheral.notify(...)(with known-correct UUIDs) throwsRuntimeError: Service with UUID ... not found.UUIDs for Feasycom modules:
This is apparently a SimpleBLE issue because both bluetoothctl and Bleak can find and use the services of these peripherals.
Currently, I am unsure of the cause or extent of the issue. SimpleBLE does work on Linux for at least some peripherals based on other hardware.
System specs:
[Edit: Updated bullet point on Bluetooth adapters tested] [Edit: Added UUIDs]