Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

My feedback: Cumulocity IoT Device Mgmt. & Connectivity

Showing 95 of 376

Accept option of observes must be selectable - LWM2M implementation

The accept option tells the lwm2m client which encoding to use in a response. This could be TLV, JSON or others. There are situations (for example for buffering data) where it is necessary to select the accept option manually. TLV does not contain...
Guest almost 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1 Unlikely to support

Custom Action on Instance Level - LWM2M implementation

Reaction on notifications are not always solely based on a single resource. In the majority of the cases there are multiple resources involved, especially the timestamp is an important field. It must be possible to configure custom actions on inst...
Guest almost 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1 Future consideration

Download Proxy for Software / Firmware images

The IoT platform could provide a download proxy that provides access to the original download endpoint. This would: a) simplify authentication problems and b) could implement on-the-fly (delta) compression and c) could allow resuming the download ...
Nikolaus Neuerburg about 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity / Device Management 0 Future consideration

Unix timestamp option for smartrest template timestamps

Having an option for unix timestamps (i.e. 1613952862) instead of ISO8601 in the smartrest templates will reduce the data sent from 20 bytes to 10 bytes for each timestamp submitted. This saving can quickly add up for devices sending lots of measu...
Guest about 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity 0

Make devices list columns configurable

Currently, every user can configure the columns displayed in the "All Device" list within the Device Management application for themselves. However, in many cases a system administrator wants to change the default configuration for the columns for...
Guest over 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity / Device Management 0 Likely to support/improve

Device Management List

Please fix the First Row that this is fixed and not be disappears once you scroll down to see more devices
Guest over 3 years ago in Cumulocity IoT Device Mgmt. & Connectivity 2 Already supported

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

Filter events by time and not just by date

Machines from Weber Maschinenbau create thousands of events per day representing state changes of the machines. In Device Management when looking at the event list, it is only possible to filter for full days instead of timestamps like it is possi...
Guest almost 4 years ago in Cumulocity IoT Device Mgmt. & Connectivity 0 Likely to support/improve

make simulator name not editable

https://migration105-ramazure_02.ram.m2m.telekom.com/apps/devicemanagement/index.html#/simulators/224373/instructions V 10.5.0.7 login: c8y / Test1234 steps: edit existing simulator > change simulator name and add some new instructions expected...
Guest about 4 years ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Already supported

Cloud Fieldbus support for float32 via Modbus

At the moment, the Cloud Fieldbus feature and the Modbus Linux agent only support integer measurements. A number of Modbus devices now actually support float values (typically 32Bit IEEE-754) which currently have to be converted manually using a m...
Guest about 4 years ago in Cumulocity IoT Device Mgmt. & Connectivity 0 Unlikely to support