# Device Integration using MQTT Protocol **URL:** \ **Category:** Forum\ **Tags:** cumulocity, device-connectivity\ **Created:** [July 18, 2024, 4:21pm UTC](https://community.cumulocity.com/t/device-integration-using-mqtt-protocol/3889 "2024-07-18T16:21:31Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![punam90singh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/punam90singh/32/29909_2.png) [@punam90singh](https://community.cumulocity.com/u/punam90singh)\ **Post date:** [July 18, 2024, 4:21pm UTC](https://community.cumulocity.com/t/device-integration-using-mqtt-protocol/3889/1 "2024-07-18T16:21:31Z")
#### _ **Product/components** used and **version/fix** level:_ #### _Detailed explanation of the problem:_ I am exploring device integration to Cumulocity using MQTT protocol. Cumulocity IoT uses specific topics for different types of messages. Here are some common topics like: Device Registration\*\*: `s/us` and Device Measurements\*\*: `s/us`. 1. Is it possible to get data on a custom MQTT topic in Cumulocity? 2. Can data received on custom/predefined MQTT topic in Cumulocity be sent to a queue or streaming pipeline for further processing before storing it to Cumulocity DB? #### _Error messages / **full error** message screenshot / **log** file:_ #### _Question related to a **free trial** , or to a **production (customer)** instance?_ ---
**Author:** ![Stefan\_Witschel](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/stefan_witschel/32/31955_2.png) [@Stefan\_Witschel](https://community.cumulocity.com/u/Stefan_Witschel)\ **Post date:** [July 18, 2024, 6:47pm UTC](https://community.cumulocity.com/t/device-integration-using-mqtt-protocol/3889/2 "2024-07-18T18:47:56Z")
Hi @punam90singh for that purpose there is the MQTT Service currently in private preview. If you are interested in a preview you should approach your Sales/Partner contact. You can send any topic & payload to that service and use a microservice to do the processing to Cumulocity or use the [Dynamic Mapper](https://github.com/Cumulocity-IoT/cumulocity-dynamic-mapper) to do that in a zero-code approach. > [@Dynamic Mapper - Map (MQTT) device data in a zero-code approach!](https://community.cumulocity.com/t/dynamic-mapper-map-mqtt-device-data-in-a-zero-code-approach/3043): > > Introduction Since years Cumulocity IoT is providing a MQTT endpoint dedicated to the Cumulocity Domain Model to connect MQTT devices. But what about devices using a pre-defined topic structure and any custom payload which cannot be modified because they are so called “closed”? Since the latest release of Cumulocity there is a new Service in private-preview - the MQTT Service - which is a full-fledged MQTT Broker without the limitation of pre-defined topic structure and payload. Still, it does… ---
**Author:** ![punam90singh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/punam90singh/32/29909_2.png) [@punam90singh](https://community.cumulocity.com/u/punam90singh)\ **Post date:** [July 19, 2024, 7:39am UTC](https://community.cumulocity.com/t/device-integration-using-mqtt-protocol/3889/3 "2024-07-19T07:39:31Z")
Thanks you Stefan for the information! I have couple of questions in this regard. 1. Any tentative timeline by when MQTT Service feature will be available for all, so that we can consider this in designing solution? 2. When we received data on Cumulocity predefined topics , it will go directly to Cumulocity persistent DB or we need to expose some microservice to process and store it to Cumulocity? ---
**Author:** ![Stefan\_Witschel](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/stefan_witschel/32/31955_2.png) [@Stefan\_Witschel](https://community.cumulocity.com/u/Stefan_Witschel)\ **Post date:** [July 19, 2024, 9:07am UTC](https://community.cumulocity.com/t/device-integration-using-mqtt-protocol/3889/4 "2024-07-19T09:07:56Z")
I think it will be available later this year. I don’t know the detailed roadmap of MQTT Service but maybe @Jane_Porter or @Scott_Mitchell1 can tell you more. To 2: If you use SmartREST all the messages are going directly to Cumulocity. Based on the topic you can decide if it should be persisted or just displayed in UI or used in Streaming Analytics. `s/us` means all of it for example. So no additional microservice needed. ---
**Author:** ![Scott\_Mitchell1](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/scott_mitchell1/32/19493_2.png) [@Scott\_Mitchell1](https://community.cumulocity.com/u/Scott_Mitchell1)\ **Post date:** [July 19, 2024, 10:04am UTC](https://community.cumulocity.com/t/device-integration-using-mqtt-protocol/3889/5 "2024-07-19T10:04:04Z")
Hi @punam90singh, The MQTT Service is currently in Private Preview (limited customer trial) status, where we are collecting feedback from customers to understand how the service needs to evolve before it can move to GA status. There is no committed timeline but we’re aiming for a GA date in early 2025. As Stefan says, if you wanted to join the preview, we can discuss that through your sales/partner representative. Many thanks, Scott ---
**Author:** ![system](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/system/32/31990_2.png) [@system](https://community.cumulocity.com/u/system)\ **Post date:** [December 29, 2024, 1:23pm UTC](https://community.cumulocity.com/t/device-integration-using-mqtt-protocol/3889/6 "2024-12-29T13:23:59Z")
---
**Author:** ![system](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/system/32/31990_2.png) [@system](https://community.cumulocity.com/u/system)\ **Post date:** [June 27, 2025, 1:24pm UTC](https://community.cumulocity.com/t/device-integration-using-mqtt-protocol/3889/7 "2025-06-27T13:24:32Z")
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.