<?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>Modify ASSET TRACKER</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/69805/modify-asset-tracker</link><description>Hello, 
 I&amp;#39;m trying to modify the current ASSET_TRACKER of SDK v1.4.1 to get it to work in my own server on AWS-IoT. 
 I&amp;#39;m wondering if there is any documentation about this app and if not I have a problem with finding the definition of the MQTT topics</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 04 Jan 2021 06:23:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/69805/modify-asset-tracker" /><item><title>RE: Modify ASSET TRACKER</title><link>https://devzone.nordicsemi.com/thread/287121?ContentTypeID=1</link><pubDate>Mon, 04 Jan 2021 06:23:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5a1560c6-8dbe-4660-88c1-b9d90b3dcd63</guid><dc:creator>Marte Myrvold</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Great to hear that you got it to work!&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Marte&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Modify ASSET TRACKER</title><link>https://devzone.nordicsemi.com/thread/287072?ContentTypeID=1</link><pubDate>Fri, 01 Jan 2021 12:14:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:424dd435-4734-49b1-b81c-b6a6c5ce03b9</guid><dc:creator>Mustafa</dc:creator><description>&lt;p&gt;Hallo Marte, Thank you for your reply. I could finally get it working successfully. The problem was that Asset_tracker expects a message from the server when the connection is established with the cloud and that message contains the topic_id where asset_tracker has to publish. I could modify this one and get it working with my own configuration.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The reason I use Asset_tracker because it has almost the same features that are required in my application.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Modify ASSET TRACKER</title><link>https://devzone.nordicsemi.com/thread/286644?ContentTypeID=1</link><pubDate>Mon, 28 Dec 2020 07:57:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:835d9d49-29da-4bdb-888a-c1a5f5046cbe</guid><dc:creator>Marte Myrvold</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Could you try testing with the&amp;nbsp;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.4.1/nrf/samples/nrf9160/mqtt_simple/README.html"&gt;Simple MQTT sample&lt;/a&gt;&amp;nbsp;and connect with the AWS test server to see if that works? The Asset Tracker isn&amp;#39;t meant for reuse in this way, so it might be simpler to combine some of the&amp;nbsp;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.4.1/nrf/samples.html"&gt;samples&lt;/a&gt;&amp;nbsp;in NCS to do what you want, instead of changing one of the&amp;nbsp;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.4.1/nrf/applications.html"&gt;applications&lt;/a&gt;, which are designed for a specific use case.&lt;/p&gt;
&lt;p&gt;Could you also give a full log output from when you connect?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Marte&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Modify ASSET TRACKER</title><link>https://devzone.nordicsemi.com/thread/286484?ContentTypeID=1</link><pubDate>Wed, 23 Dec 2020 14:16:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4c16ea0a-a218-49c9-a7ef-fa3e62b77e29</guid><dc:creator>Marte Myrvold</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I&amp;#39;m not sure why it gives error when you try to publish with id to another topic, but I&amp;#39;ll look more into your case and come back to you.&lt;/p&gt;
&lt;p&gt;Please be aware that we have reduced staffing due to holiday season, so response time might be longer than normal. In addition to this, most of our nRF9160 experts are on holiday, but some will be back next week.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Marte&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Modify ASSET TRACKER</title><link>https://devzone.nordicsemi.com/thread/286433?ContentTypeID=1</link><pubDate>Wed, 23 Dec 2020 11:23:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dc20a50f-62a8-40fb-8fa3-93276850ab3e</guid><dc:creator>Mustafa</dc:creator><description>&lt;p&gt;Thanks Vkadal for your answer. Actually, my question was more about modifying the asset_tracker to get it to work on my own server ( also on AWS IOT ). until now I get successfully connection with my server and I could get messages on my shadow device topics. but when the device tries to publish a message-id ( RSRP ) to a modified topic which I modified instead of the old topic of nrf-cloud, I get then &lt;strong&gt;NRF_CLOUD_EVT_TRANSPORT_DISCONNECTED&lt;/strong&gt; event. this error I get only when I try to publish the message with id (RSRP ) to another topic for example ( test/node ).&lt;/p&gt;
&lt;p&gt;Any idea what the problem is,&lt;/p&gt;
&lt;p&gt;Thanks in advance!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Modify ASSET TRACKER</title><link>https://devzone.nordicsemi.com/thread/286338?ContentTypeID=1</link><pubDate>Tue, 22 Dec 2020 15:15:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:870309c3-18ba-45ca-8fa6-ea7adf1af8af</guid><dc:creator>vkadal</dc:creator><description>&lt;p&gt;Most probably, take a bare machine in those cloud services, and install required server components. Then it may be easy&amp;nbsp; to integrate nRF-9160 to cloud. But integrating with one of their IoT services may be a challenge&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>