First make sure that you have actually received the handle-value pair you are trying to access. If you suddenly no longer can find the handle-value pair, it could have fallen out of the “data cache”. If a value falls out of the "data cache", the device stops retransmitting it and you no longer have access to the value through the rbc_mesh_value_get() function. This can happen if you receive so many new handle-value pairs, that you no longer have enough memory for the old handle-value pair.
If you want to ensure that a handle-value pair is not forgotten, you can use the function rbc_mesh_persistence_set() to achieve this. Note that setting too many persistent values in the cache will reduce the framework's ability to retransmit non-persistent values, it is therefore recommended to be conservative about the usage of this flag. But, It is recommended that all values that the device intends to write to later are marked as persistent.
First make sure that you have actually received the handle-value pair you are trying to access. If you suddenly no longer can find the handle-value pair, it could have fallen out of the “data cache”. If a value falls out of the "data cache", the device stops retransmitting it and you no longer have access to the value through the rbc_mesh_value_get() function. This can happen if you receive so many new handle-value pairs, that you no longer have enough memory for the old handle-value pair.
If you want to ensure that a handle-value pair is not forgotten, you can use the function rbc_mesh_persistence_set() to achieve this. Note that setting too many persistent values in the cache will reduce the framework's ability to retransmit non-persistent values, it is therefore recommended to be conservative about the usage of this flag. But, It is recommended that all values that the device intends to write to later are marked as persistent.
