Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

All feedback

Showing 148

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

Retention Rule for Binary Store

We create exports in our application. Now it would be nice to have the possibility to create a retention rule to delete exports older than x-days. ATM that seems not be possible.
Florian Gopp about 2 years ago in Cumulocity IoT Platform Services / Platform Management 1 Future consideration

Provide Import / Export in Data Point Library

A user can define parameters in one tenant, but then can't utilize the same in another tenant. User should be able to export data point library from one tenant to another so that they can be used more often and with ease
Rahul Talreja over 1 year ago in Cumulocity IoT Cockpit and WebSDK / Data Point Library 0 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 about 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1 Future consideration

Support for bulk alarm uploads using normal REST

No REST support for uploading bulk alarms. Many of our field devices don't have the capability to communicate with the cloud directly, and hence when it is connected to the docking station, the docking station will download all the data from the f...
Guest 10 months ago in Cumulocity IoT Platform Services / Data at Rest 1 Future consideration

Databroker filtering process

Filtering process is not good enough. It does not allow to filter by different fragments. We need to create 1 filter per fragment. It would be nice to have some sort of "OR" filter for fragments, so we could add as many fragments as needed into 1 ...
Guest over 1 year ago in Cumulocity IoT Platform Services / Data in Motion 0 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

message "out of data range" should be availavle for all gauge widgets

i have a device which is sending data (just one measurement here: temperature) in the range -50 until 50 also i created a dashboard with all available gauge widget (info, linar, radial) and silo widget (which are shown just the data point temperat...
Guest over 1 year ago in Cumulocity IoT Cockpit and WebSDK / Widgets 1 Future consideration

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