Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

All feedback

Showing 372 of 372

Clicking on non-device objects (like microservices) from events needs to be displayed in a separate screen, other than the device info page

Currently, clicking on non-device objects such as microservice application from events, opens the device info page for that object which is ideally not correct nor user-friendly. Issue impact? When users have large amount of assets (devices/non-de...
Mohammed Ali Khan over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 3 Clarification needed

Add additional {{ variables }} to HTML Widget, to convey widget dimensions

The widget is currently capable of passing the following variables: {{device}} – current device or group, you can access its properties e.g. {{device.name}}, {{devices}} – children of current device or group, you can access their properties e.g. {...
Neil C almost 2 years ago in Cumulocity IoT Cockpit and WebSDK / Dashboarding 1 Unlikely to support

Group commands for LwM2M

When operating at scale (100K+ devices in a single tenant), it is critical to have ability to issue commands once that apply to a group of devices. A standard API that accepts a list of device groups and a list of LwM2M shell commands is needed. A...
Guest almost 2 years ago in Cumulocity IoT Platform Services 1 Clarification needed

Cloud Fieldbus UI: Validation of fragment / series names

Our Customer TT-Control has following issue: Incident: 5428979 Basically the problem of TTC is that their customers uses spaces when they define device types in holding registers. The problem results in empty reports. TTC asks if it is possible to...
Guest over 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity / Cloud Fieldbus 2 Future consideration

Domain Name Validation when creating Sub Tenant

It would be helpful to directly check the filled in sub domain name if it is still available instead of doing this validation when hitting the save button.
Marco Biegel almost 2 years ago in Cumulocity IoT Platform Services / Platform Management 0 Future consideration

Need hook for performing validations on JSON file in Device Protocols

Internal ticket: TTCON3G-2287 No validation is currently done when importing a device type from a JSON file in the Device Protocol view and this leads to invalid protocols. This causes issues on customer side. TTControl requests a hook to be able ...
oana velicu almost 2 years ago in Cumulocity IoT Device Mgmt. & Connectivity 3 Already supported

Optimize OPC-UA gateways' address scanning

As many of the PLC's and Yokogawa historian have vasts amounts of tags they expose the address space of their OPC-UA servers is very large. (500.000+ nodes for Yokogawa, at this point unclear how large in total). The OPC-UA gateway frequently cras...
Misja Heuveling almost 2 years ago in Cumulocity IoT Device Mgmt. & Connectivity 0 Future consideration

webMethods.io CDH Connector

To also have the possibility to upload information and data of 3rd party backend systems to a central hosted data lake. In combinatio with DataHub customers will get more insights of their data. Additionally this would perfectly fit to our company...
Guest almost 4 years ago in Cumulocity IoT Integration 1

Display visual warning on deleting the components used in a profile and a warning that a profiles component does not exist

Device profiles are observed to hold the deleted files/configurations without any notification/warning to the user. This, in-turn, causes unnecessary confusions/issues for the devices assigned with such device profiles. It is highly desirable that...
Mohammed Ali Khan almost 2 years ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Future consideration

Deduplication of alarms doesn't consider severity

If an alarm has the same type and the same source deduplication puts this alarm count. However, if the alarm with same type and source has another severity it is also put to the same group. It can happen that the customer has an alarm with same ty...
Guest almost 4 years ago in Cumulocity IoT Platform Services / Data at Rest 1 Future consideration