Issue connection for "Google find my device"

[yousseflxn]

Hello

Environment:

• nRF Connect SDK Version: v2.7.0-rc2
• Board: nRF52840 DK
• Operating System: Windows 10
• Android Phones: Samsung S20 (Android 13) / POCO F3 (Android 13)

Description:

I am using the locator_tag example in the nRF Connect SDK to test the "Google Find My Device" feature. The project was built with the default MODEL_ID and ANTI_SPOOFING_KEY.

When running the project on the nRF52840 DK, I receive the connection pop-up from the "Google Find My Device" application and start the connection process.

However, I consistently encounter an issue connecting from the app (see attached picture).

I have tested with both my phones, and the "Find My Device" feature is active and functioning on both devices with different accounts. Despite this, the issue persists.

Below are the logs from the nRF52840 DK, which seem to be normal, with no warnings or errors except for the "Key discarded (timeout)" message.

nRF52840 DK Logs:

I: Settings loaded
I: FMDN: setting battery level to 100 %
I: FMDN level: Normal
I: DULT level: Full
I: Fast Pair: RPA expired
I: Fast Pair: setting RPA timeout to 775 [s]
I: Fast Pair: prepared the advertising set
D: FMDN State: TX power set to 0 [dBm]
D: FMDN State: enabled
I: DULT enabled
D: Fast Pair is enabled
I: FMDN: state changed to unprovisioned
I: Fast Pair: advertising in the discoverable mode
I: Sample has started
I: Connected
D: Personalized Name is empty
D: Personalized Name was not notified (Key-based Pairing)
D: Key-based Pairing write: res=80 conn=0x200022b8
D: Account Key stored
I: Fast Pair: Account Key write
I: Fast Pair: automatically switched to non-discoverable advertising mode
I: Fast Pair: advertising inactive due to an active connection
D: Account Key write: res=16 conn=0x200022b8
D: Beacon Actions GATT Read Request
D: Beacon Actions: challenge-response enabled for the next write:
D: f5 e0 1c a0 4a e5 77 14 |....J.w.
D: Beacon Actions read: res=9 conn=0x200022b8
I: Beacon Actions CCCD write, handle: 0, value: 0x0001
D: Beacon Actions GATT Write Request:
D: 01 08 6e 59 a1 7d 29 c1 |..nY.}).
D: 13 41 |.A
D: Beacon Actions: consuming random nonce read operation
D: Beacon Actions response:
D: 01 09 13 bb 57 8c 8b 79 |....W..y
D: c4 d7 02 |...
D: Beacon Actions write: res=10 conn=0x200022b8
I: Beacon Actions CCCD write, handle: 0, value: 0x0000
I: Key discarded (timeout)
I: Performing reset to factory settings...
D: FMDN State: disabled
I: DULT reset completed
D: Fast Pair is disabled
I: Fast Pair: automatically switched to disabled advertising mode
I: Fast Pair: advertising inactive due to an active connection
I: Factory Reset: resetting Bluetooth identity within the factory reset
I: Fast Pair: RPA expired
I: Fast Pair: the last timeout has occurred 309 [s] ago
I: Fast Pair: setting RPA timeout to 751 [s]
I: Fast Pair: prepared the advertising set
D: FMDN State: TX power set to 0 [dBm]
D: FMDN State: enabled
I: DULT enabled
D: Fast Pair is enabled
I: Reset to factory settings has completed
I: FMDN: state changed to unprovisioned
I: Please press a button to put the device in the Fast Pair discoverable advertising mode after a reset to factory settings
I: Disconnected (reason 22)
I: Fast Pair: advertising in the disabled mode
D: FMDN Clock: storing the last value: 600 [s]

Questions:

1. Is the behavior observed in the nRF52 logs normal when connecting to a new Android phone?
2. Could the issue be related to using the default debug MODEL_ID and ANTI_SPOOFING_KEY provided in the sample?

Thank you for your assistance.

Youssef

[luckbear]

Hi，Youssef

I would like to ask what ID you are using. After I use 0x4A436B，fast pair cannot get the device. Has it been refined?

