Skip to main content
Associate III
January 30, 2025
Solved

Connection with Garmin devices with privacy enabled

  • January 30, 2025
  • 1 reply
  • 543 views

Our product is based on an STM32WB5MM. On the STM32WB, we have privacy enabled and use the filter/acceptance list.

When the filter/acceptance list is not enabled, we want the device to be able to connect to a Garmin device. Unfortunately, the device does not appear in the scan results. We’ve confirmed that when privacy is disabled, the device appears in the results without issues. This Garmin incompatibility with BLE devices using resolvable private address (RPA) is known (https://forums.garmin.com/developer/connect-iq/i/bug-reports/not-all-ble-devices-found-by-scanning?CommentId=0740ab84-c44f-49a2-a165-5aff687d5435).

My question is: is it possible to keep privacy enabled while advertising with a static random address instead of an RPA?

If this is not possible, what workaround could we use to allow both RPA-compatible and non-RPA-compatible devices to connect?

Thanks in advance.

Best answer by STTwo-32

Hello @thealbertdev 

As you can see on the description of the ACI_GAP_SET_DISCOVERABLE parameter description (table 173 of the AN5270) we have: "Own address type: if Privacy is disabled, the address can be public or static random, otherwise, it can be a resolvable or a non-resolvable private address". So, we can keep privacy enabled only will using RPA or NRPA as Own_Address_Type.

For any workaround, I think this should be related to the central device (the Garmin device) and not our side.

Best Regards.

STTwo-32

1 reply

STTwo-32
STTwo-32Best answer
Technical Moderator
February 28, 2025

Hello @thealbertdev 

As you can see on the description of the ACI_GAP_SET_DISCOVERABLE parameter description (table 173 of the AN5270) we have: "Own address type: if Privacy is disabled, the address can be public or static random, otherwise, it can be a resolvable or a non-resolvable private address". So, we can keep privacy enabled only will using RPA or NRPA as Own_Address_Type.

For any workaround, I think this should be related to the central device (the Garmin device) and not our side.

Best Regards.

STTwo-32