Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linux: SimpleBLE fails to find services for some peripherals #299

Closed
JoeHowse opened this issue Apr 7, 2024 · 1 comment
Closed

Linux: SimpleBLE fails to find services for some peripherals #299

JoeHowse opened this issue Apr 7, 2024 · 1 comment

Comments

@JoeHowse
Copy link

JoeHowse commented Apr 7, 2024

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]

@kdewald
Copy link
Member

kdewald commented Aug 19, 2024

Hey @JoeHowse, I think this issue is now solved after landing the following fix #321

Feel free to reopen if it's still failing.

@kdewald kdewald closed this as completed Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants