Locator Tag Testing Requirements

[Kai@Nessie]

I'm developing a FMDN locator tag and would like to use the locator tag sample in the connect SDK for testing.

Unfortunately, the requirements and exact procedure for running the sample are not sufficiently documented.

I understand that my Google account needs to be registered in order to use fast pair with debug models such as the model ID used in the sample. The sample's README suggests to complete the device proposal form in order to register the Google account accordingly. However, as part of this form I have to specify a model ID that I am supposed to create myself through the Google Nearby console. It also asks for many details about my product that are not yet known at this stage.

Could you please clarify exactly the requirements and procedure to use the locator tag sample with nordic's debug model ID starting with a 'clean' Google account?

[PaKa]

The device registration is a Google requirement and must be completed to be onboarded into the program. Without this completed you won't be able to use the developer keys present in the sample. This part of the process is owned by Google so you will need to complete it and if you need help then you will need to get that from the Google side, we do not have access to this portal from our end.

[Kai@Nessie]

OK but what's the benefit of providing Nordic's debug model ID/antispoofing key in the sample if I cannot use it without getting my own model ID? I have the feeling I'm still missing something.

I understand that this process is owned by Google and you have no control over it. Yet, this samle is part of the NCS and I think a precise documentation of the requirements and process would be beneficial to users. From my understanding it works like this:

In order to use the locator tag sample, you will first need to obtain your own model ID and anti-spoofing key from Google following the instructions here: https://developers.google.com/nearby/fast-pair/specifications/service/modelregistration#CreateModelId

Completing this process is only possible as a company with a Bluetooth Assigned Number.

Once you have obtained your model ID/anti-spoofing key, you have to submit the Fast Pair device proposal form: https://docs.google.com/forms/d/1-QLoVRkxZQQtk14lGvgs88laM9zC1p35pzYwXBLosFk/viewform

After completion, your Google Account should be unlocked for using FastPair with debug model ID devices.

Is this roughly how it works?

[PaKa]

So getting onboarded to do testing with the development keys didn't require you to get your own model ID and spoofing keys, this may have changed since last I checked though.

What is true is you need to have a project backing your request to get access and that will require you to be a Bluetooth member as far as I have seen as without being one, you can't register a finished design. That means that if you are a contractor then your customer will need to register the project.

We target to cover everything to do with our deliveries in our documentation. We will also try to cover what we can from external dependencies but for some of these they will have to be solved through Google as they do control the access to this information.