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

Characteristic - Insufficient Encryption #33

Open
adras opened this issue Mar 16, 2020 · 5 comments
Open

Characteristic - Insufficient Encryption #33

adras opened this issue Mar 16, 2020 · 5 comments

Comments

@adras
Copy link

adras commented Mar 16, 2020

I'm trying to explore a bluetooth device, however on some characteristics I see the error "Insufficient encryption". If I use a similar app on android, it's able to show me those characteristics.

Is there a way to add encryption?

@Sinorm
Copy link
Contributor

Sinorm commented Mar 16, 2020

Have you paired with the device? Once your device is paired, the connection will be encrypted.

@adras
Copy link
Author

adras commented Mar 16, 2020

I just double checked, yes it is paired.

@adras
Copy link
Author

adras commented Mar 17, 2020

Any update on this? Even when the device is paired I get the error "Insufficient encryption" on some characteristics on my device.

@Gongxter
Copy link

Im having the same Issue, I once managed to get a secured connection with my BLE device, where everything worked fine. Once I tried to redo it it never worked again.
I tried to pair it via the Application as well as in the Windows settings. As far is I could figure this out these are the only options you have to pair a device in Windows.

Device I tried to connect to is a Philips Hue RGB Lamp.

**
image
**

any advice on how to set up the secure connection ?

@adras
Copy link
Author

adras commented Jan 26, 2021

Seems like

BluetoothLEDevice.ConnectionStatus.WasSecureConnectionUsedForPairing

is now no longer supported. But if you connect with:
DevicePairingResult result = await DeviceInfo.Pairing.PairAsync(DevicePairingProtectionLevel.Encryption)

then:

result.ProtectionLevelUsed
will be None

The default-mode which is normaly used upgrades the ProtectenLevel, if a higher one is supported. But it seems like those devices don't do that, why?

Same Philips Device as Gongxter has. You can also see: Read Not Permittted everywhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants