Skip to Main Content
Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

Cumulocity IoT Device Mgmt. & Connectivity

Showing 96 of 376

To have an option to delete multiple device assets at once from the UI

Currently, the Cumulocity UI only offers an option to delete one device at a time which becomes quite tedious if bulk devices needs to be removed. With bulk device registration option in place, it makes sense to have an option for bulk deletion of...
Mohammed Ali Khan 7 months ago in Cumulocity IoT Device Mgmt. & Connectivity 2 Future consideration

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 7 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Unlikely to support

Certificate refresh for connected devices

One method to authenticate devices to the platform is certificate-based authentication. But to enhance security, a growing number of standards and best practise guides are encouraging device manufacturers to issue certificates for their devices wi...
Neil C over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 2 Planning / planned

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

LwM2M: Change implementation to not count connector as device

Currently (c8y 10.16) LwM2M creates a "LwM2M Connector Device" which is available in the All Devices list and has the c8y_IsDevice fragment. This fragment is actually a key element for device-count in tenant-statistics, so when LwM2M is added on a...
Christoph Marschall 9 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Planning / planned

MEA types/series names should not be altered by LwM2M agent

The LwM2M agent adds a suffix to the type (and series, for measurements) of measurements, events, and alarms that it creates from received values. The suffix reflects the object instance and resource ID in the resource path. This alteration means ...

Request to add device LastCommunication date field to the standard columns list in device list table

It's good to have device LastCommunication date to the standard columns list(Device Management-> All devices-> standard columns of the table AND Cookpit->Groups->Subassets ). We used to get regular customer incidents for device disconn...
Santhosh Thakkalapally 6 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Likely to support/improve

LwM2M PSK should not be available in plaintext

The LwM2M config (including PSK ID and keys for bootstrap and server authentication) is available/displayed in plaintext through the API and UI. This is in contrast to the secure provisioning of standard device credentials (password), which cannot...
Guest 9 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Likely to support/improve

LwM2M - Standards-based Server API Support

Today, each LwM2M Server has a proprietary API interface that external systems can use for integration. This requires costly server-specific integration work and support. We understand that OMA is working on adding a standards-based Server API. Li...
Iain Mackenzie 6 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1

device protocol interprete holding register as DINT/REAL

In the "New holding register" dialog of the device protocols it is possible to configure the transformation of the passed bits. The number of bits can be configured. However, only integer numbers are interpreted. However, the holding registers can...
Thomas Kühn 3 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Unlikely to support