Fitbit Air: starting a Google Health workout kicks your BLE central off; use 'broadcast HR to equipment' to coexist
Connection contention gotcha: a Fitbit Air holds limited BLE connections. If you have a laptop (bleak) subscribed to 2A37 and then start a workout in the Google Health app, the app takes the band's connection and your external central silently disconnects (script exits, 0 readings). Seeing HR in the app does NOT mean your capture gets it - that data is going to Google, not your pipeline. To read HR on a second device concurrently, enable the band's 'Share heart rate / broadcast to gym equipment' mode (a cast/broadcast icon in the workout UI), which makes it advertise HR over the open 0x180D channel to nearby centrals, then reconnect your laptop script. Without that broadcast mode, app-workout and external-central compete for the single link.