Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

All feedback

Showing 406

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 7 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Clarification needed

Global time selector: Zooming in to one graph should reflect in other graphs too

With the new global time selector the time can only be selected in the top bar of the Dashboard. It would be very user friendly if the time selection would work similarly to Grafana. When zooming into the data point graph widget the user can also ...
Kai Sieben about 1 year ago in Cumulocity IoT Cockpit and WebSDK / Dashboarding / Widgets 1 Likely to support/improve

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 7 months ago in Cumulocity IoT Cockpit and WebSDK / Alarms 0 Planning / planned

Analytics Builder "Simulation Mode" should support simulating groups of devices

Analytics Builder currently has a simulation mode, which allows an Analytics Builder to consume historical data from the Operational Store (MongoDB), and feed it in real-time to a model. However, this simulation capability is limited to models tha...
Neil C about 2 years ago in Cumulocity IoT Streaming Analytics (inc. Apama) / Analytics Builder 0 Future consideration

Exporting Chart Data in CSV ,XLSX, PDF or any other formats

Allow exporting the rendered chart data in CSV, XLSX, PDF or any other formats Sample: How will this help ? Solution administrators can create the dashboards, while the end user can change the time range as per choice and download the data in csv ...
Rahul Talreja over 1 year ago in Cumulocity IoT Cockpit and WebSDK 0 Planning / planned

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 over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 6 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 7 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Clarification needed

User-defined 'Titles' and usage 'Descriptions' for Analytics Builder block instances

Even relatively simple models in Analytics Builder can be tricky to understand. Right now, the only method to document the design intent, or the method of operation of a model is to enter a lengthy description into the "Description" field in the M...
Neil C over 1 year ago in Cumulocity IoT Streaming Analytics (inc. Apama) / Analytics Builder 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 almost 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1 Planning / planned

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 almost 5 years ago in Cumulocity IoT Platform Services / Data at Rest 3 Future consideration