Skip to Main Content
Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

LWM2M

Showing 8

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 over 2 years ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1 Future consideration

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

Allow comments in LWM2M post operations

In the LWM2M post operations input field operations that will be sent to device can be edited. In the example window on the right there are comments that start with a "#" to describe the following line: # Discover all resources of Object 3300, the...
Guest over 2 years ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1 Planning / planned

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 about 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1 Future consideration

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 about 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 2 Future consideration

Lwm2m x509 authentication should validate the full certificate chain during initial DTLS handshake

Lwm2m x509 authentication should validate the full certificate chain during initial DTLS handshake This feature is an enhancement that should allow a more efficient way to validate a chain of certificates that occur in an advanced manufacturing. V...
Andrew Nowak 3 days ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1

Accept option of observes must be selectable - LWM2M implementation

The accept option tells the lwm2m client which encoding to use in a response. This could be TLV, JSON or others. There are situations (for example for buffering data) where it is necessary to select the accept option manually. TLV does not contain...
Guest about 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1 Unlikely to support

LwM2M Firmware repository - fragment with the MO itself to configure individual FW updates to use one protocol over another

Orignial question: We currently have support for both CoAP and HTTP based protocols for the firmware repo, how do we configure individual firmware updates to use one protocol over another? Attached is further commentary between Elias and Cris Da...
Guest almost 5 years ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1 Unlikely to support