Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

Cumulocity IoT Device Mgmt. & Connectivity

Showing 94 of 372

Add ability to Report devices in export for a Top-Level-Group with Devices in Sub-Sub Groups

Customer has built a group structure with subgroups to organize his devices.The structur contains serveral top level groups with subgroups to organize its device. The customer is now trying to export a report on all devices by selecting the top le...
Juergen Hahl 9 months ago in Cumulocity IoT Device Mgmt. & Connectivity 0

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 about 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 4 Planning / planned

Implementation of Wildcard search option at Device credentials page

Currently Device Credentials page is not having any filtering option on the basis of wild search. Also we are not observing sorting option as well. So we are proposing the implementation of the filtering on the basis of wild search(*) and Sorting ...
Akshay Zade 5 months ago in Cumulocity IoT Device Mgmt. & Connectivity 4 Future consideration

Implementation of Sorting and Filtering options for Device registration page

Currently Device Registration page has no sorting and filtering options availabl We are proposing the implementation of the below that would enhance the UI experience and also help in troubleshooting for Device Registration page(Device Management=...
Akshay Zade 5 months ago in Cumulocity IoT Device Mgmt. & Connectivity 4 Future consideration

Create a new UI widget that uses a LwM2M object or objects as a data source

Create a new UI widget that uses a LwM2M object or objects (via a composite read) as a data source. This configurable widget (list, table, chart, etc) could be added, like other widgets, to the C8Y Device Management application.
Iain Mackenzie 6 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Unlikely to support

Bulk device registration – Support json & xml files

Currently, for LwM2M devices, bulk registration only supports csv files. It would be useful if other file types, in particular json & xml were supported as well. It would also be useful if these files supported the addition of custom device at...
Iain Mackenzie 6 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Partially supported already

Device names from OPCUA server

The device name is generated automatically. It would be helpful if the name could be read from the OPCUA server and used as the device name.
Marius Walzog 6 months ago in Cumulocity IoT Device Mgmt. & Connectivity 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

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 12 months 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 12 months ago in Cumulocity IoT Device Mgmt. & Connectivity 2 Future consideration