[yousseflxn]

Hi

For me, I also used model id: 0x4A436B, I always got Issue Connecting pop-up

[Amanda Hsieh]

You must configure the Android device to include the debug results while displaying the nearby Fast Pair Providers. 

[luckbear]

Hi Amanda,

Thank you for your replay.

After checking, the debug results and developer mode are both turned on, but I still can't get the device to fast pair function. The code version is v2.7.0-rc2

*** Booting nRF Connect SDK v2.7.0-rc2-b2d45030365f ***
*** Using Zephyr OS v3.6.99-f047959a650c ***
I: Starting Bluetooth Fast Pair locator tag example
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, ec8
I: data wra: 0, 150
I: SoftDevice Controller build revision: 
I: 6d 38 c5 3b 03 9c 98 a4 |m8.;....
I: 87 09 7c fd 21 77 4e c1 |..|.!wN.
I: 0e a7 52 bd             |..R.    
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF52x (0x0002)
I: Firmware: Standard Bluetooth contr*** Booting nRF Connect SDK v2.7.0-rc2-b2d45030365f ***
*** Using Zephyr OS v3.6.99-f047959a650c ***
I: Starting Bluetooth Fast Pair locator tag example
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, ec8
I: data wra: 0, 150
I: SoftDevice Controller build revision: 
I: 6d 38 c5 3b 03 9c 98 a4 |m8.;....
I: 87 09 7c fd 21 77 4e c1 |..|.!wN.
I: 0e a7 52 bd             |..R.    
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF52x (0x0002)
I: Firmware: Standard Bluetooth controller (0x00) Version 109.50488 Build 2560361275
I: No ID address. App must call settings_load()
I: Bluetooth initialized
I: Identity[0]: E4:A7:2E:D6:3F:77 (random)
I: Identity[1]: D6:B4:45:6E:A0:78 (random)
I: HCI: version 5.4 (0x0d) revision 0x11f3, manufacturer 0x0059
I: LMP: version 5.4 (0x0d) subver 0x11f3
I: Settings loaded
I: FMDN: setting battery level to 100 %
I:      FMDN level: Normal
I:      DULT level: Full
I: Fast Pair: RPA expired
I: Fast Pair: setting RPA timeout to 799 [s]
I: Fast Pair: prepared the advertising set
D: FMDN State: TX power set to 0 [dBm]
D: FMDN State: enabled
I: DULT enabled
D: Fast Pair is enabled
I: FMDN: state changed to unprovisioned
I: Fast Pair: advertising in the discoverable mode
I: Sample has started

Then， My phone（pix7 android 14） interface is unresponsive, Is this in line with expectations?

I refer to https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline （1. Preparation for Certification）

[Amanda Hsieh]

Please move to NCS v2.7.0 which was released last week.  

Do you register the account with Google for the FMDN feature?

Please see the note in the Testing section:

If the test Android device uses a primary email account that is not on Google’s email allow list for the FMDN feature, testing steps will fail at the FMDN provisioning stage for the default debug (uncertified) device model. To be able to test with debug device models, register your development email account by completing Google’s device proposal form. You can find the link to the device proposal form in the Fast Pair Find My Device Network extension specification.

[luckbear]

Thks Amanda，I updated my code to NCS v2.7.0, but the result is still the same.

I would like to ask two questions：

1.Can Fast Pair recognize FMDN only after submitting the device registration application? Does enabling the FMDN function affect the connection of the fast pair?

2.Can the ID provided by Nordic Demo be used by the developer if his account is not registered in fmdn?

[Amanda Hsieh]

luckbear said:

Can Fast Pair recognize FMDN only after submitting the device registration application?

Yes, please contact Google. 

luckbear said:

Does enabling the FMDN function affect the connection of the fast pair?

It affects this sample Bluetooth Fast Pair: Locator tag. Please see the note in the Testing. 

luckbear said:

Can the ID provided by Nordic Demo be used by the developer if his account is not registered in fmdn?

No, please see the note in the Testing. 

[luckbear]

Thank you very much for your detailed answer。