<?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[M5Stamp Pico API key too short]]></title><description><![CDATA[<p dir="auto">The docs suggest that the WiFi AP name doubles as your API key.  But it's only 8 characters, UIFlow wants 12 characters:</p>
<p dir="auto"><img src="/assets/uploads/files/1673455920299-tooshort_apikey_2.png" alt="0_1673455917788_tooshort_apikey_2.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">I don't have the little USB adapter so was hoping to just fiddle around in UIflow to get started.  Anyone know the secret to finding the API key on these?  Did something change about the way it is configured?</p>
]]></description><link>https://community.m5stack.com/topic/4971/m5stamp-pico-api-key-too-short</link><generator>RSS for Node</generator><lastBuildDate>Wed, 29 Apr 2026 01:47:39 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/4971.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 11 Jan 2023 16:53:41 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to M5Stamp Pico API key too short on Fri, 13 Jan 2023 18:13:59 GMT]]></title><description><![CDATA[<p dir="auto">For future viewers of this thread, the API key is the same as the MAC address.  You can usually find this on your router config where it shows device info.  The MAC is also shown in the serial output when you connect a burner device (or FTDI cable as mentioned above.</p>
<p dir="auto">My problem was the device was stuck and needed reflashing. Once I did that it worked perfectly using the 12-digit MAC as the API key.</p>
<p dir="auto">You may safely ignore the 8 digit "API Key" that is shown in M5burner or the command line, this was a red herring.</p>
]]></description><link>https://community.m5stack.com/post/19865</link><guid isPermaLink="true">https://community.m5stack.com/post/19865</guid><dc:creator><![CDATA[greenleaf]]></dc:creator><pubDate>Fri, 13 Jan 2023 18:13:59 GMT</pubDate></item><item><title><![CDATA[Reply to M5Stamp Pico API key too short on Fri, 13 Jan 2023 18:00:18 GMT]]></title><description><![CDATA[<p dir="auto">Hello <a class="plugin-mentions-user plugin-mentions-a" href="/user/greenleaf" aria-label="Profile: greenleaf">@<bdi>greenleaf</bdi></a></p>
<p dir="auto">glad to hear it worked.</p>
<p dir="auto">Thanks<br />
Felix</p>
]]></description><link>https://community.m5stack.com/post/19864</link><guid isPermaLink="true">https://community.m5stack.com/post/19864</guid><dc:creator><![CDATA[felmue]]></dc:creator><pubDate>Fri, 13 Jan 2023 18:00:18 GMT</pubDate></item><item><title><![CDATA[Reply to M5Stamp Pico API key too short on Fri, 13 Jan 2023 16:51:03 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> you are a god.  I didn't want to order a $15 burning tool for my $5 m5stamp so I've been using a cheapo FTDI adapter.  Connecting GPIO0 to GND worked like a charm.</p>
]]></description><link>https://community.m5stack.com/post/19863</link><guid isPermaLink="true">https://community.m5stack.com/post/19863</guid><dc:creator><![CDATA[greenleaf]]></dc:creator><pubDate>Fri, 13 Jan 2023 16:51:03 GMT</pubDate></item><item><title><![CDATA[Reply to M5Stamp Pico API key too short on Fri, 13 Jan 2023 03:32:25 GMT]]></title><description><![CDATA[<p dir="auto">Hello <a class="plugin-mentions-user plugin-mentions-a" href="/user/greenleaf" aria-label="Profile: greenleaf">@<bdi>greenleaf</bdi></a></p>
<p dir="auto">from the M5Stamp Pico <a href="https://docs.m5stack.com/en/core/stamp_pico" target="_blank" rel="noopener noreferrer nofollow ugc">documentation</a>, section Program Download.</p>
<p dir="auto"><em>STAMP-PICO adopts the most streamlined circuit design, so it does <strong>not</strong> include the program download circuit, users can download the program through the USB-TTL burner.</em></p>
<p dir="auto">If you don't have the USB-TTL burner board, in order to use M5Burner or esptool, you'll need to put the M5Stamp Pico into download mode manually by connecting a wire from GPIO0 to GND before powering it up. (For regular boot, the wire needs to be removed again.)</p>
<p dir="auto">Thanks<br />
Felix</p>
]]></description><link>https://community.m5stack.com/post/19858</link><guid isPermaLink="true">https://community.m5stack.com/post/19858</guid><dc:creator><![CDATA[felmue]]></dc:creator><pubDate>Fri, 13 Jan 2023 03:32:25 GMT</pubDate></item><item><title><![CDATA[Reply to M5Stamp Pico API key too short on Thu, 12 Jan 2023 21:21:02 GMT]]></title><description><![CDATA[<p dir="auto">When I boot in UIFlow mode this is how the serial output looks.  But M5burner and esptool won't work at all...</p>
<p dir="auto"><img src="/assets/uploads/files/1673558457443-uiflow_m5stamp.png" alt="0_1673558455172_uiflow_m5stamp.png" class=" img-fluid img-markdown" /></p>
]]></description><link>https://community.m5stack.com/post/19853</link><guid isPermaLink="true">https://community.m5stack.com/post/19853</guid><dc:creator><![CDATA[greenleaf]]></dc:creator><pubDate>Thu, 12 Jan 2023 21:21:02 GMT</pubDate></item><item><title><![CDATA[Reply to M5Stamp Pico API key too short on Thu, 12 Jan 2023 20:42:55 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/ajb2k3" aria-label="Profile: ajb2k3">@<bdi>ajb2k3</bdi></a></p>
<p dir="auto">I hooked up a FTDI adapter and am seeing these errors in the serial output.  Did I get a bad board?</p>
<pre><code>14:41:58.735 -&gt; Start factory test
14:41:58.735 -&gt; Start IO TEST
14:41:59.066 -&gt; 18 &gt;&gt;&gt;&gt; 1
14:41:59.111 -&gt; error HIGH--&gt;&gt;&gt;OUT:26  IN:18
14:41:59.738 -&gt; 18 &gt;&gt;&gt;&gt; 0
14:41:59.770 -&gt; 21 &gt;&gt;&gt;&gt; 0
14:41:59.815 -&gt; error HIGH--&gt;&gt;&gt;OUT:19  IN:21
14:42:00.434 -&gt; 18 &gt;&gt;&gt;&gt; 0
14:42:00.473 -&gt; 21 &gt;&gt;&gt;&gt; 0
</code></pre>
]]></description><link>https://community.m5stack.com/post/19849</link><guid isPermaLink="true">https://community.m5stack.com/post/19849</guid><dc:creator><![CDATA[greenleaf]]></dc:creator><pubDate>Thu, 12 Jan 2023 20:42:55 GMT</pubDate></item><item><title><![CDATA[Reply to M5Stamp Pico API key too short on Thu, 12 Jan 2023 09:50:33 GMT]]></title><description><![CDATA[<p dir="auto">The 12 digit api code was on a label stuck to the front of the stamp Pico. If you have reset or updated you need to go into M5Burner and load the configuration data from the stamp to get the new API code</p>
]]></description><link>https://community.m5stack.com/post/19840</link><guid isPermaLink="true">https://community.m5stack.com/post/19840</guid><dc:creator><![CDATA[ajb2k3]]></dc:creator><pubDate>Thu, 12 Jan 2023 09:50:33 GMT</pubDate></item><item><title><![CDATA[Reply to M5Stamp Pico API key too short on Wed, 11 Jan 2023 17:17:50 GMT]]></title><description><![CDATA[<p dir="auto">I also noticed every other device in UIFlow uses an 8 character API Key (MAC).  The m5stamp is the only one that requires 12.  Could this be a bug or unfinished configuration in the app?</p>
<p dir="auto">As a last resort I tried the actual real MAC address of the device that I got from my router.  That failed too, although I can see the device is definitely on the local network.</p>
]]></description><link>https://community.m5stack.com/post/19827</link><guid isPermaLink="true">https://community.m5stack.com/post/19827</guid><dc:creator><![CDATA[greenleaf]]></dc:creator><pubDate>Wed, 11 Jan 2023 17:17:50 GMT</pubDate></item></channel></rss>