nrf9160 nRF cloud doesn't pair, stuck at CLOUD_EVT_PAIR_REQUEST

[samo4]

Hello,

I have a Thingy91 which was previously successfuly paired to nrf cloud. I deleted the device from nrf cloud and provisioned new certificates from nrf cloud (and uploaded to device). Now the device won't pair.. no error. See part of the log below.

[0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_USER_ASSOCIATION_REQUEST

[0m<inf> asset_tracker: CLOUD_EVT_PAIR_REQUEST

[0m<inf> asset_tracker: Add device to cloud account.

[0m<inf> asset_tracker: Waiting for cloud association...

[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 1 result = 0

I also tried provisioning certificates with my custom prefix (and changing the NRF_CLOUD_CLIENT_ID_PREFIX), but the result is the same.

I'm currently using LTE-M, but I believe the original pairing was done with NbIOT. That being said.. I'm wondering how is NRFCloud able to support NBIOT (UDP?).

[samo4]

ok, I got new certificate from nrfcloud (with prefix nrf-), I uploaded certificates to modem and uploaded assset tracker to Thingy.

When first booting, this is what I got:

asset_tracker: CLOUD_EVT_DISCONNECTED: 
asset_tracker: Disconnected by the cloud.
asset_tracker: This can occur during initial nRF Cloud provisioning.
asset_tracker: LTE link disconnect
asset_tracker: RRC mode: Idle
asset_tracker: Shutdown modem

Then a reboot occured, and we have the same situation as before:

asset_tracker: CLOUD_EVT_PAIR_REQUEST
asset_tracker: Add device to cloud account.
asset_tracker: Waiting for cloud association...

[Albrecht Markus Schellenberger]

During:

asset_tracker: CLOUD_EVT_PAIR_REQUEST
asset_tracker: Add device to cloud account.
asset_tracker: Waiting for cloud association...

Have you been able to succesfully add your device to the nRF Cloud? Or do you get any error in the cloud?

Regards,

Markus

[samo4]

device doesn't show up in my cloud account, if that's what you mean. Also there are no errors except what you see in the logs above.

[Albrecht Markus Schellenberger]

Sorry for being unclear!

When you remove a device from the nRF Cloud, you have to add it again (as an LTE Device in this case), after it has been provisioned by the Asset Tracker application.

Regards,

Markus

[samo4]

That works, thank you. I feel that this whole interaction was me wasting your time.

Can I hijack this thread for a better understanding how nrfcloud works in case of NBIoT connection?

As far as I understand, nbiot means UDP connection and UDP connection can't have SSL? So if that is true, how does provisioning and authentication actually work?  Perhaps you can point me to a better explanation of the whole process?