Unable to connect to "Find My Device" / FastPair locator_tag example

RE: Unable to connect to "Find My Device" / FastPair locator_tag example

Felix Shih — Fri, 01 Nov 2024 10:07:35 GMT

Sorry, I checked again, they use the different Model ID.

One is

 set(FP_MODEL_ID "0x2A410B")

and another is

set(FP_MODEL_ID "0x4A436B")

RE: Unable to connect to "Find My Device" / FastPair locator_tag example

Vidar Berg — Fri, 01 Nov 2024 08:11:26 GMT

Thank you, Wanye. Yes, the input device sample does not include the FMDN extension and will not attempt to join the Google Finder network. Therefore, the requirements differ.

RE: Unable to connect to "Find My Device" / FastPair locator_tag example

Wayne — Fri, 01 Nov 2024 08:09:09 GMT

Hi Felix,

I would have to make some guesses:

1. Ability to create more than one 'Series' (device) with the same ModeID, but with different device types, in the Google Nearby console,

and

2 The device type (HID, tag, audio, etc) information being obtained from the device BLE advertisement or a GATT service at runtime allows FMD to determine if it needs to validate that the Android account is allowed to use tags for dev/debug.

However, someone from Nordic or Google should be able to answer that definitively.

Thanks

Wayne

RE: Unable to connect to "Find My Device" / FastPair locator_tag example

Felix Shih — Fri, 01 Nov 2024 07:25:43 GMT

Hi Wayne ,

Since "input_device" and "locator_tag" samples use the same Model ID, why input_device accept by "Find My Device" google APP but locator_tag not?

RE: Unable to connect to "Find My Device" / FastPair locator_tag example

Vidar Berg — Thu, 17 Oct 2024 07:32:44 GMT

Thanks for the update. Yes, as Edvined mentioned in the other thread, your email must be added to the 'allow list' by Google for pairing to work.

RE: Unable to connect to "Find My Device" / FastPair locator_tag example

Wayne — Wed, 16 Oct 2024 23:19:01 GMT

I think this is relevant: https://devzone.nordicsemi.com/f/nordic-q-a/115212/fast-pair---locator-tag-example-failing/505377