LWM2M Errors when first connecting to server - Normal behavior?

[hubert_11]

Hi, 

I'm using the asset tracker example code with the LWM2M overlay to connect to the Coiote server.

This seems to work fine, and messages do get through. But when booting the device I always get several errors as shown below. Is this normal behavior for a first time connection process?

*** Booting nRF Connect SDK 3758bcbfa5cd ***
[00:00:00.271,270] <inf> at_host: UART check failed: 12. Dropping buffer and retrying.
[00:00:00.282,135] <inf> app_event_manager: APP_EVT_START
[00:00:00.511,749] <inf> app_event_manager: MODEM_EVT_INITIALIZED
[00:00:00.647,613] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTING
[00:00:00.710,296] <inf> lwm2m_firmware: Image is confirmed OK
[00:00:01.324,432] <inf> app_event_manager: DATA_EVT_CONFIG_INIT
%CESQ: 60,3,14,2
+CEREG: 2,"56BD","019B5501",7
[00:00:02.229,003] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
+CSCON: 1
+CGEV: ME PDN ACT 0,0
[00:00:03.768,615] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTED
[00:00:03.769,622] <inf> net_lwm2m_rd_client: Start LWM2M Client: urn:imei:xxxx
[00:00:03.770,141] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:xxxx' with client lifetime 43200 using server object 0
+CNEC_ESM: 50,0
%MDMEV: SEARCH STATUS 2
+CEREG: 5,"56BD","019B5501",7,,,"00001111","11100000"
+CEDRXP: 4,"0000","0000","0000"
%XTIME: "80","42609121624280","01"
[00:00:03.983,581] <inf> app_event_manager: MODEM_EVT_LTE_PSM_UPDATE
[00:00:03.984,191] <inf> app_event_manager: MODEM_EVT_LTE_EDRX_UPDATE
[00:00:03.984,771] <inf> app_event_manager: DATA_EVT_DATE_TIME_OBTAINED
[00:00:04.068,054] <inf> lwm2m_security: Need to write credentials, requesting LTE and GNSS offline...
[00:00:04.068,572] <inf> app_event_manager: CLOUD_EVT_LTE_DISCONNECT
+CGEV: ME PDN DEACT 0
[00:00:04.163,146] <inf> app_event_manager: MODEM_EVT_LTE_DISCONNECTED
+CEREG: 0
[00:00:04.263,427] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
+CGEV: ME DETACH
%CESQ: 255,0,255,0
+CSCON: 0
[00:00:07.849,975] <inf> lwm2m_security: Requesting LTE and GNSS online
[00:00:07.850,494] <inf> app_event_manager: CLOUD_EVT_LTE_CONNECT
[00:00:07.892,150] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTING
%CESQ: 61,3,18,2
+CEREG: 2,"56BD","019B5501",7
[00:00:09.451,354] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
+CSCON: 1
[00:00:09.852,111] <err> net_lwm2m_engine: Failed to enable TLS_DTLS_CID: -22
[00:00:09.852,569] <err> net_lwm2m_engine: Cannot connect UDP (-114)
[00:00:09.852,813] <err> net_lwm2m_rd_client: Cannot init LWM2M engine (-114)
[00:00:09.853,149] <err> net_lwm2m_rd_client: sm_do_network_error, retries 0
[00:00:09.853,393] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:xxxx' with client lifetime 43200 using server object 0
[00:00:09.853,698] <err> net_lwm2m_message_handling: Unable to resolve address
[00:00:09.853,729] <err> net_lwm2m_rd_client: Cannot init LWM2M engine (-2)
[00:00:09.853,942] <err> net_lwm2m_rd_client: sm_do_network_error, retries 1
%CESQ: 56,2,16,2
%CESQ: 52,2,11,1
[00:00:10.854,827] <err> net_lwm2m_rd_client: sm_do_network_error, retries 1
[00:00:10.855,072] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:xxxx' with client lifetime 43200 using server object 0
[00:00:10.855,407] <err> net_lwm2m_message_handling: Unable to resolve address
[00:00:10.855,407] <err> net_lwm2m_rd_client: Cannot init LWM2M engine (-2)
[00:00:10.855,743] <err> net_lwm2m_rd_client: sm_do_network_error, retries 2
+CGEV: ME PDN ACT 0,0
[00:00:11.447,906] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTED
+CNEC_ESM: 50,0
%MDMEV: SEARCH STATUS 2
+CEREG: 5,"56BD","019B5501",7,,,"00001111","11100000"
%XTIME: "80","42609121621380","01"
%CESQ: 47,2,12,1
[00:00:11.759,948] <inf> app_event_manager: MODEM_EVT_LTE_PSM_UPDATE
%CESQ: 52,2,12,1
[00:00:12.855,682] <err> net_lwm2m_rd_client: sm_do_network_error, retries 2
[00:00:12.855,957] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:xxxx' with client lifetime 43200 using server object 0
[00:00:12.938,385] <err> net_lwm2m_engine: Failed to enable TLS_DTLS_CID: -22
[00:00:13.376,739] <inf> net_lwm2m_engine: Connected, sock id 2
[00:00:13.853,363] <inf> net_lwm2m_rd_client: Registration Done (EP='urn:imei:xxxx')
[00:00:13.854,156] <inf> app_event_manager: CLOUD_EVT_CONNECTED

