<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>receive MQTT signals directly from AWS on thread end device</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/96528/receive-mqtt-signals-directly-from-aws-on-thread-end-device</link><description>Hello, 
 
 I am working on a thread based project for a class and I was wondering if it was possible to receive an MQTT packet directly from AWS through the border router? Or is it required to use MQTT-SN with a MQTT broker on the border router. If the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 10 Feb 2023 12:19:25 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/96528/receive-mqtt-signals-directly-from-aws-on-thread-end-device" /><item><title>RE: receive MQTT signals directly from AWS on thread end device</title><link>https://devzone.nordicsemi.com/thread/409341?ContentTypeID=1</link><pubDate>Fri, 10 Feb 2023 12:19:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f554a32e-f8d2-4cc2-bf7c-b7046b0a13f1</guid><dc:creator>Elfving</dc:creator><description>&lt;p&gt;Hello Liam,&lt;/p&gt;
&lt;p&gt;Are you using nRF 5 SDK or NCS. If you are using nRF 5, &lt;a href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/nrf-connect-sdk-and-nrf5-sdk-statement"&gt;I would recommend you to switch&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Given that you are using NCS, I would not use MQTT-SN. It is difficult. Use MQTT instead.&lt;/p&gt;
[quote user=""]possible to receive an MQTT packet directly from AWS through the border router?[/quote]
&lt;p&gt;This might require the Thread device to have a public IP, but you could get around that. For MQTT, the Thread device will subscribe to a MQTT Broker. And since the device have subscribed &amp;quot;via a TCP connection&amp;quot;, the Broker likely do not need to know the address of the Thread Device.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Elfving&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>