MLopezJ / LwM2M-Asset-Tracker

Document process of implement LwM2M protocol in Asset Tracker
0 stars 1 forks source link

Does coiote support LwM2M v1.1? #4

Open MLopezJ opened 1 year ago

MLopezJ commented 1 year ago

In Coiote, when creating a Template for the integration (https://eu.iot.avsystem.cloud/ui/hyperscalersCenter/view/manager/templates), there is no resource 5518. It gives the impression Coiote does not support LwM2M version 1.1 but here is said that versions 1.2, 1.1 and 1.0 of the protocol are supported.

+ info

MLopezJ commented 1 year ago

Question asked to Coiote:

How to report Timestamp data to Azure Device Twin (using Coiote integration) from Temperature, Humidity, Pressure and Push button?

Goal

It is desired to report the resource number 5518 in Device Twin from the following LwM2M objects:

Context

I have a device integrated with Azure. That integration was configured using this tutorial: https://iotdevzone.avsystem.com/docs/Demo_Projects/Tracking_tutorial/ .

The LwM2M version of objects 3303, 3304, 3323 and 3347 is 1.1. One important thing to notice is that version 1.0 of those objects do not have resource number 5518, but version 1.1 has.

Problem

In Coiote, when creating a Template for the integration (https://eu.iot.avsystem.cloud/ui/hyperscalersCenter/view/manager/templates), there is no resource 5518. It gives the impression Coiote does not support LwM2M version 1.1 but here https://www.avsystem.com/coiote-iot-device-management-platform/?utm_term=lightweight%20m2m&utm_campaign=IOT&utm_source=adwords&utm_medium=ppc&hsa_acc=6340757895&hsa_cam=20184078630&hsa_grp=151143476524&hsa_ad=660239387959&hsa_src=g&hsa_tgt=aud-2008718743085:kwd-295094585646&hsa_kw=lightweight%20m2m&hsa_mt=b&hsa_net=adwords&hsa_ver=3&gclid=CjwKCAjwzJmlBhBBEiwAEJyLu3vZWKQsnanA6gKHrBIgyVweQwg4jPH536_fpdtupKrPDPsZoaicchoCniAQAvD_BwE#:~:text=The%20platform%20supports%20LwM2M%20features%20for%201.2%2C%201.1%2C%201.0%20protocol%20versions is said that versions 1.2, 1.1 and 1.0 of the protocol are supported. So I am confuse.

Steps:

1- define your LwM2M object. Temperature (3303) for this example.

/**
 * Temperature
 */
const temp: Temperature_3303 = [
    {
        '5518': 1665149633,
        '5601': 23.51,
        '5602': 23.51,
        '5603': -40,
        '5604': 85,
        '5700': 24.57, // Sensor Value
        '5701': 'Celsius degrees',
    },
]

2- Create template for integration: https://user-images.githubusercontent.com/8351865/251450654-73ed85ba-1f7b-4f40-9d55-e94d4c6ae7ad.png ( there is no resource 5518)

3- Register device: https://user-images.githubusercontent.com/8351865/251452664-43c2bed2-43f3-496d-a76f-f991a512b404.png (id 5518 has no recognized resource name.)

4- Check object in device twin: https://user-images.githubusercontent.com/8351865/251452898-0c8c1f95-e4dd-49d8-aefb-4d587568e2a1.png (value for 5518 is not reported in the device twin in Azure)

I am missing some step in the template definition? Or how can I be able to select objects with resource number 5518?

Question link here

MLopezJ commented 1 year ago

Coiote does not support v. 1.1 in Templates.

That means the resource 5518 from objects 3303, 3304, 3323 and 3347 are not going to be send to Azure Device Twin.

This is critical issue because those values are required in Asset Tracker web app. They said: "The request is forwarded to the development team for further analysis. I'll keep you updated."

Server timestamp is going to be used in case one of those values is missing.