Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

Cumulocity IoT Device Mgmt. & Connectivity

Showing 106

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

Feature Request Ops to Dev: Change Rollout Success Notification for Cases where SW is already deployed

Description Would like to file a feature request: "Change Rollout Success Notification for Cases where SW is already deployed". During the MVoIP project we stumbled upon cases where MVoIP was displayed on the UI as redeployed successfully again al...
Manash Baruah over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Unlikely to support

License Management

Several of our product teams are working on ways to monetize the software on the fielded medical capital equipment. Having a module available to measure and manage licenses would be very helpful to distribute licensed software to specific devices ...
Dave Presuhn 10 months ago in Cumulocity IoT Device Mgmt. & Connectivity 3

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 about 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1 Future consideration

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

System_ID should be numerically sorted instead of string sorting

System_Id is a numeric id auto generated by the c8y platform for every managed object. This is however treated as string instead of numeric when sorting is performed which gives incorrect sorting results. This incorrect sorting results gives misle...
Mohammed Ali Khan over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 3 Unlikely to support

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