Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

Cumulocity IoT Device Mgmt. & Connectivity

Showing 106

Export/Import Device Management->Device protocol XML resource mapping

If a user configures a bunch of Lwm2m XMLs and links each resource with MEAs or custom actions inside one tenant, this work cannot be easily exported to another tenant and thus requires manually setting all of this again.
John Fisher over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 2 Future consideration

LWm2m: Avoid unnecessary unavailability alarms for LwM2M device

Description: For LWm2m devices, the expected transmission interval (Required interval) is currently linked to the registration lifetime and it doesn't matter what is entered in the GUI, this value is always be overwritten by the "LwM2M Server Life...
Juergen Hahl over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 6 Planning / planned

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

MEA types/series names should not be altered by LwM2M agent

The LwM2M agent adds a suffix to the type (and series, for measurements) of measurements, events, and alarms that it creates from received values. The suffix reflects the object instance and resource ID in the resource path. This alteration means ...
Guest 7 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Planning / planned

device protocol interprete holding register as DINT/REAL

In the "New holding register" dialog of the device protocols it is possible to configure the transformation of the passed bits. The number of bits can be configured. However, only integer numbers are interpreted. However, the holding registers can...
Thomas Kühn 7 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Unlikely to support

select multiple devices via checkbox at bulk operations

we want to achive to execute a bulk operation for more than one devices. for that i expected to select more devices (e.g. 4) via checkbox in the appropriate dialoge. similiar to add target devcie to a group, we expect the same for "select target d...
Guest over 2 years ago in Cumulocity IoT Device Mgmt. & Connectivity 2 Future consideration

When device type is deleted remove related objects

This would help customer mange many device at one time. For example customer has 1000 child devices of one device type and after some time this device type is no longer supported. Customer has to manually remove 1000 child devices and he has to be...
Mirela Kovacevic almost 2 years ago in Cumulocity IoT Device Mgmt. & Connectivity 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

Download Proxy for Software / Firmware images

The IoT platform could provide a download proxy that provides access to the original download endpoint. This would: a) simplify authentication problems and b) could implement on-the-fly (delta) compression and c) could allow resuming the download ...
Nikolaus Neuerburg over 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity / Device Management 0 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