So the specific error that I'm talking about are:

[00:00:09.852,111] <err> net_lwm2m_engine: Failed to enable TLS_DTLS_CID: -22
[00:00:09.852,569] <err> net_lwm2m_engine: Cannot connect UDP (-114)
[00:00:09.852,813] <err> net_lwm2m_rd_client: Cannot init LWM2M engine (-114)
[00:00:09.853,149] <err> net_lwm2m_rd_client: sm_do_network_error, retries 0
[00:00:09.853,393] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:xxxx' with client lifetime 43200 using server object 0
[00:00:09.853,698] <err> net_lwm2m_message_handling: Unable to resolve address
[00:00:09.853,729] <err> net_lwm2m_rd_client: Cannot init LWM2M engine (-2)
[00:00:09.853,942] <err> net_lwm2m_rd_client: sm_do_network_error, retries 1
%CESQ: 56,2,16,2
%CESQ: 52,2,11,1
[00:00:10.854,827] <err> net_lwm2m_rd_client: sm_do_network_error, retries 1
[00:00:10.855,072] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:xxxx' with client lifetime 43200 using server object 0
[00:00:10.855,407] <err> net_lwm2m_message_handling: Unable to resolve address
[00:00:10.855,407] <err> net_lwm2m_rd_client: Cannot init LWM2M engine (-2)
[00:00:10.855,743] <err> net_lwm2m_rd_client: sm_do_network_error, retries 2

Appart from those error during the first connection I also get some errors during use after that, when it tries to connect again. Is this also normal or something that I should look into?

[00:05:13.858,337] <err> net_lwm2m_location_assist: Temporary error in location services retry scheduled
[00:05:13.858,337] <err> cloud_module: cloud_wrap_cloud_location_send, err: -120
+CSCON: 0
%XT3412: 46799999
%XT3412: 0
+CSCON: 1
%CESQ: 59,2,13,1
+CSCON: 0
%XT3412: 46799999
%XT3412: 0
+CSCON: 1
%CESQ: 53,2,11,1
%CESQ: 58,2,10,1
+CSCON: 0
%XT3412: 46799999
[00:06:14.030,426] <err> net_lwm2m_location_assist: No response error in location services
[00:06:14.030,487] <err> net_lwm2m_obj_gnss_assistance: Result code 2
%CESQ: 255,0,255,0
%CESQ: 61,3,14,2
%MDMEV: SEARCH STATUS 2
%XT3412: 0
+CSCON: 1
%CESQ: 56,2,12,1
+CSCON: 0
%XT3412: 46799999
%CESQ: 255,0,255,0
[00:07:46.751,037] <wrn> net_lwm2m_rd_client: Registration Update Timeout
[00:07:46.751,129] <inf> lwm2m_rai: RAI disabled
[00:07:46.751,159] <wrn> lwm2m_integration: LWM2M_RD_CLIENT_EVENT_REG_TIMEOUT
[00:07:46.751,800] <inf> app_event_manager: CLOUD_EVT_CONNECTING
[00:07:46.759,429] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:350457794446409' with client lifetime 43200 using server object 0
%CESQ: 63,3,19,2
%MDMEV: SEARCH STATUS 2
%XT3412: 0
+CSCON: 1
%CESQ: 56,2,12,1
[00:07:47.666,717] <err> net_lwm2m_engine: Failed to enable TLS_DTLS_CID: -22
[00:07:47.779,113] <inf> net_lwm2m_engine: Connected, sock id 2
[00:07:47.942,321] <inf> net_lwm2m_rd_client: Registration Done (EP='urn:imei:350457794446409')
[00:07:47.945,068] <inf> lwm2m_rai: RAI enabled
[00:07:47.945,434] <inf> app_event_manager: CLOUD_EVT_CONNECTED
[00:07:48.178,253] <inf> net_lwm2m_rd_client: Update callback (code:2.4)
[00:07:48.178,375] <inf> net_lwm2m_rd_client: Update Done
[00:07:48.221,069] <inf> lwm2m_rai: Ongoing traffic, RAI disabled
+CSCON: 0
%XT3412: 46799999
%CESQ: 60,3,17,2
[00:08:11.398,925] <err> net_lwm2m_location_assist: No response error in location services
[00:08:11.398,956] <err> net_lwm2m_obj_ground_fix: Result code 2

