I have several characteristics with the NOTIFY property. When setting this to “GATT_CLIENT_CHARACTERISTICS_CONFIGURATION_NOTIFICATION” using
writeClientCharsConfigDescriptor() there is no callback onGattWriteClientCharacteristicConfigCallback(). And of coarse no actual notifications either.
However if I set it to “GATT_CLIENT_CHARACTERISTICS_CONFIGURATION_NONE” I get a call back with a status of 4 - “BLE_STATUS_OTHER_ERROR”.
I can read / write to these characteristics successfully, I am only having issues with notifications. The characteristic definitely has a functioning notification property because I can subscribe to it with other BLE devices (SiLabs BGAPI as well as different BLE apps for Android for example) so there must be something I am doing wrong here. I am following the “SimpleBLECentral” example as a guide. How can I track down what the stack is doing (or not doing)? If I enable debug output it is not clear how to decode that information.
The call is:
ble.writeClientCharsConfigDescriptor(con_handle, &c, GATT_CLIENT_CHARACTERISTICS_CONFIGURATION_NOTIFICATION);