Okay so I got diagnosed with pre-diabetes a few months ago and instead of just staring at numbers on a glucometer screen I decided to build something. I have an Accu-Chek Guide and I want to pull the glucose readings off it via BLE into a web dashboard I built. I can see the GATT profile fine in nRF Connect. Service 0x1808, characteristic 0x2A18 with Notify, RACP at 0x2A52. All standard Bluetooth SIG glucose profile stuff. The problem is when I try to connect via Web Bluetooth in Chrome the authenticated pairing fails. The meter shows a 6 digit PIN on screen but Chrome never surfaces a PIN entry dialog. It just throws CONNECTION ATTEMPT FAILED. I tried enabling the experimental permissions backend flag and the experimental web platform features flag in chrome://flags and still nothing. Has anyone dealt with authenticated BLE pairing on a medical device through Web Bluetooth? Is this just a fundamental limitation of the API or am I missing something in the connection sequence?