Skip to Main Content
Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

Cumulocity IoT Device Mgmt. & Connectivity

Showing 109

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 Device Availability (connectivity state) should be made available to APIs

Currently in the c8y platform, there can be a connectivity disconnect between c8y and a lwm2m endpoint. When this occurs the User experiences commands become queued while the availability is shown to still be green bi-directionally. Notably the qu...
Andrew Nowak 3 months ago in Cumulocity IoT Device Mgmt. & Connectivity 0

File_successfully_uploaded message on lwm2m bulk registration dialog is misleading for failed lwm2m device creations

Customer has raised concerns around lwm2m bulk registration dialog where the message “File successfully uploaded” for failed devices is bit misleading. By default, the complete message on the dialog is hidden until dropdown is clicked and hence wi...
Santhosh Thakkalapally 3 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Planning / planned

Add the ability to Export Events from a Lwm2m Device

The ability to export events through the UI or through API would drastically help troubleshooting new device integration. Having to click on each event to open it and observe the data for several events concurrently is not efficient. An export to ...
Andrew Nowak 3 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Future consideration

MQTT static template - Operation for clearing an alarm on the source device

Devices can raise alarms via SmartREST templates such as 301, 302, 303, 304 and 305. Devices can also clear alarms via SmartREST via the templates such as 306 and 307. However, there is no standard way to backpropagate the alarm status to the devi...

LwM2M: list resources according to their ID

Currently the L2M2M resources are listed in an undefined sequences. Most often the resource sequence is alphabetic, but not always (Device Management->Objects->Device\3\0). The resources should be listed according to their ID. This is how it...
Guest 3 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Planning / planned

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

Events and Alarms that exist in the future should be rendered.

Events and Alarms that exist in the future should be rendered. When testing events/alarms or other features it is useful to render all events and alarms even if they exist in the future. This can assist a user to identify time issues. ...
Andrew Nowak 5 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Unlikely to support