# MQTT with 3rd party broker **URL:** \ **Category:** 3rd Party Modules\ **Created:** [September 26, 2018, 11:20am UTC](https://forum.inductiveautomation.com/t/mqtt-with-3rd-party-broker/19831 "2018-09-26T11:20:46Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![jean.noel.dotter](https://avatars.discourse-cdn.com/v4/letter/j/c68b51/32.png) [@jean.noel.dotter](https://forum.inductiveautomation.com/u/jean.noel.dotter)\ **Post date:** [September 26, 2018, 11:20am UTC](https://forum.inductiveautomation.com/t/mqtt-with-3rd-party-broker/19831/1 "2018-09-26T11:20:46Z")
Dear All, We are starting with Inductive Edge and MQTT. If we use the provided Broker the example is working fine, But if we use our Broker the data are published but are not displayed under the “MQTT Engine” three view Under “Edge Nodes+Tutorial Device+…” Any idea which is mandatory to see the “discovery” feature at work? Thanks, ---
**Author:** ![AlThePal](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/althepal/32/3603_2.png) [@AlThePal](https://forum.inductiveautomation.com/u/AlThePal)\ **Post date:** [October 1, 2018, 3:19pm UTC](https://forum.inductiveautomation.com/t/mqtt-with-3rd-party-broker/19831/2 "2018-10-01T15:19:44Z")
You will have to use a Broker designed to work with Ignition. As far as I know Cirrus Link’s Broker is the only one. ---
**Author:** ![Kyle\_Chase](https://avatars.discourse-cdn.com/v4/letter/k/9de0a6/32.png) [@Kyle\_Chase](https://forum.inductiveautomation.com/u/Kyle_Chase)\ **Post date:** [October 1, 2018, 4:17pm UTC](https://forum.inductiveautomation.com/t/mqtt-with-3rd-party-broker/19831/3 "2018-10-01T16:17:08Z")
This is not correct. There is no such thing as a “Broker designed to work with Ignition.” Check your connection logs, it is probably a permission issue. ---
**Author:** ![ryanjmclaughlin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryanjmclaughlin/32/4318_2.png) [@ryanjmclaughlin](https://forum.inductiveautomation.com/u/ryanjmclaughlin)\ **Post date:** [October 1, 2018, 4:41pm UTC](https://forum.inductiveautomation.com/t/mqtt-with-3rd-party-broker/19831/4 "2018-10-01T16:41:50Z")
You can certainly use your own broker. Check out [https://docs.chariot.io/display/CLD/ME%3A+Configuration](https://docs.chariot.io/display/CLD/ME%3A+Configuration) for config details. If your topics do not conform to Sparkplug, you may need to setup some custom namespaces to ensure things populate for your topics (also in the docs above). ---
**Author:** ![AlThePal](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/althepal/32/3603_2.png) [@AlThePal](https://forum.inductiveautomation.com/u/AlThePal)\ **Post date:** [October 1, 2018, 4:46pm UTC](https://forum.inductiveautomation.com/t/mqtt-with-3rd-party-broker/19831/5 "2018-10-01T16:46:02Z")
My bad, I always find the Cirrus Link modules confusing. It is the Cirrus Link Engine module which has the ability to auto-create Ignition tags, as far as I know this should work with any broker (theirs is called the Distributor module). ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [October 1, 2018, 4:53pm UTC](https://forum.inductiveautomation.com/t/mqtt-with-3rd-party-broker/19831/6 "2018-10-01T16:53:26Z")
Any broker should work (I think there’s some minimum QoS it needs to support). The auto-creation of tags by the Engine module is possible when the data pushed to the broker is conforming to the Sparkplug protocol. edit: oops, @ryanjmclaughlin already basically said this. ---
**Author:** ![JoeJansen](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/joejansen/32/5277_2.png) [@JoeJansen](https://forum.inductiveautomation.com/u/JoeJansen)\ **Post date:** [October 1, 2018, 7:57pm UTC](https://forum.inductiveautomation.com/t/mqtt-with-3rd-party-broker/19831/7 "2018-10-01T19:57:35Z")
I tested it using Mosquitto. I ended up having to append’/json’ to the incoming namespace subscription and then set JSON payload to TRUE. My data source was the ‘Generic MQTT’ on a Red Lion Graphite HMI using Crimson 3.1 I set the Publication Topic to G07Pub on the HMI. In Ignition MQTT Engine, I created a custom Namespace. Subscrtiptions was ‘G07Pub/json’, root Tag Folder was TagData, and JSON Payload was checked true. The MQTT Engine did auto-create the tags for me as expected. –j-- ---
**Author:** ![jean.noel.dotter](https://avatars.discourse-cdn.com/v4/letter/j/c68b51/32.png) [@jean.noel.dotter](https://forum.inductiveautomation.com/u/jean.noel.dotter)\ **Post date:** [October 2, 2018, 6:42am UTC](https://forum.inductiveautomation.com/t/mqtt-with-3rd-party-broker/19831/8 "2018-10-02T06:42:31Z")
Hello Kyle\_Chase, After some playing, the system is runing as expected now, this topic is closed. But by the way, where can we check the connection logs? Thanks, ---
**Author:** ![Kyle\_Chase](https://avatars.discourse-cdn.com/v4/letter/k/9de0a6/32.png) [@Kyle\_Chase](https://forum.inductiveautomation.com/u/Kyle_Chase)\ **Post date:** [October 2, 2018, 2:00pm UTC](https://forum.inductiveautomation.com/t/mqtt-with-3rd-party-broker/19831/9 "2018-10-02T14:00:23Z")
It all depends on what broker you are using. Mosquitto outputs it’s logs to /var/log/mosquitto.log I think.