Help & FAQ
Web Bluetooth is supported by Chromium-based browsers (Chrome, Edge, Brave, Opera, Vivaldi) on Android, Windows, macOS, ChromeOS, and Linux. It requires an HTTPS or localhost origin.
Safari on iOS/iPadOS does not support Web Bluetooth. Firefox does not either. There's no workaround from a web page.
Unlike a fitness tracker that advertises the Bluetooth SIG Heart Rate service, Amazfit watches wrap all of their data in a proprietary, encrypted Huami / Zepp protocol. Reading it requires:
- the per-device auth key from your Zepp account,
- a client-side implementation of that watch's protocol version.
Older Mi Band and early Amazfit models (Bip, Cor, GTR/GTS 1) use the classic Huami handshake, which is what Wristline attempts if you provide an auth key in Settings.
Zepp OS 4 devices — including the Amazfit T-Rex 3, GTR 4, Balance, Cheetah, Active — use a newer encrypted protocol. Wristline implements the 2021 handshake and is adding each Gadgetbridge-style endpoint parser in stages.
The community-maintained Gadgetbridge wiki documents ways to obtain the Huami auth key by intercepting the Zepp pairing traffic on your phone. This is a manual, technical process and it does not apply to newer Zepp OS 4 watches.
Wristline stores whatever key you paste only in this browser's local storage. It is never sent to any server.
Even without protocol support, you can:
- Pair the watch and see it in your browser's device chooser.
- Read manufacturer, model, firmware, hardware and serial.
- Read the current battery level and watch it change live.
- Enumerate every GATT service and characteristic the watch exposes — useful for developers investigating the protocol.