How does google "chrome://bluetooth-internals" bluetooth tool show Read Encrypted and Write Encrypted

Dear support team,
We need to show support for Read Encrypted and Write Encrypted on the "chrome://bluetooth-internals" Bluetooth tool, as shown below:

I modified it based on the \examples\ble_peripheral\ble_app_gls example, but it was not successful. How to modify it?

BR,

Zero

Parents
  • Okay, that makes things harder I guess. Can you please confirm that you did indeed bond the device to the computer before checking the characteristics? The Bluetooth LE spec requires devices to be bonded before they can successfully support encrypted transmissions to read/write characteristics. 

    Do you see any error messages when trying to debug this on the nRF side? I would assume you get a "GATT_INSUFFICIENT_ENCRYPTION" error for example when trying to read encrypted characteristics if the device isn't bonded or encryption isn't set correctly.

    Best regards,

    Simon

  • Dear Simon,

    I'm seeing the same on my end as well,

    The device has been paired and bound on Win. Didn't your test also fail?

    Best regards,

    Zero

  • Yes, I tested with the ble_app_hrs and ble_app_gls samples as is, but haven't made any changes to the sample on my end. I made sure I paired and bonded with the device, but did not make any changes to the characteristics/services like you say you have. And I don't know what this Chrome tool requires for these boxes to be checked, so I don't have any good ideas I'm afraid.

    Do you see any error messages when trying to debug this on the nRF side?

    Best regards,

    Simon

Reply
  • Yes, I tested with the ble_app_hrs and ble_app_gls samples as is, but haven't made any changes to the sample on my end. I made sure I paired and bonded with the device, but did not make any changes to the characteristics/services like you say you have. And I don't know what this Chrome tool requires for these boxes to be checked, so I don't have any good ideas I'm afraid.

    Do you see any error messages when trying to debug this on the nRF side?

    Best regards,

    Simon

Children
Related