Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

LWM2M

Showing 11 of 408

Leverage Kubernetes for rolling Lwm2m Upgrades

Rolling LwM2M Agent upgrades. Leverage Kubernetes rolling upgrade capability such that a LwM2M Agent does not experience an outage (that today requires all devices to be re-Registered).
Andrew Nowak 3 months ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 0

Add new c8y_LWM2MObserveNotification and c8y_LWM2MSend event types.

Messages originating from the device (Observe Notify and Send) are included in the Event Notification channel but now appear only in the c8y_lwm2mlog event type (that cannot be used as it is not supported). These 2 new Event types will allow uServ...
Andrew Nowak 3 months ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 0

Add “Last Updated Time” to Operation Object

Currently, Operations only have a created date. The Last Update Time will provide time stamp info for an Operation state change and provide “hints” around message latency.
Andrew Nowak 3 months ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1

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 4 months ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 2 Planning / planned

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

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 almost 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1 Planning / planned

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

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

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 over 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1 Unlikely to support