Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

My feedback: Cumulocity IoT Device Mgmt. & Connectivity

Showing 95 of 376

LwM2M: Show version of LWM2M object definition file

LwM2M objects can have different version. For instance the object "Connectivity Monitoring" has already 4 versions. We have started to use different version of the same LWM2M object in multiple tenants. However, the version of the is not shown in ...
Guest over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Future consideration

UI support for OPC-UA address space refresh

Situation: We have a device that is connected via OPC-UA to the tenant. Now, the address space on the south (machine) is changing. I learned already that with the help of an operation, the address space in the tenant can be updated. But this is un...
Manfred Strasser over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Likely to support/improve

Certificate refresh for connected devices

One method to authenticate devices to the platform is certificate-based authentication. But to enhance security, a growing number of standards and best practise guides are encouraging device manufacturers to issue certificates for their devices wi...
Neil C over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 2 Planning / planned

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

Remote Access over HTTP to Device UI with Configuration

Some devices have a Configuration tool on the device side which could be accessed over cumulocity with the remote access Microservice. Remote Access does not support http (443) connect. Some of the device configuration are device specific and are ...
Guest almost 2 years ago in Cumulocity IoT Device Mgmt. & Connectivity / Cloud Remote Access 6 Partially supported already

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 almost 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 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