The forthcoming version 2.2.0 of the Nearby SDK for embedded systems will introduce compatibility with Google’s innovative Find My Device (FMD) network, empowering billions of Android devices and accessories to locate each other in case of loss or misplacement.
This updated SDK will enable accessory manufacturers to incorporate support for Fast Pair (FP) and, in the near future, the Find My Device Network (FMD Network). By leveraging this technology, users will be able to easily locate their Android devices and accessories, providing an enhanced sense of security and peace of mind.
Release Notes for Nearby SDK for Embedded Systems (v2.2.0-embedded):
- Addition of Find My Device Network functionality
- Introduction of micro-ecc component
- Please note that although the changelog was briefly available, it was subsequently reverted, and the updated documentation is not yet accessible.
Additionally, the upcoming SDK release appears to offer support for unknown tracker alerts. Users will have the option to request different ringing volumes (default, low, medium, high) and utilize a physical button to activate the “EIK (Ephemeral Identity Key) recovery mode.” Clearing the EIK for a locator tag will result in the device being reset to its factory default settings.
To address safety concerns, Google’s announcement assures users that instructions will be provided on physically disabling the tracker and preventing it from updating its location.
If the platform supports “interleaving [Bluetooth] LE advertisements,” it can be configured to transmit both Fast Pair (FP) and Find My Device Network (FMD Network) advertisements at different intervals. Alternatively, the advertisements will be alternated if interleaving is not supported.
Furthermore, it has been discovered that there are distinct thresholds for low battery and critically low battery alerts (20% and 10% respectively). Moreover, the Find My Device Network advertisements can be deactivated for earbuds when they are placed in their case, allowing the case to advertise its own location.
(Note: Subsequent examination of newer commits suggests that the release may actually be version 2.0.0. Nevertheless, as an open-source project, the forthcoming updates are available for public scrutiny.)