Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

All feedback

Showing 127

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

Usage Statistics App - Default Configuration

Overview: The configuration for the usage statistics application should be inherited from a tenant property. This would enable metrics and thresholds to be added by default, rather than having to be added by the end user. In addition, this would e...
Tal Dunne 10 months ago in Cumulocity IoT SaaS Enablement 0 Future consideration

Usage Statistics App - Allow Calculated Metrics & Thresholds

Overview: To support custom pricing models built on top of Cumulocity IoT, the user needs the ability to define custom metrics using the existing data set. In addition, the user should be able to define thresholds on these custom metrics, so that ...
Tal Dunne 10 months ago in Cumulocity IoT SaaS Enablement 0 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

Provide Import / Export in Data Point Library

A user can define parameters in one tenant, but then can't utilize the same in another tenant. User should be able to export data point library from one tenant to another so that they can be used more often and with ease
Rahul Talreja about 1 year ago in Cumulocity IoT Cockpit and WebSDK / Data Point Library 0 Future consideration

Databroker filtering process

Filtering process is not good enough. It does not allow to filter by different fragments. We need to create 1 filter per fragment. It would be nice to have some sort of "OR" filter for fragments, so we could add as many fragments as needed into 1 ...
Guest over 1 year ago in Cumulocity IoT Platform Services / Data in Motion 0 Future consideration

message "out of data range" should be availavle for all gauge widgets

i have a device which is sending data (just one measurement here: temperature) in the range -50 until 50 also i created a dashboard with all available gauge widget (info, linar, radial) and silo widget (which are shown just the data point temperat...
Guest over 1 year ago in Cumulocity IoT Cockpit and WebSDK / Widgets 1 Future consideration

Alarm Synchronization DataBroker

Databroker currently synchronizes objects from edge instance to cloud instance based on events occurring in Cumulocity Edge. Same requests sent to Cumulocity Edge are sent to Cloud instance. When losing connection in the Edge side, Databroker is e...
Guest over 1 year ago in Cumulocity IoT Platform Services / Data in Motion 1 Future consideration