Skip to Main Content
Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

All feedback

Showing 374 of 374

[DataHub] How do user know if the Offloading has been flushed or appended from the Auditing logs

First, currently when a user tries to stop and start the offloading the task by selecting to flush the available data in data lake, there is no record of this anywhere in the Auditing(Query/System) logs other than just that the task was stopped an...
Shaopeng (Jeffrey) Song 11 months ago in Cumulocity IoT DataHub 0 Likely to support/improve

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 11 months ago in Cumulocity IoT Platform Services / Data at Rest 4 Future consideration

Alarm List Sort by Date

Add ability to sort default ALARM LIST widget by date: both ascending and descending order. Intention is to show recent alarms of all severity levels in reverse order.
Sean Thomas 11 months ago in Cumulocity IoT Cockpit and WebSDK / Alarms / Widgets 1 Planning / planned

User configurable data partitioning

Allow user to configure data partitioning scheme at offloading time i.e. rather than partition offloaded data by create time, allow user to configure partitioning by device, device group, etc. based on how they expect to query the data for improve...
Chris Furlong 11 months ago in Cumulocity IoT DataHub 1 Likely to support/improve

Digital Twin Manager - Blacklist / restrictions for custom properties with key type and id

See https://getsupport.softwareag.com/servicedesk/customer/portal/2/SI-506280 Idea:There should be a blacklist, which contains keys, which must not be used by users and are marked as built-in.Also the input field for key should have restrictions r...
Juergen Hahl 12 months ago in Cumulocity IoT Digital Twin Manager / Asset Properties 1 Planning / planned

Password-change UX should consider server-synchronization

When a user changes the password (today in Cumulocity v10.15), the UX provides a success-message of the change without any conditions. However, the password may not be usable for some additional minutes as the change has not been synchronized acro...
Christoph Marschall 12 months ago in Cumulocity IoT Platform Services / Authentication & Authorisation 1 Likely to support/improve

Device Stats API - c8y_IsDevice & Device Name

The Device Statistics API should have an indication whether the inventory object is marked c8y_IsDevice or not. Some customers use this fragment to identify devices, and it would make identification of each device easier. In addition, the Device S...
Tal Dunne 12 months ago in Cumulocity IoT SaaS Enablement 0 Future consideration

Exchange referenced OPC UA Server in device protocol

When creating a device protocol I need to reference a Server.After some time, this server may be not existing anymore. Without this server, there is a problem in editing/changing the device protocol. It would be very easy to reference another (exi...
Manfred Strasser 12 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Unlikely to support

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

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