We use the device shadow "desired" section to send configuration params to the device. The device processes and accepts the params and then returns them in the "reported" section.
This generally works as expected.
However, sometimes at some point the reported section in the nRF Cloud stops reflecting the update and shows the old values.
Example: Lets say the old value of "param" is "old".
The nRF Cloud sends a new "desired" section to the device:
"desired": {
"config": {
"param": "new"
}
}
The device accepts "param": "new", processes the change internally, and then returns
"reported" : {
"config": {
"param": "new"
}
}
However, in the nRF Cloud reported section "param" remains "old". It seems the new "reported" section is not processed by the nRF Cloud shadow.
We have not found a trigger for this. But is happens on multiple devices fairly regularly.
Have you seen this before? Do you have advice how to proceed?
Thanks
