Skip to Main Content
Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

Cumulocity IoT Device Mgmt. & Connectivity

Showing 94 of 372

System_ID should be numerically sorted instead of string sorting

System_Id is a numeric id auto generated by the c8y platform for every managed object. This is however treated as string instead of numeric when sorting is performed which gives incorrect sorting results. This incorrect sorting results gives misle...
Mohammed Ali Khan over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 3 Unlikely to support

Cumulocity SNMP Protocols should allow explicit casting of strings to integer/float

We can currently manually configure a SNMP Protocol component through the Device Management application, which allows us to request a specific OID from a SNMP device, and map it to a measurement (or event/alarm) in Cumulocity. However, if the devi...
Neil C over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Unlikely to support

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

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

Add warnings when deleting objects with dependent linked objects

Please add warnings when deleting objects with dependent linked objects. Preferably, we would also have an option for cascade deletion. Example: deleting device protocol affects child devices that reference it.
oana velicu 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 over 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity / Cloud Fieldbus 2 Future consideration

Firmware/Software mgmt: Store documents, like terms & conditions and release notes to each firmware/software

Enhance the firmware/software repository and management by adding the functionality to attach (multiple) documents to each firmware/software. Documents could be Terms & Conditions and release notes.Optionally each document can be categorized ...
Guest over 4 years ago in Cumulocity IoT Device Mgmt. & Connectivity / Software Management 1 Unlikely to support

Inappropriate response for error reporting during the migration of lwm2m devices

We have noticed an inappropriate response for error reporting during the migration of lwm2m devices in one of our customer tenancy. device count for migration success/failure is reported as null instead of actual count. Customer attempted to migra...
Santhosh Thakkalapally 25 days ago in Cumulocity IoT Device Mgmt. & Connectivity 0

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

device protocol interprete holding register as DINT/REAL

In the "New holding register" dialog of the device protocols it is possible to configure the transformation of the passed bits. The number of bits can be configured. However, only integer numbers are interpreted. However, the holding registers can...
Thomas Kühn 2 months ago in Cumulocity IoT Device Mgmt. & Connectivity 0