Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

Cumulocity IoT Device Mgmt. & Connectivity

Showing 106

Devicelist - Registration date filter - date in future should be greyed out in popup

steps: open an devicemngt instance navigate to devicemngt > all devices list click filter registration date > popup with filter options appear choose future date (e.g. the day after today) in field "Show devices registered after" choose fute...
Guest over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 2 Unlikely to support

Have time parameter be optional on the REST create event request similar to how the create event static template works in MQTT

Device time is not always accurate. As BIOS batteries wear down, device time can change every time a device is powered of. This makes event reporting inaccurate when using device time. By having this be an optional field, the system time could be ...
Dave Presuhn over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Unlikely to support

Software & configuration update operations lifecycle should include a "Locally Staged" step

In common with many industrial equipment manufacturers, our customers are cautious about over-the-air updates for devices in thier facilities. A common request is for a local approval step in the application of software updates and configuration c...
Neil C almost 2 years ago in Cumulocity IoT Device Mgmt. & Connectivity 3 Future consideration

Honor UI consistency by moving button for adding new OPC UA Server to top of management page for OPC UA Gateway devices

The default location for any "add XXX" functionality for c8y web interface is always top right in the "page-toolbar". However, after registering an OPC-UA gateway, the "Add Server" button on sub menu "OPC UA server" is located at the bottom of the...
Guest almost 2 years ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Already supported

Add OPC/UA pub/sub to the opc/UA agent

We should be able to connect the opc-ua agent to the OPC UA standard and the the whole integration between devices should work out of te box. https://www.prosysopc.com/blog/opc-ua-pubsub-explained/ So publishing information from the device should ...
Guest almost 2 years ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Future consideration

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 almost 4 years ago in Cumulocity IoT Device Mgmt. & Connectivity / Cloud Fieldbus 2 Future consideration

Device tracking should update with all movement as you change the time frame

We noticed a strange behavior with the Tracking option for a device, under the Device Management application. When we reselect the date / time range from, say, “Last hour” to “Last day”, the map doesn’t seem to update to show all the movement in t...
Guest about 2 years ago in Cumulocity IoT Device Mgmt. & Connectivity 3 Planning / planned

When the system language is set to Simplified Chinese, the device status time display is changed to 24 hours or the option to set the time display format is added.

When the system language is set to Simplified Chinese, in the "All devices" option of MindConnect IoT Extension, the time format of the current device connection status is changed from 12-hour system to 24-hour system, or the option that the user ...
Guest about 2 years ago in Cumulocity IoT Device Mgmt. & Connectivity 5 Clarification needed

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 about 2 years ago in Cumulocity IoT Device Mgmt. & Connectivity 3 Clarification needed

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 about 2 years ago in Cumulocity IoT Device Mgmt. & Connectivity 3 Already supported