Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

All feedback

Showing 407

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

Measurement query for specific group of devices

In the API for Measurement there is no possibility to query for Group Devices. If I have same Device Types with the same Measurement Structure (Type,Fragment,Series) there is no easy way to delete measurements for a group of Devices. It is only po...
Guest over 2 years ago in Cumulocity IoT Platform Services / Data at Rest 1 Future consideration

[Sensor App] Ability to choose group to which phone is assigned

Hi, As part of our IoT Education Package we are making heavy use of the Cumulocity IoT Sensor App. We are also providing a team based device visibility based on Cumulocity Role Based Access Control features. I.e. a group of users shall only see th...
Guest over 2 years ago in Cumulocity IoT Mobile Apps 0

Implementation of checks/warnings upon creations of multiple primary groups with exact similar name

Currently it is seenthat the user is able to create two or more primary groups with exact similar name without any notification/warning, which in turn causes problem when bulk registration of devices are performed. It would be a good idea to imple...
Mohammed Ali Khan over 2 years ago in Cumulocity IoT Cockpit and WebSDK / WebSDK 4 Planning / planned

Fix filter mechanism

[internal ticket TTCON3G-2267] On certain pages, the filter mechanism only searches through items shown on a page. This means that if an item is not listed on the respective page, it will not appear in the results. User needs to load all results f...
oana velicu over 2 years ago in Cumulocity IoT Device Mgmt. & Connectivity 3 Clarification needed

Introduce Device Type to DataPoint Library

Currently, a user can define Data Point library entries based on their fragment/series and the Library Entry applies to each measurement producing measurements with exactly these fragment/series combination. My idea is to introduce an optional fie...
Korbinian Butz over 2 years ago in Cumulocity IoT Cockpit and WebSDK / Data Point Library 0

VSphere DRS issues with hazelcast on core nodes

VSphere DRS is autoleveling ESXi hosts load by automated migrations of virtual machines. When DRS wants to migrate core nodes, it causes hazelcast malfunction, that is spread all other core nodes. This is causing a significant short performance dr...
Ramon Peters about 1 year ago in Cumulocity IoT Platform Services / Product Infrastructure & Microservices 1 Already supported

Per-Device Expectation Configuration with Alarming

On each device, I would like to set the expected data frequency, and receive an alarm if the actual frequency goes above this value. Use case: I know my device is supposed to send 20 MEAs/day, but for some reason it is sending 30 MEAs/day. I need ...
Tal Dunne about 1 year ago in Cumulocity IoT SaaS Enablement 0

Recycle bin feature

Currently recycle bin feature is not supported for any of the following items, if deleted: Device protocol – we learned from raimondi that it may stop the transmission of all devices with it Device – customer may delete a device by mistake, after ...
oana velicu about 1 year ago in Cumulocity IoT Platform Services / Data at Rest 0 Future consideration

For users created via SSO, display a more user-friendly value in the upper right corner (where the user menu is).

Sometimes the value of the User ID for users created via SSO is just a UUID value, i.e. some random string. This way it is difficult to understand which is the currently active user. Ideally a name or an email address would be displayed, similar t...
Guest over 3 years ago in Cumulocity IoT Platform Services / Authentication & Authorisation 0 Future consideration