Skip to Main Content
Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

All feedback

Showing 148

Usage Statistics App - Default Configuration

Overview: The configuration for the usage statistics application should be inherited from a tenant property. This would enable metrics and thresholds to be added by default, rather than having to be added by the end user. In addition, this would e...
Tal Dunne about 1 year ago in Cumulocity IoT SaaS Enablement 0 Future consideration

Usage Statistics App - Allow Calculated Metrics & Thresholds

Overview: To support custom pricing models built on top of Cumulocity IoT, the user needs the ability to define custom metrics using the existing data set. In addition, the user should be able to define thresholds on these custom metrics, so that ...
Tal Dunne about 1 year ago in Cumulocity IoT SaaS Enablement 0 Future consideration

case-insensitive filtering in inventory

today, the devices from inventory can only be filtered by case sensitive queries for name or other fragment. Idea is to implement option to filter case-insensitevly. MongoDB provides enough expressions to be used to extend filtering options and st...
Peter Gaspar over 4 years ago in Cumulocity IoT Platform Services / Data at Rest 3 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

API access control for hybrid cloud solutions

If a customer wants to integrate the Cumulocity Web services (APIs) into their own Web application, e.g. a self-service platform for realizing new business models, we call this a hybrid cloud solution. In this case, the customer must pay to use th...
Frank Bauer about 1 year ago in Cumulocity IoT Platform Services / Platform Management 6 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

It should be possible to copy widgets from one dashboard to another

For example, I have an Alarm List widget configured with several custom alarm types (around 30) and I should be able to copy the widget including its list of alarm types over to another dashboard.
Guest almost 2 years ago in Cumulocity IoT Cockpit and WebSDK / Dashboarding / Widgets 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