pair a real Find Hub tracker without Android

[baptx]

The README says "You can also send register your own ESP32- or Zephyr-based trackers, as described below." but is there something preventing to pair a real Find Hub tracker like Chipolo POP without Android?
This would be useful for people who don't use Android, for example with Linux on the PinePhone.

[P6g9YHK6]

i am currently digging this exact question but the answer is probably no
impossible due to how the device use your android's information's as decryption keys.

and it is possible to register your own tracker because we are aware of the advertisement token on it something that is not the case for commercially available tracker as the information is pre-filled in the device and without a complicated key extractions process, you are stuck

[baptx]

Another issue could be that Google may also ban users trying to use Find Hub without Android, like Facebook did for WhatsApp when they discovered the third-party software yowsup, in addition to sending cease and desist letters to developers.

At least what I am able to do right now is to track a Bluetooth tracker like Chipolo POP that is already registered to Find Hub, without Android even if the Bluetooth LE MAC address is changing randomly.

I had to extract the IRK of an Android smartphone that is not rooted by following instructions from https://www.home-assistant.io/integrations/private_ble_device/ :
"Alternatively, the IRK of an Android phone and/or secondary device can be obtained using Wireshark:

In developer settings on the Android phone, enable the “USB Debugging” and “Enable Bluetooth HCI snoop log” options.
Ensure a second Bluetooth device (e.g., smartwatch or earbuds) is unpaired.
Disable and re-enable Bluetooth on the phone ,then re-pair the secondary device.
Connect the Android phone to a computer with adb installed.
Establish an adb connection (adb connect...), then run the command: adb bugreport scanwatch.
In the generated scanwatch.zip file, locate and extract FS\data\misc\bluetooth\logs\btsnoop_hci.log.
Open btsnoop_hci.log in Wireshark and search for btsmp.id_resolving_key.
Select one of the frames and expand the “Bluetooth Security Manager Protocol.” The hex dump will show either the sending or receiving device IRK.
Reverse the value displayed. For example, if it is 763af6c7f7d94ad6c262158e2320544e, the IRK to use would be: 4e5420238e1562c2d64ad9f7c7f63a76."

Since there was no file FS\data\misc\bluetooth\logs\btsnoop_hci.log, I had to use the script https://android.googlesource.com/platform/packages/modules/Bluetooth/+/refs/heads/master/system/tools/scripts/btsnooz.py like mentioned on https://stackoverflow.com/questions/28445552/bluetooth-hci-snoop-log-not-generated/30352487#30352487:
./btsnooz.py scanwatch/bugreport-XXX.txt > BTSNOOP.log

I did not find btsmp.id_resolving_key in Wireshark but the IRK was in another place like mentioned on home-assistant/home-assistant.io#37615:
"From what I understand this information must be exchanged, so it has to be in those logs somewhere. I just attempted this with some AirPods and my up-to-date Pixel 8 Pro. I'm seeing a record with Info "Sent LE Add Device to Resolving List" -- it has a "Peer IRK" and "Local IRK" in the value of the command. I think Local IRK is my Pixel and Peer is the Airpods, the IRKs also need to be reversed before putting in HA. (byte by byte, not directly reversed)"

Once we got the peer IRK reversed, we can track the Bluetooth device with a tool like https://github.com/HackingDave/btrpa-scan:
btrpa-scan --irk XXX
We can also see the RSSI which could be used in a script to create out of range alerts, for example if we want to have an alarm if a luggage is being stolen.

Registering a device to Find Hub without Android could also be possible in an Android container like Waydroid with the official Find Hub app when there will be a solution for the Bluetooth passthrough issue:
waydroid/waydroid#155