Skip to Main Content
Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

Data in Motion

Showing 13

Notification 2.0 API - Allow to subscribe to events from all devices

The Notification 2.0 API only allows to subscribe to events for a single device / managing object at a time. Subscription to all events (i.e. at the tenant level) is needed for the wm.io Cumulocity trigger
Frédéric Joulin about 2 years ago in Cumulocity IoT Platform Services / Data in Motion 0 Planning / planned

IoT Broker / Accept generic MQTT payload / Inbound translation

Extend Cumulocity IoT to be able to integrate any MQTT device independendly of its message format. Currently it is not possible to integrate an MQTT enabled device which sends payloads differntly from what Cumulocity expects or expects downstream ...
Guest almost 5 years ago in Cumulocity IoT Platform Services / Data in Motion 6 Planning / planned

Notifications 2.0 - Add the ability to filter on Managed Object fragments

Enhance the Notifications 2.0 subscription filter to enable filtering on managed object fragments such as device type and to use wild cards in filters, such as “c8y_temp*”, to match everything starting with “c8y_temp”.
Iain Mackenzie 9 months ago in Cumulocity IoT Platform Services / Data in Motion 1 Future consideration

Manage Notification 2.0 API consumers

If the Cumulocity platform is used for a Data as a Service platform used for an integration in a 3rd-party application, we should be able to monitor and manage the consumers using the Notification 2.0 API. Dead or unused subscriptions seem to bloc...
Frank Bauer about 1 year ago in Cumulocity IoT Platform Services / Data in Motion 2 Likely to support/improve

Notification 2.0 API - Send notifications for group deletions

With a subscription to the API "managedobjects" on the context "tenant", notifications are sent whenever a group is created in Cumulocity IoT. Nevertheless, no notification is sent when a group is deleted. As no notification is sent either with a ...
Frédéric Joulin almost 2 years ago in Cumulocity IoT Platform Services / Data in Motion 0 Likely to support/improve

Enable Response/Error Mapping in Smart Rest via MQTT

On behalf of TT-Control, I'd like to create the below feature request: # Feature Request - Enable Request/Response Mapping in Smart Rest via MQTT ## Requirement TT-Control implemented an Agent in Smart Rest 1 via Mqtt a while ago. They have the re...
Guest over 3 years ago in Cumulocity IoT Platform Services / Data in Motion 0 Future consideration

Data Broker Back-channel

The data broker is forwarding objects such as Alarms from one tenant to another. However, there is no mechanism to sync data back to the source tenant. One example is an alarm that is cleared in the target tenant will still be active in the source...
Guest about 5 years ago in Cumulocity IoT Platform Services / Data in Motion 1 Future consideration

Add Tenant Context Support to the Notifications 2.0 API

Itron is using the C8Y Notifications API for LwM2M messaging integrations to upstream systems. Currently, only API Version 1 is available with C8Y Operations message type support (needed for LwM2M messages), but it is limited to 50 transactions pe...
Iain Mackenzie 9 months ago in Cumulocity IoT Platform Services / Data in Motion 2 Likely to support/improve

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

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