Thingy91 over LwM2M?

[Luke_M]

Hi, How can I configure the LwM2M server (URL, Port, Credentials) on my Thingy91?
Can I do this via MQTT and the nrf Cloud or do I need some specific tools?

[Didrik Rokhaug]

Hi.

Could you tell me a bit more about what it is you want to achieve?

Without more details, it is hard to give a concrete answer, but here are some pointers:

There is no LwM2M support in the default firmware (asset_tracker sample application) on the Thingy:91. However, the lwm2m_client sample should work for the Thingy:91 as well as for the nRF91DK.

The documentation and source code is a good starting point.

To program the Thingy:91, you ideally would use an external JLink programmer (or the nRF91DK which has one on board) that is compatible with ARMv8. However, if you do not have any such programmers, you can use MCUBoot to perform DFU. Take a look at this guide to learn how. Note: you should take care to ensure that CONFIG_BOOTLOADER_MCUBOOT=y is added to the project configuration (prj.conf), so that the project is built with MCUBoot. If not, you will not be able to update the firmware on the Thingy again without an external debugger.

Best regards,

Didrik

[Luke_M]

Hi Didrik,

THX for the information - and the additional inks - will look into it and see how far it will get me.
In the Thingy91 introduction video, it looks like the LwM2M Agent is already preinstalled on the devices and ready to use

As for your question: I want to achieve fully automated remote devices management of the Thingy91 in addition to other devices I already have. Set parameter, read values, change modes, monitor states, ... all the fun stuff

MQTT is a great messaging protocol to send messages and ignore data consumption but very bad when it comes to managing multiple devices from multiple manufacturers that run different firmware.

Cheers
Luke

[Didrik Rokhaug]

I am not sure what video you are referencing, but the asset_tracker demo application only uses MQTT.

There is a pull request open for adding support for the lwm2m_carrier library (https://github.com/NordicPlayground/fw-nrfconnect-nrf/pull/1408), although, at the moment, that library only supports Verizon's device management features.

Other than that, I think the lwm2m_client sample is the place to start.

[Luke_M]

Hi Didrik,

THX for the info - Both sources Webinar-Q6 and the documentation refer to an LwM2M client that runs on the application layer.

Do I understand you correctly thath the application mentioned here is not available by itself to be uploaded to the devices and run on top of the existing OS but only by updating the whole device firmware including the LwM2M agent within?

[Luke_M]

One more question regarding the MCUBoot -
nrfcloud is described as following: Control device settings and notifications from the cloud—no coding required. Plus, automatically install firmware updates.
Can I push the compiled LwM2M Application/Firmware over the nrfcloud onto the device?

[Didrik Rokhaug]

Hi.

The firmware that the Thingy:91 shipped with from the factory sadly does not support over the air firmware updates.

Regarding your last comment (about LwM2M): I think you misunderstood what was said. The SDK supports LwM2M (and you can run LwM2M on the Thingy), but the Thingy does not support LwM2M out of the box.

I have also taken a closer look at the lwm2m_client sample, and it does not appear to use the real sensors by default. It should however, only be a matter of defining the sensors in the prj.conf file to change that. Take a look at the asset_tracker sample's configuration file for the Thingy to get an example.

[henry lau]

hi,

Noted on the sensor configuration required.

We plan to compile and run the sample code on the Thingy91, but there is an error that project is not a Zephyr project. 

[henry lau]

I am using the Segger Embedded Studio in Windows environment.

[Didrik Rokhaug]

Hi, henry lau.

Could you open a new ticket, where you also provide some information about how you import the project to Segger Embedded Studio?

Best regards,

Didrik