Skip to Main Content
Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

Cumulocity IoT Device Mgmt. & Connectivity

Showing 33

When device type is deleted remove related objects

This would help customer mange many device at one time. For example customer has 1000 child devices of one device type and after some time this device type is no longer supported. Customer has to manually remove 1000 child devices and he has to be...
Mirela Kovacevic over 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Future consideration

LwM2M - Standards-based Server API Support

Today, each LwM2M Server has a proprietary API interface that external systems can use for integration. This requires costly server-specific integration work and support. We understand that OMA is working on adding a standards-based Server API. Li...
Iain Mackenzie 8 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Future consideration

Easier way to search for events in the LwM2M events log

When searching for logs in the events tab (either from the overall events stream in the Device Management or from the device itself), we can only search for event types such as: c8y_CBOR_DECODING_EVENT lwm2m_log c8y_LWM2MDeviceRegistration Howeve...
Laudemhir Jan Parel 8 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Future consideration

LwM2M - Non-Confirmable Message Support

Current LwM2M standards require all LwM2M messages to be confirmed. Itron understands that OMA will soon be adding an option to selectively disable message confirmation. Changes to both LwM2M server and LwM2M clients will be needed to deliver non-...
Iain Mackenzie 8 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Future consideration

LwM2M – Support for version 1.2

While several C8Y competing, products are supporting LwM2M version 1.2 features (AVSystems, Ioterop, Friendly Technologies...), SAG's C8Y is lagging and has not yet released LwM2M 1.2 support. The following 1.2 features are increasingly becoming i...
Iain Mackenzie 8 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Future consideration

LwM2M – Complete support for version 1.1

The following LwM2M 1.1 features are currently not supported by C8Y and are important to Itron: OSCORE - preferred E2E security solution by the Itron security team and a fundemental requirement for a couple of projects (water metering). Multi-inst...
Iain Mackenzie 8 months ago in Cumulocity IoT Device Mgmt. & Connectivity 5 Future consideration

Read out a OPC UA server via the OPC UA client

I would like to read out a OPC UA server via the OPC UA client possibilities of C8y. I have several tags that I need to capture at 50 ms which is not problem. However to avoid having a lot of data, I have a trigger available to me that tells me wh...
Guest 9 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Future consideration

Allow custom LwM2M decoder microservice to create/update arbitrary inventory fragments

A custom decoder microservice can return dataFragments to the LwM2M agent in order to update the managed object, but this is only capable of updating the fragment specific to the LwM2M resource, e.g. "dataFragments" :[ { "value" : "Hello World" , ...
Guest about 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 2 Future consideration

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

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