<?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>Azure IOT hub large Cloud 2 Device message</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/117213/azure-iot-hub-large-cloud-2-device-message</link><description>Hello, 
 
 At the moment I have a correctly working Azure IOT hub connection. 
 DPS works, device twin configurations works and transmitting data to the hub is also no problem. 
 We can also receive cloud 2 device (C2D) messages from the IOT hub. 
 Now</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 12 Dec 2024 13:04:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/117213/azure-iot-hub-large-cloud-2-device-message" /><item><title>RE: Azure IOT hub large Cloud 2 Device message</title><link>https://devzone.nordicsemi.com/thread/514746?ContentTypeID=1</link><pubDate>Thu, 12 Dec 2024 13:04:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5aff7140-0531-4afa-ab4f-64ac161b741e</guid><dc:creator>Charlie</dc:creator><description>&lt;p&gt;&lt;span&gt;Hi René,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;No problem, let me kown if you need more help!&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Charlie&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Azure IOT hub large Cloud 2 Device message</title><link>https://devzone.nordicsemi.com/thread/514728?ContentTypeID=1</link><pubDate>Thu, 12 Dec 2024 12:23:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0974027a-1d7d-422e-a193-c249a31202d1</guid><dc:creator>rene_pvh</dc:creator><description>&lt;p&gt;Hi Charlie,&lt;/p&gt;
&lt;p&gt;Thank you for the quick response.&amp;nbsp;&lt;br /&gt;We will&amp;nbsp;try the posts you suggested.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Ren&amp;eacute;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Azure IOT hub large Cloud 2 Device message</title><link>https://devzone.nordicsemi.com/thread/514717?ContentTypeID=1</link><pubDate>Thu, 12 Dec 2024 11:43:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2952f768-1582-43cc-87f4-9721236a7233</guid><dc:creator>Charlie</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you for reaching out to us.&lt;/p&gt;
&lt;p&gt;The nRF9160 modem has a hardware resource constraint, as mentioned in the &lt;a href="https://nsscprodmedia.blob.core.windows.net/prod/software-and-other-downloads/dev-kits/nrf9160-dk/release_notes_modemfirmware/mfw_nrf9160_1.3.7_release_notes.txt" target="_new"&gt;&lt;span&gt;Modem&lt;/span&gt;&lt;span&gt; Firmware&lt;/span&gt;&lt;span&gt; 1.3.7&lt;/span&gt;&lt;span&gt; release&lt;/span&gt;&lt;span&gt; notes&lt;/span&gt;&lt;/a&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;2kB secure socket buffer size.&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;One potential solution is to use MbedTLS in the application core, as discussed here: &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/96779/nrf9160-mqtt-message-payload-over-2302-bytes-results-in-socket-error-pollerr-and-dropped-connection/410691"&gt;RE: nRF9160 MQTT message payload over 2302 bytes results in Socket error: POLLERR and dropped connection&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;A better approach would be to split the message payload on the MQTT broker server side. This is supported by &lt;a href="https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-mqtt-support" target="_new"&gt;&lt;span&gt;Azure&lt;/span&gt;&lt;span&gt; IoT&lt;/span&gt;&lt;span&gt; Hub&lt;/span&gt;&lt;span&gt; MQTT&lt;/span&gt;&lt;span&gt; 5&lt;/span&gt;&lt;span&gt; support&lt;/span&gt;&lt;/a&gt;&amp;nbsp;by setting&amp;nbsp;&lt;span&gt;Maximum Packet Size. U&lt;/span&gt;nfortunately, the Zephyr MQTT client does not currently support MQTT 5. You can find more details here: &lt;a href="https://github.com/zephyrproject-rtos/zephyr/issues/21633" target="_new"&gt;&lt;span&gt;Support&lt;/span&gt;&lt;span&gt; for&lt;/span&gt;&lt;span&gt; MQTT&lt;/span&gt;&lt;span&gt; 5&lt;/span&gt;&lt;span&gt; · Issue&lt;/span&gt;&lt;span&gt; #21633&lt;/span&gt;&lt;span&gt; · zephyrproject&lt;/span&gt;&lt;span&gt;-rtos&lt;/span&gt;&lt;span&gt;/zephyr&lt;/span&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If this feature is critical for your project, we recommend sharing your request on the feature request page. This could be a viable solution once Zephyr MQTT 5 support becomes available.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Charlie&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>