Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

All feedback

Showing 408 of 408

Lwm2m x509 authentication should validate the full certificate chain during initial DTLS handshake

Lwm2m x509 authentication should validate the full certificate chain during initial DTLS handshake This feature is an enhancement that should allow a more efficient way to validate a chain of certificates that occur in an advanced manufacturing. V...
Andrew Nowak 4 months ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 2 Planning / planned

Allow dashboard templates for Child Devices as well

We recently updated the Cockpit to the current version, and we are currently testing the Dashboard Manager on our tenants. While the initial feedback is positive, we have noticed limitations in functionality for child devices. Specifically, in our...
Lucas Wilbers 3 months ago in Cumulocity IoT Cockpit and WebSDK / Dashboarding 0

LwM2M: list resources according to their ID

Currently the L2M2M resources are listed in an undefined sequences. Most often the resource sequence is alphabetic, but not always (Device Management->Objects->Device\3\0). The resources should be listed according to their ID. This is how it...
Guest 3 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Planning / planned

Get more detailed info about users

Hello, It would be great to have more info on users like : Creation date Last login date
Guest about 2 months ago in Cumulocity IoT Platform Services 0

Google Cloud Storage Support for DataHub

Offloading to Google Cloud Storage as a supported data lake for DataHub.
Chris Furlong almost 3 years ago in Cumulocity IoT DataHub 1 Future consideration

Archive Feature for Microservice Application

Frontend applications have the archive feature but it is not supported for microservice applications on our tenants and it makes it hard to switch between versions for microservices. Need rollback option, as for Applications.
oana velicu over 1 year ago in Cumulocity IoT Platform Services / Product Infrastructure & Microservices 2 Future consideration

Cumulocity Edge should support LwM2M protocol

Cumulocity Edge should support devices communicating using the LwM2M protocol. This would allow deployments with devices that do not support C8y's REST/MQTT protocols and/or require a more lightweight transport protocol than HTTPS (i.e. COAPS). Th...
Guest 6 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Partially supported already

Easy Data Export for Machine Data

Currently, many Cockpit users struggle with the Data Export functionality. The top 2 pain points are: The data export only works for users with access to all devices (global inventory access). However, in e.g. equipment rental cases where an admin...
Nikolaus Neuerburg over 1 year ago in Cumulocity IoT Cockpit and WebSDK / Exports / Widgets 2 Planning / planned

Notification 2.0 - Each API need to have own Subscription Filter

Currently, Notification 2.0 Subscription Filters are not tied to the respective API. It's a common filter for API lists. Ideally, the same service is required to process Events, Alarms but filter conditions are different for each one.
Venkatesu Punugupati 4 months ago in Cumulocity IoT Platform Services 1 Future consideration

Notification 2.0 Subscription Filters Allowing Custom Attribute Filter along with Type Filter

Some cases "Type Filter" is not good enough to filter events, alarms. It's better to give flexibility for user to allow configure custom attribute and it's filter conditions along with "Type"
Venkatesu Punugupati 4 months ago in Cumulocity IoT Platform Services 1 Future consideration