Skip to Main Content
Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

All feedback

Showing 377 of 377

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 6 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1

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 3 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Unlikely to support

Digital Twin: Include last measurements and events in the managedObject of the device

To improve performance of dashboards, and to allow faster access to digital twin, it would be good, if for each measurement and event type, the last received object was also cached in the managedObject. In case new measurement/event of the same ty...
Peter Gaspar over 2 years ago in Cumulocity IoT Platform Services / Data at Rest 4 Planning / planned

Association templates, to link device features (measurements, alarms etc.) to Digital Twin Assets

The Digital Twin Manager is a powerful tool for defining asset "type" data models. However, once an asset has been defined, the intuition and value of what a device represents begins to change... Really, a device now only represents and endpoint i...
Neil C over 1 year ago in Cumulocity IoT Digital Twin Manager 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 6 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Future consideration

Improvement child device view

How do I recognize the assignment to a "parent" device of a child device in the platform? If I am looking for a child device, e.g. by name, then at least I get the view in Device Management. there I can't see the assignment to the "root" device, ...
Guest over 2 years ago in Cumulocity IoT Device Mgmt. & Connectivity 0 Likely to support/improve

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 6 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Future consideration

Extended system of units, and units conversion

Currently, Cumulocity has a rudimentary model for systems of units. It recognises metric and imperial units systems, and the API will convert measurement values between them. https://cumulocity.com/api/10.15.0/#section/System-of-units Metric Imper...
Neil C about 1 year ago in Cumulocity IoT Cockpit and WebSDK / Dashboarding / Data Point Library 1 Likely to support/improve

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 7 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 7 months ago in Cumulocity IoT Device Mgmt. & Connectivity 5 Future consideration