[dejans]

Hi,

Which board do you use?

Which SIM card do you use? Which network does your device connect to?

Can you provide a modem trace? You can follow the guide for capturing modem traces.

Best regards,
Dejan

[hubert_11]

Hi Dejan,

I'm using a Thingy 91, version 1.6.0.

Its using an iBASIS eSim, connecting to Vodafone NL.

This is the modem trace:

trace-2024-06-27T11-34-45.200Z.mtrace

Thank you for your time!

[dejans]

Hi,

Thank you for additional information.

Which NCS version do you use?

You said that errors appear when the device boots. Does the device boot on its own or is your action/application that is causing the device to boot? Are there any reboots?

Did you make any changes to asset tracker v2 sample?

Best regards,
Dejan

[hubert_11]

I'm using toolchain and SDK 2.6.1.

I tested with slightly altered software and a completely stock asset tracker. Both give me the same errors.

When I say booting, I mean just powering it on. It then seems to give multiple errors upon first connecting with the LWM2M server. It does not reboot and does seem to connect after a while, but having errors still seems like a potential problem to me.

There are no reboots, but it does give me additional errors when it tries to connect to the server again after sleeping for a while (both are mentioned in the first post of this thread, too).


For example, this is the fully stock asset tracker with the LWM2M overlay, booting and connecting after having been manually turned off:

