Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

My feedback: Cumulocity IoT Device Mgmt. & Connectivity

Showing 96 of 376

Access timestamp from custom LwM2M decoder microservice

When a decoder microservice is used as a custom action to process a LwM2M payload, it would be useful to have access to the timestamp if it it present in the SenML-JSON/CBOR message. That is, if the payload is received by the LwM2M agent as the re...
Guest about 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 2 Future consideration

Create a new UI widget that uses a LwM2M object or objects as a data source

Create a new UI widget that uses a LwM2M object or objects (via a composite read) as a data source. This configurable widget (list, table, chart, etc) could be added, like other widgets, to the C8Y Device Management application.
Iain Mackenzie 6 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Unlikely to support

Bulk device registration – Support json & xml files

Currently, for LwM2M devices, bulk registration only supports csv files. It would be useful if other file types, in particular json & xml were supported as well. It would also be useful if these files supported the addition of custom device at...
Iain Mackenzie 6 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Partially supported already

Device names from OPCUA server

The device name is generated automatically. It would be helpful if the name could be read from the OPCUA server and used as the device name.
Marius Walzog 6 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Future consideration

Feature Request Ops to Dev: Change Rollout Success Notification for Cases where SW is already deployed

Description Would like to file a feature request: "Change Rollout Success Notification for Cases where SW is already deployed". During the MVoIP project we stumbled upon cases where MVoIP was displayed on the UI as redeployed successfully again al...
Manash Baruah about 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Unlikely to support

LwM2M – C8Y should not implement queuing when a device registers with queue mode = false

For a LwM2M device, C8Y always performs queuing even if queue mode is set to false (Binding Mode: U) on registration. This can be observed by: Device successfully registers. A read (or write) is issued from the shell, but due to say a temporary lo...
Iain Mackenzie 7 months ago in Cumulocity IoT Device Mgmt. & Connectivity 3 Likely to support/improve

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

LWM2M custom decoder for a whole object

For some objects, it is more efficient for a device to report whole object in one message. Therefore it would be good to have a possibility to use custom decoder on the whole object and not resource by resource. Location updates already work this ...
Peter Gaspar about 4 years ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1 Future consideration

LwM2M - Show the newest location of a device in the Map widget

Hi, as defined by the LwM2M standard, while creating a new LwM2M observer the actual value will be returned. In addition, Cumulocity automatically creates a location event with a timestamp and position fragment without a timestamp while observing ...
Guest 7 months ago in Cumulocity IoT Device Mgmt. & Connectivity 2 Planning / planned

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