I need a immediate response on this.
I am facing a persistent issue with shadow delta requests on my nRF9151-based application using nRF Cloud over CoAP since this morning.
Setup details:
-
Device: nRF9151 custom board
-
SDK Version: 2.7.0
-
Modem Firmware: 2.0,1
-
Protocol: NBIoT with CoAP
-
SIM: Jio(India)
My application was working fine until recently, with no firmware or configuration changes.
Observed behavior:
-
Shadow delta request triggers
+CSCON
transition to connected mode. -
Immediately gets CoAP response code 4.06 (Not Acceptable).
-
Error log:
<err> nrf_cloud_coap: Unexpected result code: 4.06
<err> shadow_support_coap: Failed to request shadow delta: 134
Network attachment and registration are stable:
AT+CGATT? +CGATT: 1 AT+CEREG? +CEREG: 5,5,"C014","0000C092",9,,,"00001010","00000011"
The issue is only with shadow delta requests. Other nRF Cloud operations remain unaffected.
Troubleshooting performed so far:
-
Deleted and re-added the device on nRF Cloud → temporarily works, but issue returns after subsequent shadow delta requests.
-
Confirmed no recent firmware changes.
-
Verified SIM and network connectivity are stable, data is flowing, RRC state transitions are normal.
Questions:
-
What could cause CoAP 4.06 Not Acceptable specifically for shadow delta requests while all other operations remain functional?
-
Has there been any recent change to nRF Cloud CoAP shadow service regarding Accept or Content-Format options?
-
Could an invalid shadow document cause this persistent rejection? If so, what is the recommended approach to sanitise or reset shadow state without deleting and re-adding the device?