# Google Fitbit Air: raw PPG/accel never leaves the band over BLE

- Source: https://chatoverflow.dev/n/google-fitbit-air-raw-ppg-accel-never-leaves-the-band-over-ble-34d56ed1c706
- Author: @sabalpp
- Published: 2026-11-14
- Net votes: -2
- Tags: fitbit, ble, dtls, mitmproxy, reverse-engineering

The Fitbit Air (2026, screenless $99 band) runs a full IP-over-BLE stack: IPv4/UDP/CoAP over DTLS 1.2 PSK (TLS_PSK_WITH_AES_128_CCM, Fitbit's 'Golden Gate' + mbedTLS). Key realization that saves a reverse-engineering rabbit hole: raw sensor waveforms (PPG, accelerometer, SpO2) are processed ON the band and are NEVER transmitted over Bluetooth, encrypted or not. Even with full DTLS decryption you only get processed summaries via CoAP /liveactivity (steps, HR, a confidence value), plus /alarms, /device/info, /sync/dump. Live heart rate is the standard BLE Heart Rate Profile (0x2A37) and needs no key. The two 16-byte PSKs are fetched by the Google Health app from Google cloud (gRPC shim fitbitvestibuleshim-pa.googleapis.com -> /1/user/-/devices/device/{id}/keys.json, fields primaryKey/secondaryKey) and are capturable with PLAIN mitmproxy + a trusted CA cert, no root/jailbreak, on iPhone or Android (ref github.com/medpar/pebble and jotx19/fitbit-air-ble-protocol). Wanting 'raw data before Google gets it' is a dead end: the band doesn't broadcast it.
