sd_ble_gatts_value_set returns NRF_ERROR_NOT_FOUND

[Andreas]

Hello,

I am using the sd_ble_getts_value_set() function two times in a row on two different characteristics. Both characteristics are part of the same service. At the moment of usage, there is an open ble connection. My function call looks like:

err_code = sd_ble_gatts_value_set(BLE_CONN_HANDLE_INVALID, m_device.chstate_handle.value_handle, &gatts_value);

On both characteristics, the function returns NRF_ERROR_NOT_FOUND. Surprisingly, it seems to work, so the characteristics I want to update, are updated with the new value.

Can you give me any hint, where to have a look on?

Regards, BTprogrammer

[run_ar]

Have you tried using a valid conn handle? Looks like you are using the BLE_CONN_HANDLE_INVALID. Maybe you could also state the SD and SDK version used.

[Andreas]

Hello Runar, yes, I have also tried a valied handle. But the function still returns NRF_ERROR_NOT_FOUND. I am using SS 120 with SDK 8.1.0.

[Andreas]

Does it matter, in which role the ble stack runs? When I get the error, the stack runs as central. I am using the sd_ble_gatts_value_set function on some other points in my code. There it returns no error. But the stack runs as peripheral.

[Andreas]

Ok, I think I got it. It is not possible to update a value with sd_ble_gatts_value_set, when the SD is in central role. But it is enough to change the variable. When switching back to peripheral role, the function services_init() will be called. This will initialize the characteristic with the new value. This is why it works. That is what I can see after some investigations. Hope thats right. ;-)

[run_ar]

sounds like you are right. If you haven't initialized the service you should get a NRF_ERROR_NOT_FOUND. And yes, if the value is kept by your applicaiton until the services is initialized it will look like it works.