# Anyone have The Things Network (MQTT) working with Ignition? **URL:** \ **Category:** Ignition\ **Created:** [July 15, 2019, 11:44pm UTC](https://forum.inductiveautomation.com/t/anyone-have-the-things-network-mqtt-working-with-ignition/26566 "2019-07-15T23:44:26Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![filipg](https://avatars.discourse-cdn.com/v4/letter/f/a88e4f/32.png) [@filipg](https://forum.inductiveautomation.com/u/filipg)\ **Post date:** [July 15, 2019, 11:44pm UTC](https://forum.inductiveautomation.com/t/anyone-have-the-things-network-mqtt-working-with-ignition/26566/1 "2019-07-15T23:44:27Z")
I have a number of temperature & relative humidity nodes sending data in over MQTT to The Things Network. Thus far, I have been subscribing to these data via NodeRED on a local virtual server. I am now looking on how to best connect this to our ignition gateway. I have tried installing cirrus engine but am not getting anywhere getting module to connect to TTN - it always get “connect with retry failed due to Unable to connect to server” with zero more information in log. I know my ‘username’ and ‘password’ are good as I have been using these in NodeRED for 12+ months. I’m specifying ‘third party’ for server type. I have tried every variation of URL (tcp://bridge.us.thethings.network:1883, tcp://west-us.thethings.network:1883, etc) to no avail. If anyone has this working, please let me know what URL should be. I already use KepwareEx for our AutomationDirect PLC and I see they support MQTT too. I also get a feeling that these forums are biased towards Cirrus (strategic partner and all). Does anyone have KepwareEx working with TTN and was it easy to set up? Thank you. ---
**Author:** ![PRAMANJ](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pramanj/32/66935_2.png) [@PRAMANJ](https://forum.inductiveautomation.com/u/PRAMANJ)\ **Post date:** [July 16, 2019, 12:55am UTC](https://forum.inductiveautomation.com/t/anyone-have-the-things-network-mqtt-working-with-ignition/26566/2 "2019-07-16T00:55:11Z")
Not sure what is TTN (I guess it’s some MQTT related stuff) but [www.pubnub.com](http://www.pubnub.com) allows you to connect remote devices and computers including ignition server over internet easily with latency of max 500 ms across the globe. Don’t know if it’s an answer in right direction. ---
**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\ **Post date:** [July 16, 2019, 12:14pm UTC](https://forum.inductiveautomation.com/t/anyone-have-the-things-network-mqtt-working-with-ignition/26566/3 "2019-07-16T12:14:00Z")
I wrote a tutorial on using NCD sensors with the Cirrus Link modules using MQTT. It may not be what you are looking for, but it may have something that could help you. check it out [here](https://community.ncd.io/t/wireless-mqtt-sensors-from-ncd-for-ignition-scada-tutorial/4250) if you’d like. ---
**Author:** ![filipg](https://avatars.discourse-cdn.com/v4/letter/f/a88e4f/32.png) [@filipg](https://forum.inductiveautomation.com/u/filipg)\ **Post date:** [July 16, 2019, 4:13pm UTC](https://forum.inductiveautomation.com/t/anyone-have-the-things-network-mqtt-working-with-ignition/26566/4 "2019-07-16T16:13:03Z")
Thanks for the link to the MQTT tutorial - half of it is helpful. The Things Network (TTN) is the cloud broker counterpart to Cirrus Link’s Distributor module. I didn’t know about custom namespace for JSON payload - not sure what TTN gateway does. Using [Quick Start Guide](https://www.thethingsnetwork.org/docs/network/cli/quick-start.html), I logged in to my TTN Console account and figured out that my region broker’s address is: us-west.thethings.network:1883 (one less mystery). Alas, still no luck. ---
**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\ **Post date:** [July 16, 2019, 6:07pm UTC](https://forum.inductiveautomation.com/t/anyone-have-the-things-network-mqtt-working-with-ignition/26566/5 "2019-07-16T18:07:40Z")
Well at least I wasn’t totally unhelpful. You should be able to get in touch with Cirrus Link support via email. I contacted them and got some good information quickly from them even without purchasing any of their software, I only had the demo. ---
**Author:** ![filipg](https://avatars.discourse-cdn.com/v4/letter/f/a88e4f/32.png) [@filipg](https://forum.inductiveautomation.com/u/filipg)\ **Post date:** [July 18, 2019, 5:10pm UTC](https://forum.inductiveautomation.com/t/anyone-have-the-things-network-mqtt-working-with-ignition/26566/6 "2019-07-18T17:10:10Z")
Thanks to everyone. I did open ticket with CirrusLink, they responded same day requesting TRACE logs of their client module, and I sent them everything. I used a simple & free windows app called MQTTBox ([http://workswithweb.com/mqttbox.html](http://workswithweb.com/mqttbox.html); it also works fine under Windows 7) to confirm that my credentials were valid, and demonstrate that connecting to my broker & subscribing to namespace yielded real-time data. Good app to show proof that broker is not the problem 🙂 ---
**Author:** ![louagejasper](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/louagejasper/32/86311_2.png) [@louagejasper](https://forum.inductiveautomation.com/u/louagejasper)\ **Post date:** [March 21, 2022, 10:42am UTC](https://forum.inductiveautomation.com/t/anyone-have-the-things-network-mqtt-working-with-ignition/26566/7 "2022-03-21T10:42:25Z")
HI @filipg, did you manage to connect to the TTN? ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [March 21, 2022, 2:05pm UTC](https://forum.inductiveautomation.com/t/anyone-have-the-things-network-mqtt-working-with-ignition/26566/8 "2022-03-21T14:05:28Z")
For connecting to The Things Network (TTN), you’ll need to use a _Custom Namespace_ configuration in MQTT Engine version 4.0.10 or higher (this is important for the _String Conversions_ feature). You should be able to configure the server settings per the TTN guidance [here](https://www.thethingsindustries.com/docs/integrations/mqtt). For the _Custom Namespace_, go to the _String Conversions_ tab (new with MQTT Engine 4.0.10) and set it up like below: ![2022-03-21 at 9.01 AM](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/5/456aabba0009a67499eaf59d2782b5e520ddb3a3.png) This substitutes the `@` sign from the topic definitions so that the hierarchy can be properly represented as Ignition tags (which don’t allow certain characters). This is what I use to pull in LoRaWAN sensor data here at the house that my LoRaWAN gateway is publishing up to TTN. ---
**Author:** ![wes0johnson](https://avatars.discourse-cdn.com/v4/letter/w/7ab992/32.png) [@wes0johnson](https://forum.inductiveautomation.com/u/wes0johnson)\ **Post date:** [March 28, 2022, 3:37pm UTC](https://forum.inductiveautomation.com/t/anyone-have-the-things-network-mqtt-working-with-ignition/26566/9 "2022-03-28T15:37:16Z")
There is a new help document here for TTN: [Do I need to do anything special to connect to my TTN (www.thethingsnetwork.org) broker - MQTT Modules for Ignition 8.x - Confluence](https://docs.chariot.io/display/CLD80/Do+I+need+to+do+anything+special+to+connect+to+my+TTN+%28www.thethingsnetwork.org%29+broker)