Fast Pair - Locator Tag Example Failing

[Sri1998]

Hai,

I am trying the fast pair - locator tag example on my nRF52833. I am using SDK version 2.7.0. The code is compiled and flash properly. In the serial terminal getting the following error.

*** Booting nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using Zephyr OS v3.6.99-100befc70c74 ***
I: Starting Bluetooth Fast Pair locator tag example
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fa0
I: data wra: 0, 64
I: SoftDevice Controller build revision: 
I: d6 da c7 ae 08 db 72 6f |......ro
I: 2a a3 26 49 2a 4d a8 b3 |*.&I*M..
I: 98 0e 07 7f             |....    
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF52x (0x0002)
I: Firmware: Standard Bluetooth controller (0x00) Version 214.51162 Build 1926957230
I: No ID address. App must call settings_load()
I: Bluetooth initialized
I: Identity[0]: C4:C2:C5:C4:0E:C8 (random)
I: Identity[1]: EE:52:78:75:F6:39 (random)
I: HCI: version 5.4 (0x0d) revision 0x11fb, manufacturer 0x0059
I: LMP: version 5.4 (0x0d) subver 0x11fb
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 759 [s]
I: Fast Pair: prepared the advertising set
E: Invalid content of the Fast Pair partition
E: modules_init returned error -22
E: FMDN: bt_fast_pair_enable failed (err -22)
E: r0/a1:  0x00000004  r1/a2:  0xe000ed00  r2/a3:  0x20004fb8
E: r3/a4:  0x00000004 r12/ip:  0x00000000 r14/lr:  0x0002fe7b
E:  xpsr:  0x21000000
E: Faulting instruction address (r15/pc): 0x0001836c
E: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
E: Current thread: 0x20004368 (unknown)
E: Halting system

Can you help me enable the Locator Tag example in nRF52833.

[Edvin]

Hello,

Did you register your own user with Google to get your own set of keys, or did you use the default set? It looks like it is this part that it doesn't recognize as valid. 

Did you specify any keys when you built, like described here?

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/external_comp/bt_fast_pair.html#provisioning_registration_data_onto_device

Best regards,

Edvin

[Sri1998]

I am using default set provided by Nordic. So I didn't add any keys. While compiling it said 

 -------------------------------------------------------
    --- WARNING: Using demo Fast Pair Model ID and Fast ---
    --- Pair Anti Spoofing Key, it should not be used   ---
    --- for production.                                 ---
    -------------------------------------------------------

I flashed the merged.hex file now and the error is solved. But the device is not getting discovered in android phone, Installed Find My Device app and given permission for finding offline devices with network in all areas. After reading the documentation I have clicked Button 1 to start fast pair advertising. It says "I: Fast Pair: advertising in the discoverable mode" in the terminal. I am able to find it in the nRF Connect scanner page. Not getting any pop-up for connecting to my devices. 

Regards,

Sri

[Edvin]

Hello Sri,

Sorry for not replying to your ticket today. I will ask around tomorrow about the behavior of Fast Pair, as I have not tried it before. It could be that it doesn't give the full experience with demo ID and key (as that would be an easy way to spam a lot of users, I would imgaine).

Best regards,

Edvin

[Sri1998]

Hello Edvin,

Thank you. I'd like to confirm if the example code works on my nRF52833 so that I can obtain my own Model ID and Anti-Spoofing Key.

Best Regards,

Sri

[Edvin]

Hello,

It seems like you do need a test account with Google:

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/bluetooth/fast_pair/locator_tag/README.html#testing

I thought I read that somewhere, but I couldn't find it again, but there it is. Your account, which will be listed with Google, needs to be enabled by Google in order to test uncertified devices.

Best regards,

Edvin

[Wayne]

I seem to recall the device proposal form requires a Bluetooth SIG registered company ID, not something I, or many devs, have if an independent developer. 

Is there anyway around this?

[Edvin]

That is something you would have to ask Google about. I am not sure, and unfortunately, it is not something I can do anything about either. 

Best regards,

Edvin

[Wayne]

I just wanted to replicate a comment I made just now on another ticket here for reference.

It might be worth highlighting in the Nordic documentation that the locator_tag sample has a high prerequisite bar in order to use for mere mortal independent developers and hobbyists. 

It appears to me, but I may be wrong, in order to get a Model ID you need to have legitimate access to a Bluetooth SIG company name when registering a device in the Google Near By developer console and only then will your email be added to the 'allow list',

Thanks

Wayne

[Wayne]

I've reached out to the Google 'nearby-devices-partners-contact' email.   I will report back.

[Sri1998]

Thank you, Wayne. I look forward to your response.

[samkris]

Hi,

Iam also facing same issue and not able to register with Google without signing NDA and all.Iam also using nrf52840 DK.any body got any solution or get the solution up and running?

[Wayne]

As has been highlighted in another thread and with a certain level of obviousness in hindsight:

This is not for 'individual' developers or hobbyists.  

You have to be registered with the Bluetooth SIG as a company* in order to get a company assigned number which will then let you select your company in the drop-down list on the Nearby console when creating a new Device & associated Model ID.

Joining as an Adopter Member (no fee) is ok.

There is a delay between obtaining a company number and it being imported by Google into the Nearby console list, but an email to the Google nearby-devices-partners-contact to let them know can help, thanks Jovi!

I've not yet had a chance to revisit the locator_tag example and have all my Google account and FMD setup ducks in a row.

*I signed up my Ltd company, I recall there were other 'legal entity' options, so your YMMV