<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[SIM7600 and ThingSpeak, unable to publish]]></title><description><![CDATA[<p dir="auto">Dear all,<br />
I nearly got SIM7600, MQTT and Thingspeak working. But I am not able to get the public working.<br />
This is my basic syntax:<br />
The module returns OK status, so so far so good. But no data shows up in my channel.<br />
The weird things is I use the same Topic and message structure as with my SIM7080 module, and that works. Any suggestions?</p>
<p dir="auto">My last part of the code :</p>
<p dir="auto">String payload="channels/"+ String(ChannelId)+"/publish";<br />
int Payload_Length;<br />
Payload_Length=payload.length();</p>
<p dir="auto">SerialAT.println("AT+CMQTTTOPIC=0,"+String(Payload_Length)); // Input the publish message topic &lt;client_index,req_length&gt;<br />
SerialAT.println(payload);<br />
Read_Response_Ignore_OK(3000);</p>
<p dir="auto">payload="field1=345&amp;field2=543";<br />
Serial.print("  ");<br />
Payload_Length=payload.length();<br />
Serial.println  ("AT+CMQTTPAYLOAD=0,"+String(Payload_Length));<br />
SerialAT.println("AT+CMQTTPAYLOAD=0,"+String(Payload_Length)); // input the publish message body &lt;client_index,req_length&gt;<br />
SerialAT.println(payload);<br />
//delay(50);<br />
Read_Response_Ignore_OK(1000);</p>
<p dir="auto">SerialAT.println("AT+CMQTTPUB=0,0,60,0,0"); // Publish a message to the server &lt;client_id,qos,pub_timeout,retained&gt;<br />
Read_Response_Ignore_OK(1000);</p>
]]></description><link>https://community.m5stack.com/topic/5713/sim7600-and-thingspeak-unable-to-publish</link><generator>RSS for Node</generator><lastBuildDate>Mon, 11 May 2026 02:07:57 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/5713.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 16 Oct 2023 12:55:00 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to SIM7600 and ThingSpeak, unable to publish on Sun, 22 Oct 2023 12:50:59 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/felmue" aria-label="Profile: felmue">@<bdi>felmue</bdi></a> And indeed, I needed to add a delay before sending the payload. I had hoped that it would be necessary (in order to speed up he process of waking up, sending and going to sleep).<br />
Regards</p>
]]></description><link>https://community.m5stack.com/post/22548</link><guid isPermaLink="true">https://community.m5stack.com/post/22548</guid><dc:creator><![CDATA[HappyUser]]></dc:creator><pubDate>Sun, 22 Oct 2023 12:50:59 GMT</pubDate></item><item><title><![CDATA[Reply to SIM7600 and ThingSpeak, unable to publish on Fri, 20 Oct 2023 18:22:52 GMT]]></title><description><![CDATA[<p dir="auto">Hello <a class="plugin-mentions-user plugin-mentions-a" href="/user/happyuser" aria-label="Profile: HappyUser">@<bdi>HappyUser</bdi></a></p>
<p dir="auto">according to the documentation, after sending the <code>AT+CMQTTTOPIC=0,&lt;length&gt;</code> command the modem answers with a prompt <code>&gt;</code> after which the topic can be sent. However your code seems to sent the topic right after issuing the command. Maybe try adding a short delay?</p>
<p dir="auto">Same for the payload - try with a short delay before sending the payload.</p>
<p dir="auto">If that solves the issue then of course the proper solution would be to actually wait for the prompt (or error) with a timeout.</p>
<p dir="auto">Thanks<br />
Felix</p>
]]></description><link>https://community.m5stack.com/post/22523</link><guid isPermaLink="true">https://community.m5stack.com/post/22523</guid><dc:creator><![CDATA[felmue]]></dc:creator><pubDate>Fri, 20 Oct 2023 18:22:52 GMT</pubDate></item></channel></rss>