lwm2m client nrf9160 - custom board

RE: lwm2m client nrf9160 - custom board

Sigurd — Mon, 27 Nov 2023 15:34:37 GMT

Hi!

[quote user="Hkhan7861"] The device will suffer a network error, suspend the lwm2m client and then enter the LTE_OFFLINE client_state. Following this it will never attempt to look for a network connection again. How do i stop this from happening?[/quote]

If you get a network error, it will try to reconnect: https://github.com/nrfconnect/sdk-nrf/blob/v2.5.0/samples/cellular/lwm2m_client/src/main.c#L787

RE: lwm2m client nrf9160 - custom board

Hkhan7861 — Thu, 12 Oct 2023 08:40:41 GMT

I have discovered what happens. The device will suffer a network error, suspend the lwm2m client and then enter the LTE_OFFLINE client_state. Following this it will never attempt to look for a network connection again. How do i stop this from happening?

RE: lwm2m client nrf9160 - custom board

Hkhan7861 — Mon, 02 Oct 2023 19:17:37 GMT

Hi Sigurd

Any updates on this ? the issue still seems to be apparent. Ant news on this?

RE: lwm2m client nrf9160 - custom board

Hkhan7861 — Fri, 29 Sep 2023 10:15:36 GMT

Hi Sigurd

Unfortunately i dont have any logs however i do suspect it is the same issue. The client is unchanged and everything ive written runs independently. When the device was reset, the flash was full of data that should have been sent which is what my code does in a separate thread. I just wanted to confirm if the issue has been reported by anybody else ?

RE: lwm2m client nrf9160 - custom board

Sigurd — Thu, 28 Sep 2023 12:26:40 GMT

Hi!

[quote user="sigurdon"]Håkon is out of office, so I'm replying instead.[/quote]

Håkon is back in office now, so I will re-assign this to him.

[quote user="Hkhan7861"]I wasn't logging initially when I made this change. When I run into an error again I will come back to this post. [/quote]

Do you have any logs to share? is it the exact same error as last time, or is it a different error you see now?

RE: lwm2m client nrf9160 - custom board

Hkhan7861 — Wed, 27 Sep 2023 06:06:33 GMT

Good day

I seem to have run into the same issue again. Just wondering if you have any updates on this?

Kind regards,

Hassan

RE: lwm2m client nrf9160 - custom board

Hkhan7861 — Mon, 11 Sep 2023 11:00:17 GMT

Hi SIgurd

I wasn't logging initially when I made this change. When I run into an error again I will come back to this post. At the moment I am using state_trigger_and_unlock instead of state_set_and_unlock . This is the most recent change I made last week.

Thank you!

Kind regards,

Hassan

RE: lwm2m client nrf9160 - custom board

Sigurd — Thu, 07 Sep 2023 11:21:33 GMT

Hi!

Håkon is out of office, so I'm replying instead.

Did you apply both PRs?
https://github.com/nrfconnect/sdk-nrf/pull/12144/files

https://github.com/nrfconnect/sdk-nrf/pull/12178/files

Do you still see this error with these PR's applied, or is it a different error you see now?

[quote user="Hkhan7861"]

I did some testing and found that when the lwm2m client triggers a NETWORK_ERROR, the client enters the START client_state. But when it enters :

lwm2m_rd_client_start(&client, endpoint_name, bootstrap_flags,

rd_client_event, NULL);

"Client is already running in state 9" (referring to the engine state) is logged and the client remains in state 1(START)

However, the client is not connected to the internet and now a lwm2m_send function will fail every time due to it not being connected.

[/quote]

RE: lwm2m client nrf9160 - custom board

Hkhan7861 — Mon, 04 Sep 2023 07:59:13 GMT

hi MIchal

I tested the code over the weekend and it appears that the client still gets stuck in that state. Has any issues on this fix been reported?

Kind regards,

Hassan

RE: lwm2m client nrf9160 - custom board

Hkhan7861 — Fri, 01 Sep 2023 06:35:59 GMT

Thank you ! Will update it accordingly.

Kind regards,

Hassan.

RE: lwm2m client nrf9160 - custom board

Hakon — Thu, 31 Aug 2023 12:57:50 GMT

[quote user="Hkhan7861"]I added the code stated in the link of the PR that you sent me and it seems to have worked. Was this not supposed to be done for SDK 2.4.0? [/quote]

Well that's great then. Here is a link to the most recent fix, https://github.com/nrfconnect/sdk-nrf/pull/12178.

RE: lwm2m client nrf9160 - custom board

Hkhan7861 — Wed, 30 Aug 2023 05:52:54 GMT

Hi Hakon

I added the code stated in the link of the PR that you sent me and it seems to have worked. Was this not supposed to be done for SDK 2.4.0?

Kind regards,

Hassan

RE: lwm2m client nrf9160 - custom board

Hakon — Tue, 29 Aug 2023 12:30:28 GMT

The fix is not working for NCS 2.4 yet (it is still being worked on), but you can make these changes to fix it

@@ -447,7 +447,7 @@ static void rd_client_event(struct lwm2m_ctx *client, enum lwm2m_rd_client_event
     case LWM2M_RD_CLIENT_EVENT_DISCONNECT:
         LOG_DBG("Disconnected");
         if (client_state != UPDATE_FIRMWARE) {
-            state_set_and_unlock(START);
+            state_trigger_and_unlock(START);
         } else {
             k_mutex_unlock(&lte_mutex);
         }
(1/2) Stage this hunk [y,n,q,a,d,j,J,g,/,e,?]? y
@@ -686,9 +686,9 @@ int main(void)
             ret = lwm2m_rd_client_start(&client, endpoint_name, bootstrap_flags,
                             rd_client_event, NULL);
             if (ret) {
-                state_set_and_unlock(NETWORK_ERROR);
+                state_trigger_and_unlock(NETWORK_ERROR);
             } else {
-                state_set_and_unlock(CONNECTING);
+                state_trigger_and_unlock(CONNECTING);

RE: lwm2m client nrf9160 - custom board

Hakon — Mon, 28 Aug 2023 09:27:41 GMT

The fix is ready. Please try this PR and see if it works for you.

RE: lwm2m client nrf9160 - custom board

Hkhan7861 — Mon, 28 Aug 2023 06:54:49 GMT

Hi Hakon

Thank you for the update ! Please let me know as soon as its available.

Kind regards,

Hassan

RE: lwm2m client nrf9160 - custom board

Hakon — Fri, 25 Aug 2023 12:24:55 GMT

Hello,

I asked the developer, and he said there is a PR with this fix. He will make a smaller one on Monday that you can apply.

RE: lwm2m client nrf9160 - custom board

Hkhan7861 — Fri, 25 Aug 2023 07:31:24 GMT

ADDITIONAL INFORMATION:

I did some testing and found that when the lwm2m client triggers a NETWORK_ERROR, the client enters the START client_state. But when it enters :

lwm2m_rd_client_start(&client, endpoint_name, bootstrap_flags,

rd_client_event, NULL);

"Client is already running in state 9" (referring to the engine state) is logged and the client remains in state 1(START)

However, the client is not connected to the internet and now a lwm2m_send function will fail every time due to it not being connected. How do I stop this from happening a force reconnection. Again , I would like to reiterate that I have not changed anything with the standard lwm2m client nrf9160 sample.