"CCCD Handle not found" error from characteristic.startNotifications()

You are reading a single comment by @Gordon and its replies. Click here to read the full conversation.

•

Gordon
Hmm... from the Nordic SDK:
```
/**@brief Invalid Attribute Handle. */
[#define](https://forum.espruino.com/search/?q=%23define) BLE_GATT_HANDLE_INVALID            0x0000

/**@brief First Attribute Handle. */
[#define](https://forum.espruino.com/search/?q=%23define) BLE_GATT_HANDLE_START              0x0001

/**@brief Last Attribute Handle. */
[#define](https://forum.espruino.com/search/?q=%23define) BLE_GATT_HANDLE_END                0xFFFF
```
So it looks a lot like the Bose device is actually using an out of spec handle. It does seem amazingly unlikely that anything would have a 0xFFFF handle, but then if we used that as an invalid handle we'd end up potentially breaking something that was ok.

What I've done for now is to modify the code so that if you manually set handle_cccd=0 as you were doing, startNotifications should then work.

So if you try a 'cutting edge' build now and you can get it working, let me know and i'll figure out another way of handling the CCCD discovery that will deal with a CCCD handle of 0.

About

Avatar for Gordon @Gordon started