NRF Cloud Connect Failed (-111) after reflashing

[AdrianT]

Hi,

I am currently extending the NRF Cloud multi service sample, thus I am constantly reflashing my NRF9161DK during development. However today, my device fails to connect to NRF Cloud. I am using the NRF Cloud Provisioning Service, with CoAP configuration.

The NRF Cloud Claimed Devices tab shows that the device status is provisioned. The Device Management -> Devices tab shows the device (which shows the old data I have transmitted during my previous testing). I have tried unclaiming the device and removing the device.

I have confirmed that my SIM is OK since I have flashed a different FW with LTE connectivity but doesn't use NRF Cloud. I have also flashed the unmodified Multi Service Sample and the issue still persists.

Attaching Logs:

[dejans]

Hi,

The issue might be related to constant reflashing of the board. If the modem has not been gracefully deinitialized (reset before deinitialization with +CFUN=0) several times (7 in case1 of modem firmware v1.3.1 or later), it enters reset loop. Could it be that modem reset loop restriction has been triggered in your case?

Best regards,
Dejan

[AdrianT]

Update:

I tried resetting the modem via Modem FW Update via programmer, and resetting the modem settings via XFACTORYRESET. But the issue is still present (device connection failure, error code -111)

BUT I am able to connect the device to NRF Cloud using the "Onboarding a device without the nRF Cloud Provisioning Service" method in multi service sample. Is it possible that the NRF Cloud provisioning service backend encountered an issue since I am constantly removing and adding the device to NRF Cloud?

[dejans]

Hi,

Is there any problem if you provision your device once and then reflash your application without provisioning service?

Provisioning with nRF Cloud provisioning service contains this sentence: "Within a few minutes of script completion, it should successfully connect to nRF Cloud and begin demonstrating the supported nRF Cloud features.". Have you tried to wait several minutes before connecting to nRF Cloud and using any of the nRF Cloud features?

Best regards,
Dejan

[dejans]

Hi,

You should take into account that the provisioning state of the device on the server side might be different than what is actually provisioned to the device, especially after resetting/reflashing. You can visit Claimed Devices on the nRF Cloud web portal, choose the device which has been reset and click on Reset on the right-hand side of the screen. This will reset the provisioning state of the device and cause all provisioning commands (onboarding commands) to be resent to the device.

Best regards,
Dejan

[AdrianT]

Hmm. My past attempts were to unclaim the device and then claim it again. Is the reset function different?

[AdrianT]

Yes, I have left the device powered for several hours, with the sample retrying every 30 seconds to connect to nrf cloud

[dejans]

Hi,

What is the result when you press on Reset to reset the provisioning state of the device?

Best regards,
Dejan