Skip to Main Content
Cumulocity IoT - Tell us your Idea
ADD A NEW IDEA

FILTER BY CATEGORY

Data in Motion

Showing 4 of 272

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 over 3 years ago in Cumulocity IoT Platform Services / Data in Motion 6 Planning / planned

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 about 2 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 over 3 years ago in Cumulocity IoT Platform Services / Data in Motion 1 Future consideration

Serve custom certificate on MQTT port 8883 when using custom domain

Currently when using a custom domain name the UI/REST AP is accessible by this custom domain name. But the data ingestion by MQTT does not work using the same custom domain name because the certificate validation will fail on client side, because ...
Florian Huber over 1 year ago in Cumulocity IoT Platform Services / Data in Motion 1 Future consideration