Google Locator Tag guidelines

[Wayne]

Hi,

There are two 'should' (as opposed to 'must') statements in the Fast Pair implementation guidelines for Locator Tags:

1. The Provider should reject normal Bluetooth pairing attempts and accept only Fast Pair pairing
2. The Provider shouldn't expose any identifying information information in an unauthenticated manner (e.g. names or identifiers).

However, I want to include the locator tag functionality into an existing custom BLE application in development that has an associated mobile app.

What's the opinions/thoughts on not following the guidelines?  (e.g. my device ModelId gets banned from the FMDN network?)

I appreciate that I may have answered my question and the authoritative source to the answer of my question is Google so as well as your thoughts I wondered if anyone in Nordic (or elsewhere) can point me to contact in Google that might be able to clarify/confirm that ignoring those 2 guidelines is perhaps a path to tears.

Thanks,

Wayne

[Charlie]

Hi Wayne,

Have you referred the following sample? The sample works as a Fast Pair Provider (one of the Fast Pair roles) and a simple HID multimedia controller.

Bluetooth Fast Pair: Input device (nordicsemi.com)

Best regards,

Charlie

[Wayne]

Hi,

I'm referring to the following sample and if not following 2 of the guidelines mentioned is a potential blocker to a consumer product: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/bluetooth/fast_pair/locator_tag/README.html#fast-pair-locator-tag

Thanks

Wayne