<?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>MQTT Not Receiving Subscribe Message for 30+ Seconds</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/118584/mqtt-not-receiving-subscribe-message-for-30-seconds</link><description>My setup: SDK version: 2.5.0.v Modem version: 1.3.0. I am using MQTT to subscribe to a topic, for example, the LED state. The plan is t o set the LED state on the server side and send the new state to the device. I need a relatively fast reaction time</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 13 Feb 2025 09:20:40 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/118584/mqtt-not-receiving-subscribe-message-for-30-seconds" /><item><title>RE: MQTT Not Receiving Subscribe Message for 30+ Seconds</title><link>https://devzone.nordicsemi.com/thread/522798?ContentTypeID=1</link><pubDate>Thu, 13 Feb 2025 09:20:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:06a76472-ad73-47c3-99b7-6c04c0041791</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;From modem team discussion;&lt;/p&gt;
&lt;p&gt;&amp;quot;Both cells customer mentions seem to be usable from L1 point of view (Pagings received in RRC Idle and RRCConnectionReleases received in RRC Connected mode).&amp;quot;&lt;/p&gt;
&lt;p&gt;&amp;quot;Cell PCI 354 is clearly weaker and SNR is worse. This cell is anyway selected always by the cell search/init sync algorithm after RRC Connection. In RRC Idle re-selection algorithm then changes back to better cell PCI 406. This is most likely normal behavior as both cells are good enough.&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;quot;NMEAS sees about identical RSRP and RSRQ for PCIs 354 and 406 - they fluctuate mostly within +-3 dB. In the last quarter of the log PCI 354 has clearly worse RSRP/RSRQ few times. So yes - you would see many reselections between the two.&amp;quot;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;quot;After changing to PCI 406 no pages are received for the device until first mobile originated connection. It seems that network is not sending DL data to correct tower. Or we are missing pages. &amp;quot;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Ok, so UE is camped to better cell when data is not received. UE receives pages for other devices and SNR is &amp;gt;0 so it’s very unlikely that UE would miss pages. So, most probably the reason is like you mentioned: “It seems that network is not sending DL data to correct tower”&lt;/p&gt;
&lt;p&gt;&amp;quot;UE is connected to PCI 354 and after RRC Connection is released, UE changes to PCI 406 so likely NW keeps sending pages for UE only to PCI 354 and not for 406. Sounds like NW configuration problem.&amp;quot;&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;
&lt;div&gt;
&lt;div&gt;
&lt;div&gt;
&lt;div&gt;
&lt;div&gt;
&lt;div&gt;
&lt;p&gt;&amp;quot;According to &lt;a title="http://cellmapper.net" href="http://cellmapper.net"&gt;cellmapper.net&lt;/a&gt; both cells are in the same tower 442 near St. Gertrude&amp;#39;s New Church, Riga. The strange thing is that in the same tower there is cells 354, 355, 356 forming probably 3 different sectors - and in addition - cell 406. Might be a misconfiguration problem on operator side.&amp;quot;&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MQTT Not Receiving Subscribe Message for 30+ Seconds</title><link>https://devzone.nordicsemi.com/thread/522187?ContentTypeID=1</link><pubDate>Mon, 10 Feb 2025 12:43:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b956dadd-8cb4-415f-a65f-e7cd569b59dc</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;Thank you very much.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MQTT Not Receiving Subscribe Message for 30+ Seconds</title><link>https://devzone.nordicsemi.com/thread/521770?ContentTypeID=1</link><pubDate>Thu, 06 Feb 2025 15:10:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a519ddbd-38ff-45ee-a4ec-59ff6323d4f3</guid><dc:creator>Eizens</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/2870.modemtraces_5F00_test1.bin"&gt;devzone.nordicsemi.com/.../2870.modemtraces_5F00_test1.bin&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MQTT Not Receiving Subscribe Message for 30+ Seconds</title><link>https://devzone.nordicsemi.com/thread/521769?ContentTypeID=1</link><pubDate>Thu, 06 Feb 2025 15:10:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cbdc6f46-8aa9-4760-8670-dc6f0e1086dc</guid><dc:creator>Eizens</dc:creator><description>&lt;p&gt;Hello, I added trace .bin file.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MQTT Not Receiving Subscribe Message for 30+ Seconds</title><link>https://devzone.nordicsemi.com/thread/521766?ContentTypeID=1</link><pubDate>Thu, 06 Feb 2025 15:05:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:01f6b804-bc1f-4c7d-a107-1f102cfa067b</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;Modem team will need a modem trace for further investigations.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MQTT Not Receiving Subscribe Message for 30+ Seconds</title><link>https://devzone.nordicsemi.com/thread/521376?ContentTypeID=1</link><pubDate>Tue, 04 Feb 2025 16:12:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:36980737-1483-4235-a55f-be961ce714e6</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
[quote user=""]I found one more interesting thing. The modem is constantly switching between two towers. The SNR of one tower is somewhere between 8 dB (fair) and 10 dB (good), while the other tower&amp;#39;s SNR ranges from -5 dB to 0 dB (poor). When the device missed the message, it was connected to the tower with poor SNR. This could explain why the MQTT message was not received.&amp;nbsp;[/quote]
&lt;p&gt;That seems plausible. I will confirm with the modem team.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>