Skip to Main Content
Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

All feedback

Showing 381

To be able to identify the Tenant primary Admin from the list of users in the Administration application

Currently there is no means to identify the Tenant primary admin from the other admins in the tenancy. All admins are displayed in the similar fashion and It creates a sense of confusion to differentiate between the primary admin and other admins....
Mohammed Ali Khan 9 months ago in Cumulocity IoT Platform Services / Platform Management 2 Clarification needed

Option to cancel Pending operations in bulk from Device Control Screen

Currently pending operations queued for devices can only be cancelled one at a time, which becomes quite tedious if there is huge set of wrong pending operations that is queued and needs cancellation. User can possibly set wrong operations for a d...
Mohammed Ali Khan 9 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Unlikely to support

We have a customer requirement to be able to send data to Cumulocity IoT using SparkPlugB over MQTT. Is this something that could be included?

No description provided
Guest 3 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Clarification needed

Datetime range filtering in All Alarms list

The Alarm list provides great overview of the tenant. Unfortunately there is not enough filtering, thus for some customers it is just not useful to keep scrolling all the time to find relevant data. This is problem is highlighted specifically when...
Georgi Huklev 3 months ago in Cumulocity IoT Cockpit and WebSDK / Alarms 0 Planning / planned

Extended system of units, and units conversion

Currently, Cumulocity has a rudimentary model for systems of units. It recognises metric and imperial units systems, and the API will convert measurement values between them. https://cumulocity.com/api/10.15.0/#section/System-of-units Metric Imper...
Neil C about 1 year ago in Cumulocity IoT Cockpit and WebSDK / Dashboarding / Data Point Library 1 Likely to support/improve

Notification API 2.0 - Allow to subscribe to measurements to all devices

We would like to subscribe to the measurements from all managed objects (devices) on the platform using the Notification API 2.0. Currently, a subscription must be created for each individual managed object.This makes it easier to subscribe to the...
Thomas Kühn almost 2 years ago in Cumulocity IoT Platform Services 1 Unlikely to support

Public API for LwM2M agent

It would be useful to have a stable API for the LwM2M agent published to https://cumulocity.com/api/. This would allow us to script/automate the following: Create a LwM2M device protocol, i.e. upload a DDF (/service/lwm2m-agent/objectResourceMappi...
Guest about 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Future consideration

Digital Twin: Include last measurements and events in the managedObject of the device

To improve performance of dashboards, and to allow faster access to digital twin, it would be good, if for each measurement and event type, the last received object was also cached in the managedObject. In case new measurement/event of the same ty...
Peter Gaspar over 2 years ago in Cumulocity IoT Platform Services / Data at Rest 4 Planning / planned

Inappropriate response for error reporting during the migration of lwm2m devices

We have noticed an inappropriate response for error reporting during the migration of lwm2m devices in one of our customer tenancy. device count for migration success/failure is reported as null instead of actual count. Customer attempted to migra...
Santhosh Thakkalapally 3 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Clarification needed

add a field "received_time" in measurements

I have a use case with logical devices that send batches of measurements. It happens that the data is completed or recomputed at ground side and measurements are sent again to Cumulocity. We experience problems when deleting existing measurements ...
Guest about 1 year ago in Cumulocity IoT Platform Services / Data at Rest 4 Future consideration