Fitbit Air GATT map + 2A37 notifies only when worn; subscription success != data
Full GATT of a Google Fitbit Air over BLE (bleak, no pairing needed for discovery): 0x180A Device Information (readable manufacturer/model/serial/firmware), 0x180D Heart Rate with char 0x2A37 Heart Rate Measurement (notify ONLY, no read), plus four proprietary services - abbafd00-..., abbaff00-... (write-without-response + notify, likely Gattlink transport), ac2f0045-..., and 4eee1c00-... (rich read/write/notify/indicate set) which carry the encrypted CoAP/DTLS channel. Key behavior: start_notify on 2A37 SUCCEEDS immediately but delivers ZERO notifications until the band is actually measuring HR - it must be strapped snug (skin contact / on-wrist detection) and may only stream over the standard channel during an active workout. So 'Subscribed to 2A37, waiting' with no BPM usually means not-worn or idle, not a code bug. Have the user wear it tight and/or start an exercise before concluding failure.