*** Booting nRF Connect SDK 3758bcbfa5cd ***
[00:00:00.272,003] <inf> app_event_manager: APP_EVT_START
[00:00:00.501,983] <inf> app_event_manager: MODEM_EVT_INITIALIZED
[00:00:00.629,028] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTING
[00:00:00.689,117] <inf> lwm2m_firmware: Image is confirmed OK
[00:00:01.300,384] <inf> app_event_manager: DATA_EVT_CONFIG_INIT
[00:00:01.952,636] <inf> app_event_manager: SENSOR_EVT_MOVEMENT_ACTIVITY_DETECTED
%CESQ: 66,3,16,2
+CEREG: 2,"7EF6","011ED70D",7
[00:00:03.854,614] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
+CSCON: 1
%CESQ: 66,3,22,3
+CGEV: ME PDN ACT 0,0
[00:00:04.591,613] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTED
[00:00:04.592,681] <inf> net_lwm2m_rd_client: Start LWM2M Client: urn:imei:350457794446409
[00:00:04.593,353] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:350457794446409' with client lifetime 43200 using server object 0
+CNEC_ESM: 50,0
%MDMEV: SEARCH STATUS 2
+CEREG: 1,"7EF6","011ED70D",7,,,"00001111","11100000"
+CEDRXP: 4,"0000","0000","0000"
%XTIME: "80","42701071839080","01"
[00:00:04.993,743] <inf> app_event_manager: MODEM_EVT_LTE_PSM_UPDATE
[00:00:04.994,415] <inf> app_event_manager: MODEM_EVT_LTE_EDRX_UPDATE
[00:00:04.995,086] <inf> app_event_manager: DATA_EVT_DATE_TIME_OBTAINED
[00:00:05.065,155] <inf> lwm2m_security: Need to write credentials, requesting LTE and GNSS offline...
[00:00:05.065,612] <inf> app_event_manager: CLOUD_EVT_LTE_DISCONNECT
+CGEV: ME PDN DEACT 0
[00:00:05.142,059] <inf> app_event_manager: MODEM_EVT_LTE_DISCONNECTED
+CEREG: 0
+CGEV: ME DETACH
[00:00:05.242,614] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
%CESQ: 255,0,255,0
+CSCON: 0
[00:00:08.817,901] <inf> lwm2m_security: Requesting LTE and GNSS online
[00:00:08.818,420] <inf> app_event_manager: CLOUD_EVT_LTE_CONNECT
[00:00:08.860,198] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTING
%CESQ: 64,3,8,1
+CEREG: 2,"7EF6","011ED70D",7
[00:00:10.341,339] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
%CESQ: 65,3,17,2
+CSCON: 1
[00:00:10.819,702] <err> net_lwm2m_engine: Failed to enable TLS_DTLS_CID: -22
[00:00:10.820,129] <err> net_lwm2m_engine: Cannot connect UDP (-114)
[00:00:10.820,465] <err> net_lwm2m_rd_client: Cannot init LWM2M engine (-114)
[00:00:10.820,800] <err> net_lwm2m_rd_client: sm_do_network_error, retries 0
[00:00:10.821,044] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:350457794446409' with client lifetime 43200 using server object 0
[00:00:10.821,441] <err> net_lwm2m_message_handling: Unable to resolve address
[00:00:10.821,441] <err> net_lwm2m_rd_client: Cannot init LWM2M engine (-2)
[00:00:10.821,777] <err> net_lwm2m_rd_client: sm_do_network_error, retries 1
+CGEV: ME PDN ACT 0,0
[00:00:11.078,796] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTED
+CNEC_ESM: 50,0
%MDMEV: SEARCH STATUS 2
+CEREG: 1,"7EF6","011ED70D",7,,,"00001111","11100000"
%XTIME: "80","42701071836180","01"
[00:00:11.280,944] <inf> app_event_manager: MODEM_EVT_LTE_PSM_UPDATE
%CESQ: 65,3,23,3
[00:00:11.821,228] <err> net_lwm2m_rd_client: sm_do_network_error, retries 1
[00:00:11.821,472] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:350457794446409' with client lifetime 43200 using server object 0
[00:00:11.897,277] <err> net_lwm2m_engine: Failed to enable TLS_DTLS_CID: -22
[00:00:12.250,549] <inf> net_lwm2m_engine: Connected, sock id 2
[00:00:12.315,460] <inf> net_lwm2m_rd_client: Registration Done (EP='urn:imei:350457794446409')
[00:00:12.316,253] <inf> app_event_manager: CLOUD_EVT_CONNECTED
[00:00:12.317,199] <inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, MOD_STAT, BAT, ENV, LOCATION)
[00:00:12.317,993] <inf> app_event_manager: LOCATION_MODULE_EVT_ACTIVE
[00:00:12.320,922] <inf> app_event_manager: LOCATION_MODULE_EVT_AGNSS_NEEDED
[00:00:12.323,120] <inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY
[00:00:12.323,730] <inf> app_event_manager: SENSOR_EVT_FUEL_GAUGE_READY
+CEREG: 1,"7EF6","011ED70D",7,,,"00001111","00101101"
[00:00:12.393,859] <inf> app_event_manager: MODEM_EVT_LTE_PSM_UPDATE
[00:00:12.470,764] <inf> app_event_manager: MODEM_EVT_MODEM_STATIC_DATA_READY
[00:00:12.473,663] <inf> net_lwm2m_obj_gnss_assistance: Requesting A-GNSS data, mask 0x000001ff
[00:00:12.473,785] <inf> net_lwm2m_location_assist: Send A-GNSS request
[00:00:12.476,531] <inf> net_lwm2m_message_handling: Send op to server (/dp)
[00:00:12.513,519] <inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY
[00:00:12.524,963] <inf> net_lwm2m_message_handling: Send done!
%CESQ: 66,3,17,2
%CESQ: 66,3,22,3
+CSCON: 0
%XT3412: 46799999
[00:00:42.478,424] <inf> lwm2m_rai: RAI enabled
%CESQ: 255,0,255,0
%CESQ: 66,3,19,2
%MDMEV: SEARCH STATUS 2
%XT3412: 0
+CSCON: 1
+CSCON: 0
%XT3412: 46799999
%XT3412: 0
+CSCON: 1
%CESQ: 65,3,24,3
[00:01:54.786,285] <wrn> location: GNSS timed out possibly due to too short GNSS time windows
%NCELLMEAS: 0,"011ED70D","20408","7EF6",17,6400,475,66,24,114005,113386
+CSCON: 0
%XT3412: 46799999
%NCELLMEAS: 0,"011ED70D","20408","7EF6",17,119478,6400,475,68,21,120854,1,0
[00:02:02.319,244] <inf> app_event_manager: DATA_EVT_DATA_READY
[00:02:02.320,678] <inf> app_event_manager: DATA_EVT_DATA_SEND
[00:02:02.326,568] <inf> net_lwm2m_message_handling: Send op to server (/dp)
%NCELLMEAS: 0,"011ED70D","20408","7EF6",17,119478,6400,475,68,22,127282,1,0,"019B5501","20404","56BD",65535,0,6300,372,61,17,127340,0,0
[00:02:07.810,821] <inf> app_event_manager: LOCATION_MODULE_EVT_CLOUD_LOCATION_DATA_READY
[00:02:07.811,401] <inf> app_event_manager: DATA_EVT_DATA_READY
[00:02:07.812,042] <inf> net_lwm2m_obj_signal_meas_info: Updating information for 0 neighbouring cells
[00:02:07.812,255] <inf> app_event_manager: DATA_EVT_CLOUD_LOCATION_DATA_SEND
[00:02:07.817,199] <inf> net_lwm2m_message_handling: Send op to server (/dp)
%XT3412: 0
+CSCON: 1
+CSCON: 0
%XT3412: 46799999
%CESQ: 64,3,18,2
%CESQ: 255,0,255,0
[00:03:12.476,806] <inf> net_lwm2m_message_handling: Send op to server (/dp)
[00:03:26.223,052] <wrn> net_lwm2m_rd_client: Registration Update Timeout
[00:03:26.223,175] <inf> lwm2m_rai: RAI disabled
[00:03:26.223,205] <wrn> lwm2m_integration: LWM2M_RD_CLIENT_EVENT_REG_TIMEOUT
[00:03:26.224,121] <inf> app_event_manager: CLOUD_EVT_CONNECTING
[00:03:26.231,597] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:350457794446409' with client lifetime 43200 using server object 0
%CESQ: 63,3,9,1
%MDMEV: SEARCH STATUS 2
%CESQ: 64,3,17,2
%XT3412: 0
+CSCON: 1
[00:03:27.055,938] <err> net_lwm2m_engine: Failed to enable TLS_DTLS_CID: -22
[00:03:27.200,256] <inf> net_lwm2m_engine: Connected, sock id 2
[00:03:27.597,900] <inf> net_lwm2m_rd_client: Registration Done (EP='urn:imei:350457794446409')
[00:03:27.600,860] <inf> lwm2m_rai: RAI enabled
[00:03:27.601,226] <inf> app_event_manager: CLOUD_EVT_CONNECTED
[00:03:27.784,545] <inf> net_lwm2m_rd_client: Update callback (code:2.4)
[00:03:27.784,637] <inf> net_lwm2m_rd_client: Update Done
[00:03:27.825,897] <inf> lwm2m_rai: Ongoing traffic, RAI disabled
%CESQ: 65,3,22,3
+CSCON: 0
%XT3412: 46799999
[00:04:00.253,967] <inf> lwm2m_rai: RAI enabled
[00:04:01.301,116] <inf> app_event_manager: APP_EVT_DATA_GET_ALL
[00:04:01.301,818] <inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, LOCATION)
[00:04:01.302,642] <inf> app_event_manager: LOCATION_MODULE_EVT_ACTIVE
[00:04:01.305,999] <inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY
[00:04:01.306,579] <inf> app_event_manager: SENSOR_EVT_FUEL_GAUGE_READY
[00:04:01.369,689] <inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY
%CESQ: 65,3,16,2
%XT3412: 0
+CSCON: 1
%CESQ: 64,3,21,3
+CSCON: 0
%XT3412: 46799999
%XT3412: 0
+CSCON: 1
%CESQ: 63,3,15,2
%CESQ: 64,3,21,3
+CSCON: 0
%XT3412: 46799999
%CESQ: 64,3,16,2
%XT3412: 0
+CSCON: 1
%CESQ: 64,3,21,3
[00:05:07.817,474] <inf> net_lwm2m_message_handling: Send op to server (/dp)
+CSCON: 0
%XT3412: 46799999
[00:05:13.984,130] <inf> app_event_manager: SENSOR_EVT_MOVEMENT_INACTIVITY_DETECTED
%CESQ: 62,3,7,1
%CESQ: 65,3,23,3
[00:05:31.328,430] <wrn> location: GNSS timed out possibly due to too short GNSS time windows
%NCELLMEAS: 0,"011ED70D","20408","7EF6",16,6400,475,67,19,329703,311244
%NCELLMEAS: 0,"011ED70D","20408","7EF6",16,311244,6400,475,67,21,330921,1,0,"019B5502","20404","56BD",65535,0,6300,325,59,23,331132,0,0
%NCELLMEAS: 2,"011ED70D","20408","7EF6",16,311244,6400,475,67,21,336595,1,0,"019B5502","20404","56BD",65535,0,6300,325,59,21,336654,0,0
[00:05:37.133,453] <wrn> lte_lc: NCELLMEAS measurements interrupted; results incomplete
[00:05:37.134,063] <inf> app_event_manager: LOCATION_MODULE_EVT_CLOUD_LOCATION_DATA_READY
[00:05:37.134,643] <inf> app_event_manager: DATA_EVT_DATA_READY
[00:05:37.135,284] <inf> net_lwm2m_obj_signal_meas_info: Updating information for 0 neighbouring cells
[00:05:37.135,498] <inf> app_event_manager: DATA_EVT_CLOUD_LOCATION_DATA_SEND
[00:05:37.136,840] <inf> app_event_manager: DATA_EVT_DATA_SEND
[00:05:37.137,664] <err> net_lwm2m_location_assist: Temporary error in location services retry scheduled
[00:05:37.137,664] <err> cloud_module: cloud_wrap_cloud_location_send, err: -120
[00:05:37.141,876] <inf> net_lwm2m_message_handling: Send op to server (/dp)
%XT3412: 0
+CSCON: 1
%CESQ: 64,3,17,2
+CSCON: 0
%XT3412: 46799999
%CESQ: 65,3,22,3
[00:06:12.474,334] <err> net_lwm2m_location_assist: No response error in location services
[00:06:12.474,365] <err> net_lwm2m_obj_gnss_assistance: Result code 2
%CESQ: 255,0,255,0
[00:07:12.030,059] <wrn> net_lwm2m_rd_client: Registration Update Timeout
[00:07:12.030,181] <inf> lwm2m_rai: RAI disabled
[00:07:12.030,181] <wrn> lwm2m_integration: LWM2M_RD_CLIENT_EVENT_REG_TIMEOUT
[00:07:12.031,005] <inf> app_event_manager: CLOUD_EVT_CONNECTING
[00:07:12.038,879] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:350457794446409' with client lifetime 43200 using server object 0
%CESQ: 63,3,17,2
%MDMEV: SEARCH STATUS 2
[00:07:12.246,429] <err> net_lwm2m_engine: Failed to enable TLS_DTLS_CID: -22
%CESQ: 64,3,12,1
%XT3412: 0
+CSCON: 1
[00:07:12.735,992] <inf> net_lwm2m_engine: Connected, sock id 2
[00:07:12.826,324] <inf> net_lwm2m_rd_client: Registration Done (EP='urn:imei:350457794446409')
[00:07:12.829,284] <inf> lwm2m_rai: RAI enabled
[00:07:12.829,650] <inf> app_event_manager: CLOUD_EVT_CONNECTED
[00:07:12.981,323] <inf> net_lwm2m_rd_client: Update callback (code:2.4)
[00:07:12.981,445] <inf> net_lwm2m_rd_client: Update Done
[00:07:13.024,108] <inf> lwm2m_rai: Ongoing traffic, RAI disabled
%CESQ: 64,3,17,2
%CESQ: 64,3,22,3
+CSCON: 0
%XT3412: 46799999
[00:07:45.533,721] <inf> lwm2m_rai: RAI enabled
%CESQ: 255,0,255,0
[00:08:07.813,751] <err> net_lwm2m_location_assist: No response error in location services
[00:08:07.813,781] <err> net_lwm2m_obj_ground_fix: Result code 2
[00:09:01.302,398] <inf> app_event_manager: LOCATION_MODULE_EVT_TIMEOUT
[00:09:01.302,947] <inf> app_event_manager: LOCATION_MODULE_EVT_INACTIVE
[00:09:01.303,558] <inf> app_event_manager: DATA_EVT_DATA_READY
[00:09:01.304,229] <inf> net_lwm2m_obj_signal_meas_info: Updating information for 0 neighbouring cells
[00:09:01.304,443] <inf> app_event_manager: DATA_EVT_CLOUD_LOCATION_DATA_SEND
[00:09:01.309,417] <inf> net_lwm2m_message_handling: Send op to server (/dp)
%CESQ: 62,3,16,2
%MDMEV: SEARCH STATUS 2
%XT3412: 0
+CSCON: 1
%CESQ: 64,3,21,3
+CSCON: 0
%XT3412: 46799999
%XT3412: 0
+CSCON: 1
+CSCON: 0
%XT3412: 46799999
%CESQ: 64,3,16,2
%CESQ: 65,3,22,3
%CESQ: 65,3,17,2
%CESQ: 255,0,255,0
%CESQ: 63,3,19,2
%MDMEV: SEARCH STATUS 2
%XT3412: 0
+CSCON: 1
+CSCON: 0
%XT3412: 46799999
%CESQ: 255,0,255,0
[00:11:43.354,156] <wrn> net_lwm2m_rd_client: Registration Update Timeout
[00:11:43.354,278] <inf> lwm2m_rai: RAI disabled
[00:11:43.354,309] <wrn> lwm2m_integration: LWM2M_RD_CLIENT_EVENT_REG_TIMEOUT
[00:11:43.354,980] <inf> app_event_manager: CLOUD_EVT_CONNECTING
[00:11:43.363,677] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:350457794446409' with client lifetime 43200 using server object 0
%CESQ: 63,3,8,1
%MDMEV: SEARCH STATUS 2
%XT3412: 0
+CSCON: 1
[00:11:44.108,764] <err> net_lwm2m_engine: Failed to enable TLS_DTLS_CID: -22
[00:11:44.243,865] <inf> net_lwm2m_engine: Connected, sock id 2
[00:11:44.365,173] <inf> net_lwm2m_rd_client: Registration Done (EP='urn:imei:350457794446409')
[00:11:44.368,133] <inf> lwm2m_rai: RAI enabled
[00:11:44.368,499] <inf> app_event_manager: CLOUD_EVT_CONNECTED
[00:11:44.544,189] <inf> net_lwm2m_rd_client: Update callback (code:2.4)
[00:11:44.544,311] <inf> net_lwm2m_rd_client: Update Done
[00:11:44.602,966] <inf> lwm2m_rai: Ongoing traffic, RAI disabled
%CESQ: 64,3,13,1
+CSCON: 0
%XT3412: 46799999
[00:12:01.309,692] <inf> net_lwm2m_message_handling: Send op to server (/dp)
%XT3412: 0
+CSCON: 1
[00:12:01.617,858] <inf> net_lwm2m_message_handling: Send done!
+CSCON: 0
%XT3412: 46799999
[00:12:31.319,335] <inf> lwm2m_rai: RAI enabled
%CESQ: 255,0,255,0
[00:22:42.898,529] <inf> app_event_manager: UI_EVT_BUTTON_DATA_READY
[00:22:42.898,803] <inf> app_event_manager: DATA_EVT_UI_DATA_READY
[00:22:42.899,658] <inf> app_event_manager: DATA_EVT_UI_DATA_SEND
[00:22:42.902,709] <inf> net_lwm2m_message_handling: Send op to server (/dp)
%CESQ: 63,3,24,3
%MDMEV: SEARCH STATUS 2
%CESQ: 62,3,18,2
%XT3412: 0
+CSCON: 1
%CESQ: 62,3,23,3

