Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

Cumulocity IoT Device Mgmt. & Connectivity

Showing 94 of 372

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 8 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Planning / planned

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

LwM2M events and alarms text placeholders

The LwM2M agent can create measurements, events, and alarms when resource values are read from or sent by an LwM2M device using additional functionalities. It seems that the text that is included in the creation of the event or alarm is a static s...
Guest 11 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Likely to support/improve

Audit log is missing device protocol XML added/deleted

In our tenant we have multiple products being developed, some of which use the same LwM2M definitions. If a user deletes/adds/modifies a LwM2M definition we have no tracking in the audit logs of who did that. Everyone on the system needs the abili...
John Fisher 12 months ago in Cumulocity IoT Device Mgmt. & Connectivity 4 Clarification needed

Export/Import Device Management->Device protocol XML resource mapping

If a user configures a bunch of Lwm2m XMLs and links each resource with MEAs or custom actions inside one tenant, this work cannot be easily exported to another tenant and thus requires manually setting all of this again.
John Fisher 12 months ago in Cumulocity IoT Device Mgmt. & Connectivity 2 Future consideration

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 about 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 4 Planning / planned

When device type is deleted remove related objects

This would help customer mange many device at one time. For example customer has 1000 child devices of one device type and after some time this device type is no longer supported. Customer has to manually remove 1000 child devices and he has to be...
Mirela Kovacevic over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Future consideration

Make devices list columns configurable

Currently, every user can configure the columns displayed in the "All Device" list within the Device Management application for themselves. However, in many cases a system administrator wants to change the default configuration for the columns for...
Guest over 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity / Device Management 0 Likely to support/improve

Cloud Fieldbus support for float32 via Modbus

At the moment, the Cloud Fieldbus feature and the Modbus Linux agent only support integer measurements. A number of Modbus devices now actually support float values (typically 32Bit IEEE-754) which currently have to be converted manually using a m...
Guest about 4 years ago in Cumulocity IoT Device Mgmt. & Connectivity 0 Unlikely to support

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