nRF9160 LWM2M sample with Leshan prj.conf setup

RE: nRF9160 LWM2M sample with Leshan prj.conf setup

Øyvind — Thu, 03 Oct 2019 06:29:03 GMT

Hello again,

Our NCS team informed me that there is a fix for the DNS issues (the reason for why you have to use an IP), Please try to update your master branch and let me know how that works. Also, the leshan servers seem to be more stable at the moment.

Kind regards,
Øyvind

RE: nRF9160 LWM2M sample with Leshan prj.conf setup

Øyvind — Fri, 27 Sep 2019 06:29:50 GMT

Hello,

I forwarded your answer to our team.

[quote]

app_lwm2m_connmon: Unable to obtain modem parameters: -11

[/quote]

This should be fixed in the latest version on master branch. Please update your repo with a git pull and west update.

[quote][/quote]

[00:00:08.342,346] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'nrf-xxxxxxxxxxxxxxx' with client lifetime 30
[00:00:19.038,024] <inf> net_lwm2m_engine: Resending message: 0x200226a4
[00:00:39.038,909] <inf> net_lwm2m_engine: Resending message: 0x200226a4

This is unfortunately nothing we can do with, as this is due to server instability. Our team has observed the same behaviour when connecting to "leshan.eclipseprojects.io". Testing against a non-public LwM2M server (running leshan implementation as well) was successfull, with no issues.

RE: nRF9160 LWM2M sample with Leshan prj.conf setup

bjull — Tue, 24 Sep 2019 20:21:16 GMT

Hi Øyvind,

I tried using the IP address and it looks like it worked a bit better. Now I get an error getting the modem parameters and I'm unabled to connect to the LWM2M server. I did some debugging and it looks like the error occurs inside modem_info_params_get when trying to get cellid_hex. After sending the AT command and reading, modem_info_parse returns E2BIG.

Here's the console output:

uart:~$ ***** Booting Zephyr OS build v1.14.99-ncs3-snapshot2-1281-g40b430ba977c *****
[00:00:00.340,911] <inf> app_lwm2m_client: Run LWM2M client
[00:00:00.341,308] <err> buzzer: Could not bind to device
[00:00:00.341,308] <err> ui: Could not enable buzzer, err code: -19
[00:00:00.341,827] <inf> app_lwm2m_client: Initializing modem.
[00:00:00.342,651] <inf> app_lwm2m_client: endpoint: nrf-xxxxxxxxxxxxxxx
[00:00:00.343,170] <dbg> app_lwm2m_loc.lwm2m_init_location: GPS device found: GPS_SIM
[00:00:00.343,811] <dbg> app_lwm2m_loc.update_location_data: nmea_data
[00:00:00.343,963] <err> app_lwm2m_temp: No temperature device found.
[00:00:00.344,573] <inf> app_lwm2m_accel: accelerometer normal
[00:00:00.344,696] <inf> app_lwm2m_firmware: Update Counter: current 0, update 0
[00:00:00.344,726] <inf> app_lwm2m_firmware: Image is confirmed OK
[00:00:00.344,726] <inf> app_lwm2m_firmware: Firmware updated successfully
[00:00:02.734,252] <inf> app_lwm2m_client: Connecting to LTE network.
[00:00:02.734,252] <inf> app_lwm2m_client: This may take several minutes.
[00:00:07.415,252] <inf> app_lwm2m_client: Connected to LTE network
[00:00:07.417,114] <inf> net_lwm2m_rd_client: LWM2M Client: nrf-xxxxxxxxxxxxxxx
[00:00:07.423,522] <err> app_lwm2m_connmon: Unable to obtain modem parameters: -11
[00:00:08.342,346] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'nrf-xxxxxxxxxxxxxxx' with client lifetime 30
[00:00:19.038,024] <inf> net_lwm2m_engine: Resending message: 0x200226a4
[00:00:39.038,909] <inf> net_lwm2m_engine: Resending message: 0x200226a4
[00:01:00.342,437] <dbg> app_lwm2m_loc.update_location_data: nmea_data
[00:01:19.048,065] <inf> net_lwm2m_engine: Resending message: 0x200226a4
[00:02:00.350,982] <dbg> app_lwm2m_loc.update_location_data: nmea_data
[00:02:39.057,189] <wrn> net_lwm2m_rd_client: Registration Timeout
[00:02:39.057,189] <dbg> app_lwm2m_client.rd_client_event: Disconnected
[00:02:39.057,220] <dbg> app_lwm2m_client.rd_client_event: Registration failure!
[00:02:39.577,178] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'nrf-xxxxxxxxxxxxxxx' with client lifetime 30

RE: nRF9160 LWM2M sample with Leshan prj.conf setup

Øyvind — Tue, 24 Sep 2019 07:17:04 GMT

Hi Ben,

Can you please try to use an IP address instead of server name:

CONFIG_APP_LWM2M_SERVER="23.97.187.154"

According to the responsible engineer, this is a known bug and will be handled in a future release.

Kind regards,
Øyvind

RE: nRF9160 LWM2M sample with Leshan prj.conf setup

Achim Kraus — Fri, 20 Sep 2019 06:21:40 GMT

There maybe many reasons for that, but one, which occurred frequently over the years, was the encoding of the PSK secret. Leshan supports hex to enable access to a full binary secret. Other just use the ASCII string direct as secret. To check that, change the secret in the client to "0123456789ABCDEF" and on leshan to "30313233343536373839414243444546". Good luck :-).

RE: nRF9160 LWM2M sample with Leshan prj.conf setup

Øyvind — Tue, 17 Sep 2019 07:40:15 GMT

Hi Ben,

I'm sorry, but no target date available yet. Will keep you posted.

Kind regards,
Øyvind

RE: nRF9160 LWM2M sample with Leshan prj.conf setup

bjull — Mon, 16 Sep 2019 19:35:03 GMT

Hi Øyvind,

Thanks for your feedback and flagging to the SDK team. Could you please provide a target date for the resolution of the issue?

Best regards,
Ben

RE: nRF9160 LWM2M sample with Leshan prj.conf setup

Øyvind — Thu, 12 Sep 2019 12:20:05 GMT

Hello again,

I am seeing the same here, and unfortunately, nothing to do at the moment. Will report as a bug to our SDK team.

Kind regards,
Øyvind

RE: nRF9160 LWM2M sample with Leshan prj.conf setup

Øyvind — Thu, 12 Sep 2019 08:59:12 GMT

Hello,

[quote user=""] I've followed the instructions on the "nRF9160: LwM2M Client" page but I've been unable to connect to the LWM2M server[/quote]

The only thing that comes to mind, is that in the documentation it to configure prj.config with:

CONFIG_APP_LWM2M_SERVER="{IP address of LwM2M server}"
CONFIG_LWM2M_PEER_PORT=5684

However, the error message:

[00:17:17.579,772] <err> net_lwm2m_rd_client: Cannot init LWM2M engine (-22)

"Cannot init LWM2M engine (-22) indicates, according to errno.h, an invalid argument when calling lwm2m_engine_start().

Will investigate here.

Kind regards,
Øyvind