[dejans]

Hi,

It seems that you get "Invalid argument" and "Network is unreachable" errors from lwm2m engine as well as "Socket already connected" from the Cloud module. Which network do you connect to? 

Do you see any difference if you disable Kconfigs shown below in your overlay-lwm2m.conf file?

CONFIG_LWM2M_TLS_SESSION_CACHING=n
CONFIG_LWM2M_DTLS_CID=n

Can you provide more information about your server configuration? Have you followed Coiote Device Management server setup guide?

Best regards,
Dejan

[hubert_11]

Hi Dejan,

After adding those Kconfigs is stil get errors unfortunately:

*** Booting nRF Connect SDK 3758bcbfa5cd ***
[00:00:00.271,118] <inf> at_host: UART check failed: 12. Dropping buffer and retrying.
[00:00:00.281,982] <inf> app_event_manager: APP_EVT_START
[00:00:00.511,810] <inf> app_event_manager: MODEM_EVT_INITIALIZED
[00:00:00.638,854] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTING
[00:00:00.698,913] <inf> lwm2m_firmware: Image is confirmed OK
[00:00:01.308,471] <inf> app_event_manager: DATA_EVT_CONFIG_INIT
[00:00:01.641,387] <inf> app_event_manager: SENSOR_EVT_MOVEMENT_ACTIVITY_DETECTED
%CESQ: 60,3,20,2
+CEREG: 2,"7EF6","011ED70D",7
+CSCON: 1
[00:00:03.762,817] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
+CGEV: ME PDN ACT 0,0
[00:00:04.966,644] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTED
[00:00:04.967,742] <inf> net_lwm2m_rd_client: Start LWM2M Client: urn:imei:350457794446409
[00:00:04.968,383] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:350457794446409' with client lifetime 43200 using server object 0
+CNEC_ESM: 50,0
%MDMEV: SEARCH STATUS 2
+CEREG: 1,"7EF6","011ED70D",7,,,"00001111","11100000"
+CEDRXP: 4,"0000","0000","0000"
%XTIME: "80","42704090010180","01"
[00:00:05.272,552] <inf> app_event_manager: MODEM_EVT_LTE_PSM_UPDATE
[00:00:05.273,254] <inf> app_event_manager: MODEM_EVT_LTE_EDRX_UPDATE
[00:00:05.273,895] <inf> app_event_manager: DATA_EVT_DATE_TIME_OBTAINED
[00:00:05.340,240] <inf> lwm2m_security: Need to write credentials, requesting LTE and GNSS offline...
[00:00:05.340,728] <inf> app_event_manager: CLOUD_EVT_LTE_DISCONNECT
+CGEV: ME PDN DEACT 0
[00:00:05.512,084] <inf> app_event_manager: MODEM_EVT_LTE_DISCONNECTED
+CEREG: 0
+CGEV: ME DETACH
[00:00:05.612,609] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
%CESQ: 255,0,255,0
+CSCON: 0
[00:00:07.792,297] <inf> lwm2m_security: Requesting LTE and GNSS online
[00:00:07.792,816] <inf> app_event_manager: CLOUD_EVT_LTE_CONNECT
[00:00:07.847,259] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTING
%CESQ: 58,2,20,2
+CEREG: 2,"7EF6","011ED70D",7
[00:00:09.349,365] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
+CSCON: 1
[00:00:09.794,616] <err> net_lwm2m_engine: Cannot connect UDP (-114)
[00:00:09.794,891] <err> net_lwm2m_rd_client: Cannot init LWM2M engine (-114)
[00:00:09.795,227] <err> net_lwm2m_rd_client: sm_do_network_error, retries 0
[00:00:09.795,440] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:350457794446409' with client lifetime 43200 using server object 0
[00:00:09.795,776] <err> net_lwm2m_message_handling: Unable to resolve address
[00:00:09.795,776] <err> net_lwm2m_rd_client: Cannot init LWM2M engine (-2)
[00:00:09.795,989] <err> net_lwm2m_rd_client: sm_do_network_error, retries 1
+CGEV: ME PDN ACT 0,0
[00:00:10.309,814] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTED
+CNEC_ESM: 50,0
%MDMEV: SEARCH STATUS 2
+CEREG: 1,"7EF6","011ED70D",7,,,"00001111","11100000"
%XTIME: "80","42704090015180","01"
[00:00:10.511,932] <inf> app_event_manager: MODEM_EVT_LTE_PSM_UPDATE
[00:00:10.796,722] <err> net_lwm2m_rd_client: sm_do_network_error, retries 1
[00:00:10.796,966] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:350457794446409' with client lifetime 43200 using server object 0
[00:00:11.176,452] <inf> net_lwm2m_engine: Connected, sock id 2
[00:00:11.326,385] <inf> net_lwm2m_rd_client: Registration Done (EP='urn:imei:350457794446409')
[00:00:11.327,209] <inf> app_event_manager: CLOUD_EVT_CONNECTED
[00:00:11.328,155] <inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, MOD_STAT, BAT, ENV, LOCATION)
[00:00:11.328,948] <inf> app_event_manager: LOCATION_MODULE_EVT_ACTIVE
[00:00:11.331,756] <inf> app_event_manager: LOCATION_MODULE_EVT_AGNSS_NEEDED
[00:00:11.334,167] <inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY
[00:00:11.334,777] <inf> app_event_manager: SENSOR_EVT_FUEL_GAUGE_READY
+CEREG: 1,"7EF6","011ED70D",7,,,"00001111","00101101"
[00:00:11.380,737] <inf> app_event_manager: MODEM_EVT_LTE_PSM_UPDATE
[00:00:11.411,346] <inf> app_event_manager: MODEM_EVT_MODEM_STATIC_DATA_READY
[00:00:11.491,363] <inf> net_lwm2m_obj_gnss_assistance: Requesting A-GNSS data, mask 0x000001ff
[00:00:11.491,485] <inf> net_lwm2m_location_assist: Send A-GNSS request
[00:00:11.494,232] <inf> net_lwm2m_message_handling: Send op to server (/dp)
[00:00:11.532,470] <inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY
[00:00:11.555,877] <inf> net_lwm2m_message_handling: Send done!
+CSCON: 0
%XT3412: 46799999
%CESQ: 58,2,15,2
%CESQ: 60,3,22,3
%CESQ: 60,3,15,2
[00:00:43.990,570] <inf> lwm2m_rai: RAI enabled
%CESQ: 61,3,20,2
%CESQ: 255,0,255,0
[00:01:04.249,359] <inf> app_event_manager: SENSOR_EVT_MOVEMENT_INACTIVITY_DETECTED
%CESQ: 59,2,9,1
%MDMEV: SEARCH STATUS 2
%CESQ: 60,3,18,2
%XT3412: 0
+CSCON: 1
%CESQ: 59,2,23,3
%CESQ: 59,2,17,2
[00:01:17.033,905] <inf> app_event_manager: SENSOR_EVT_MOVEMENT_ACTIVITY_DETECTED
%CESQ: 58,2,12,1
%CESQ: 58,2,18,2
%CESQ: 58,2,23,3
%CESQ: 59,2,17,2
%CESQ: 59,2,22,3
%CESQ: 58,2,17,2
%CESQ: 56,2,22,3
%CESQ: 54,2,16,2
%CESQ: 52,2,21,3
%CESQ: 52,2,16,2
%CESQ: 51,2,21,3
+CSCON: 0
%XT3412: 46799999

The server is just the normal Coiote server, set up as per the link that you gave. So I added the device to the Coiote server fist (via the management server, no bootstrap), then programmed the asset tracker with the PSK and server address.

 What exact information on the server do you need?

[dejans]

Hi,

hubert_11 said:

What exact information on the server do you need?

Apart from what you already provided, there is no need for additional information at this point. I will let you know if more information is needed.

We will look into this issue internally. I will get back to you by the end of the next week. Please note that delayed replies can be expected due to reduced staffing during the holiday season.

Best regards,
Dejan

[hubert_11]

Thank you Dejan,

I'll await your response then.

Have a nice weekend!

[dejans]

Hi,

Have a nice weekend too!

Best regards,
Dejan