eriklins/insideblue-ble-tool

InsideBlue BLE Tool is a cross-platform Bluetooth LE utility. It can scan for BLE devices showing device information and advert payload as well as connect to devices and access GATT services/characteristics.

insideblue-ble-tool's Issues

InsideBlue can no longer connect to BLE devices on Windows 11

After switching to Windows 11, InsideBlue still does proper scanning for BLE devices, but connecting hangs for a while and finally fails. Not sure if related to SimpleBLE issue 31, which was related to Python bindings.

Cross Platform Support

As title, this application works on Linux and other os?

DLL SimpleBLE libraries

Hi , excellent repo .
I have downloaded repo and installed in my work folder for Lazarus 2.2.2 under windows 10 64bit .
When I try to compile / run app I get this message :
Failed to load SimpleBLE library .
I have copied 2 dll files from this repo (last release ) and place them into src and bin folders . But I am still getting the same message .
Can you please advice where is a problem . Thanks

compile instructions

Hello, I use arm64 so trying to compile it from source. New toolchains with different conf files etc always have a steep learning curve for me. I was hoping to be able to use a simple lazbuild command. Unfortunately it just says it cant find the main file, I tried in the ide gui thing and it says cant find main unit. Also not sure how to include the lazarus dependency listed in README. My lazarus etc install seems to be fine I use it to compile versaloons vsgui. Thank you in advance for any possible hints or steps.

GUI form elements do not scale/position properly when Windows display scaling set different from 100%

Just tried InsideBlue first time on Windows 11 and the form elements look weird.

Add decoding of characteristics values for known BT SiG Assigned Numbers.

Some data is not displayed correctly. (ASCII)
Example in the screenshot.

Services listing for device - Editable field bug

Hi There seems to be an issue with listing services for some devices (see screenshot). The third service listed is strange. I do not know which of the additional services avliable on the device this represents, but here is my parsed output for the same device (Also using SimpleBLE):

Connected: Tacx Flux-2 25385 -55dBm [Connectable] e2:62:1c:17:1f:0d
Manufacturer data: Tacx b.v. (0x2980)
Service: 00001800-0000-1000-8000-00805f9b34fb
Characteristic: 00002a00-0000-1000-8000-00805f9b34fb [read]
Characteristic: 00002a01-0000-1000-8000-00805f9b34fb [read]
Characteristic: 00002a04-0000-1000-8000-00805f9b34fb [read]
Service: 00001801-0000-1000-8000-00805f9b34fb
Characteristic: 00002a05-0000-1000-8000-00805f9b34fb [indicate]
Descriptor: 00002902-0000-1000-8000-00805f9b34fb
Service: 0000180a-0000-1000-8000-00805f9b34fb
Characteristic: 00002a24-0000-1000-8000-00805f9b34fb [read]
Characteristic: 00002a26-0000-1000-8000-00805f9b34fb [read]
Characteristic: 00002a29-0000-1000-8000-00805f9b34fb [read]
Service: 00001818-0000-1000-8000-00805f9b34fb
Characteristic: 00002a5d-0000-1000-8000-00805f9b34fb [read]
Characteristic: 00002a63-0000-1000-8000-00805f9b34fb [notify]
Descriptor: 00002902-0000-1000-8000-00805f9b34fb
Characteristic: 00002a65-0000-1000-8000-00805f9b34fb [read]
Characteristic: 00002a66-0000-1000-8000-00805f9b34fb [write_request, indicate]
Descriptor: 00002902-0000-1000-8000-00805f9b34fb
Service: 00001826-0000-1000-8000-00805f9b34fb
Characteristic: 00002acc-0000-1000-8000-00805f9b34fb [read]
Characteristic: 00002ad2-0000-1000-8000-00805f9b34fb [notify]
Descriptor: 00002902-0000-1000-8000-00805f9b34fb
Characteristic: 00002ad6-0000-1000-8000-00805f9b34fb [read]
Characteristic: 00002ad8-0000-1000-8000-00805f9b34fb [read]
Characteristic: 00002ad9-0000-1000-8000-00805f9b34fb [write_request, indicate]
Descriptor: 00002902-0000-1000-8000-00805f9b34fb
Characteristic: 00002ada-0000-1000-8000-00805f9b34fb [notify]
Descriptor: 00002902-0000-1000-8000-00805f9b34fb
Service: 669aa501-0c08-969e-e211-86ad5062675f
Characteristic: 669aac01-0c08-969e-e211-86ad5062675f [read, write_request]
Descriptor: 00002904-0000-1000-8000-00805f9b34fb
Service: 669aa605-0c08-969e-e211-86ad5062675f
Characteristic: 669aab01-0c08-969e-e211-86ad5062675f [write_request]
Descriptor: 00002901-0000-1000-8000-00805f9b34fb
Characteristic: 669aab02-0c08-969e-e211-86ad5062675f [notify]
Descriptor: 00002901-0000-1000-8000-00805f9b34fb
Descriptor: 00002902-0000-1000-8000-00805f9b34fb
Characteristic: 669aab21-0c08-969e-e211-86ad5062675f [write_request, write_command]
Descriptor: 00002901-0000-1000-8000-00805f9b34fb
Characteristic: 669aab22-0c08-969e-e211-86ad5062675f [notify]
Descriptor: 00002901-0000-1000-8000-00805f9b34fb
Descriptor: 00002902-0000-1000-8000-00805f9b34fb
Service: 6e40fec1-b5a3-f393-e0a9-e50e24dcca9e
Characteristic: 6e40fec2-b5a3-f393-e0a9-e50e24dcca9e [notify]
Descriptor: 00002902-0000-1000-8000-00805f9b34fb
Characteristic: 6e40fec3-b5a3-f393-e0a9-e50e24dcca9e [write_request, write_command]

The device also fails to connect, and I'm guessing that this is related. There is no output to the log other than "Failde to connect...") The device is connectable via SimpleBLE as I am doing it in my application from the same machine (Windows, SimpleBLE). Please let me know if there is some input I can provide that can help you track down the connection issue. I belive the isssue is somewhere in your handling of the service listings.

InsideBlue 0.6 Win64