My feedback: LWM2M

Showing 4

Bulk upload of multiple LWM2M object definition files

When using LWM2M every object has to be uploaded separatly to the platform. This causes a lot of repetitive work. The idea is, instead of uploading single LWM2M object definition at a time, upload multiple files at once. This would smoothen the se...

Guest almost 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1 Future consideration

7 VOTE

LWM2M custom decoder for a whole object

For some objects, it is more efficient for a device to report whole object in one message. Therefore it would be good to have a possibility to use custom decoder on the whole object and not resource by resource. Location updates already work this ...

Peter Gaspar over 4 years ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1 Future consideration

2 VOTE

Allow custom LwM2M decoder microservice to create/update arbitrary inventory fragments

A custom decoder microservice can return dataFragments to the LwM2M agent in order to update the managed object, but this is only capable of updating the fragment specific to the LwM2M resource, e.g. "dataFragments" :[ { "value" : "Hello World" , ...

Guest over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 2 Future consideration

4 VOTE

Custom Action on Instance Level - LWM2M implementation

Reaction on notifications are not always solely based on a single resource. In the majority of the cases there are multiple resources involved, especially the timestamp is an important field. It must be possible to configure custom actions on inst...

Guest over 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1 Future consideration

Please enter your email address

FILTER BY CATEGORY