Skip to Main Content
Cumulocity IoT Feedback Portal

All feedback

Showing 31

moving up from child MO to parent MO in the hierarchy issue

Kemin encountered this situation: a Device has a child device assigned. An user has inventory read access on a device group, both devices are assigned to this device group. For Kemins use case, they need to find the ID of the parent device based o...
Guest 18 days ago in Cumulocity IoT Platform Services / Data at Rest 1 Planning / planned

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 3 months ago in Cumulocity IoT Cockpit and WebSDK / Alarms 0 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 ...
Guest 5 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Planning / planned

To be able to edit the custom column added in the All devices page of Device Management

Currently when a user adds any custom column using "header" and "fragement_path" in the All devices page, it is found that those columns are non-editable and can only be deleted. Also the user is not able to view what values were entered for 'head...
Mohammed Ali Khan 8 months ago in Cumulocity IoT Device Mgmt. & Connectivity 4 Planning / planned

LwM2M - Show the newest location of a device in the Map widget

Hi, as defined by the LwM2M standard, while creating a new LwM2M observer the actual value will be returned. In addition, Cumulocity automatically creates a location event with a timestamp and position fragment without a timestamp while observing ...
Guest 9 months ago in Cumulocity IoT Device Mgmt. & Connectivity 2 Planning / planned

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

Branding Editor: provide option to remove app icon and name

There are cases where user does not want to have an app icon or any app name and its unable to remove the same. The hack used by customer is to upload a transparent png image and use app name as .
Rahul Talreja about 1 year ago in Cumulocity IoT Cockpit and WebSDK / Branding 1 Planning / planned

Branding Plugin - Add horizontal navigation bar branding

The branding options for the horizontal navigation bar (see attached sample) is missing in the color options of the branding plugin.
Frank Bauer over 1 year ago in Cumulocity IoT Cockpit and WebSDK / Branding 1 Planning / planned

LwM2M - Bootstrap configurations sent automatically

Problem: While connecting to the Bootstrap server, some of the configurations (Lifetime, pmin, pmax) are automatically sent to the devices, even if the were not specified during the device registration process. This could lead to problem, for inst...
Guest over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 3 Planning / planned

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