Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

Cumulocity IoT Device Mgmt. & Connectivity

Showing 35

LwM2M – Complete support for version 1.1

The following LwM2M 1.1 features are currently not supported by C8Y and are important to Itron: OSCORE - preferred E2E security solution by the Itron security team and a fundemental requirement for a couple of projects (water metering). Multi-inst...
Iain Mackenzie 11 months ago in Cumulocity IoT Device Mgmt. & Connectivity 5 Future consideration

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

Read out a OPC UA server via the OPC UA client

I would like to read out a OPC UA server via the OPC UA client possibilities of C8y. I have several tags that I need to capture at 50 ms which is not problem. However to avoid having a lot of data, I have a trigger available to me that tells me wh...
Guest 11 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Future consideration

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

Access timestamp from custom LwM2M decoder microservice

When a decoder microservice is used as a custom action to process a LwM2M payload, it would be useful to have access to the timestamp if it it present in the SenML-JSON/CBOR message. That is, if the payload is received by the LwM2M agent as the re...
Guest over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 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