<?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[Grove HUB unit trouble]]></title><description><![CDATA[<p dir="auto">DHT12 in Environment Sensor unit does not working when it will connected to Grove HUB unit.<br />
BMP280 in the same configuration is working</p>
]]></description><link>https://community.m5stack.com/topic/517/grove-hub-unit-trouble</link><generator>RSS for Node</generator><lastBuildDate>Wed, 29 Apr 2026 06:21:35 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/517.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 18 Jan 2019 17:27:10 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Grove HUB unit trouble on Wed, 30 Jan 2019 08:05:05 GMT]]></title><description><![CDATA[<p dir="auto">I tested a hub device attached to port A with a few 100cm grove cables and I was able to successfully read the i2c address of the ENV sensor and also others. I tested with the i2c_tester arduino program <a href="https://github.com/m5stack/M5Stack/blob/master/examples/Advanced/I2C_Tester/I2C_Tester.ino" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/m5stack/M5Stack/blob/master/examples/Advanced/I2C_Tester/I2C_Tester.ino</a> perhaps its just an isolated incident.<br />
<img src="/assets/uploads/files/1548835372478-wechatimg46-resized.jpg" alt="0_1548835367201_WechatIMG46.jpg" class=" img-fluid img-markdown" /></p>
]]></description><link>https://community.m5stack.com/post/2781</link><guid isPermaLink="true">https://community.m5stack.com/post/2781</guid><dc:creator><![CDATA[lukasmaximus]]></dc:creator><pubDate>Wed, 30 Jan 2019 08:05:05 GMT</pubDate></item><item><title><![CDATA[Reply to Grove HUB unit trouble on Tue, 29 Jan 2019 15:27:27 GMT]]></title><description><![CDATA[<p dir="auto">Also out of scientific curiosity, try wrapping the wires in some foil. It could be that the larger wire need to be shielded or the device may need its own power at that distance</p>
]]></description><link>https://community.m5stack.com/post/2772</link><guid isPermaLink="true">https://community.m5stack.com/post/2772</guid><dc:creator><![CDATA[ajb2k3]]></dc:creator><pubDate>Tue, 29 Jan 2019 15:27:27 GMT</pubDate></item><item><title><![CDATA[Reply to Grove HUB unit trouble on Tue, 29 Jan 2019 09:31:45 GMT]]></title><description><![CDATA[<p dir="auto">Are the wires in the same order as your short cables? we were having QC issues for a while where the manufacturing department put the wires in the wrong order into the grove connector. Would greatly appreciate if you could double check for me.</p>
<p dir="auto">Thanks</p>
]]></description><link>https://community.m5stack.com/post/2768</link><guid isPermaLink="true">https://community.m5stack.com/post/2768</guid><dc:creator><![CDATA[lukasmaximus]]></dc:creator><pubDate>Tue, 29 Jan 2019 09:31:45 GMT</pubDate></item><item><title><![CDATA[Reply to Grove HUB unit trouble on Mon, 28 Jan 2019 11:44:31 GMT]]></title><description><![CDATA[<p dir="auto">Unfortunately, all these wires were bought in the official m5stack store(<br />
Including 50 cm wire</p>
]]></description><link>https://community.m5stack.com/post/2752</link><guid isPermaLink="true">https://community.m5stack.com/post/2752</guid><dc:creator><![CDATA[vvs551]]></dc:creator><pubDate>Mon, 28 Jan 2019 11:44:31 GMT</pubDate></item><item><title><![CDATA[Reply to Grove HUB unit trouble on Thu, 24 Jan 2019 12:31:57 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/vvs551" aria-label="Profile: vvs551">@<bdi>vvs551</bdi></a> said in <a href="/post/2679">Grove HUB unit trouble</a>:</p>
<blockquote>
<p dir="auto">Oh yes!)<br />
I discovered the cause of this problem with ENV unit<br />
It is long cable (50 cm) to HUB unit<br />
When I connected HUB unit with short cable to m5core - all I2C addresses was scanned successfully!<br />
<img src="/assets/uploads/files/1548318186817-f1c52e6a-0154-4c2f-a1f3-feb9900a442a-image.png" alt="0_1548318186295_f1c52e6a-0154-4c2f-a1f3-feb9900a442a-image.png" class=" img-fluid img-markdown" /></p>
</blockquote>
<p dir="auto">Nice discovery</p>
]]></description><link>https://community.m5stack.com/post/2680</link><guid isPermaLink="true">https://community.m5stack.com/post/2680</guid><dc:creator><![CDATA[ajb2k3]]></dc:creator><pubDate>Thu, 24 Jan 2019 12:31:57 GMT</pubDate></item><item><title><![CDATA[Reply to Grove HUB unit trouble on Thu, 24 Jan 2019 08:23:10 GMT]]></title><description><![CDATA[<p dir="auto">Oh yes!)<br />
I discovered the cause of this problem with ENV unit<br />
It is long cable (50 cm) to HUB unit<br />
When I connected HUB unit with short cable to m5core - all I2C addresses was scanned successfully!<br />
<img src="/assets/uploads/files/1548318186817-f1c52e6a-0154-4c2f-a1f3-feb9900a442a-image.png" alt="0_1548318186295_f1c52e6a-0154-4c2f-a1f3-feb9900a442a-image.png" class=" img-fluid img-markdown" /></p>
]]></description><link>https://community.m5stack.com/post/2679</link><guid isPermaLink="true">https://community.m5stack.com/post/2679</guid><dc:creator><![CDATA[vvs551]]></dc:creator><pubDate>Thu, 24 Jan 2019 08:23:10 GMT</pubDate></item><item><title><![CDATA[Reply to Grove HUB unit trouble on Wed, 23 Jan 2019 12:31:08 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/vvs551" aria-label="Profile: vvs551">@<bdi>vvs551</bdi></a> If you wire the ENV module to the GROVE port A (with and without HUB) do you have the charging base connected?<br />
Specifically do you have the M5GO Base (e.g. Fire) or the Core Bottom Base?</p>
]]></description><link>https://community.m5stack.com/post/2660</link><guid isPermaLink="true">https://community.m5stack.com/post/2660</guid><dc:creator><![CDATA[PlayTheGame]]></dc:creator><pubDate>Wed, 23 Jan 2019 12:31:08 GMT</pubDate></item><item><title><![CDATA[Reply to Grove HUB unit trouble on Tue, 22 Jan 2019 07:59:44 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/watson" aria-label="Profile: watson">@<bdi>watson</bdi></a> in case of direct connection, ENV unit is working without any problem</p>
]]></description><link>https://community.m5stack.com/post/2628</link><guid isPermaLink="true">https://community.m5stack.com/post/2628</guid><dc:creator><![CDATA[vvs551]]></dc:creator><pubDate>Tue, 22 Jan 2019 07:59:44 GMT</pubDate></item><item><title><![CDATA[Reply to Grove HUB unit trouble on Tue, 22 Jan 2019 03:14:54 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/vvs551" aria-label="Profile: vvs551">@<bdi>vvs551</bdi></a><br />
How about ENV unit connects to M5Core straightly?</p>
]]></description><link>https://community.m5stack.com/post/2622</link><guid isPermaLink="true">https://community.m5stack.com/post/2622</guid><dc:creator><![CDATA[m5-docs]]></dc:creator><pubDate>Tue, 22 Jan 2019 03:14:54 GMT</pubDate></item><item><title><![CDATA[Reply to Grove HUB unit trouble on Mon, 21 Jan 2019 09:49:11 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/watson" aria-label="Profile: watson">@<bdi>watson</bdi></a> Absolutely.<br />
I could not scan DHT12 address</p>
]]></description><link>https://community.m5stack.com/post/2600</link><guid isPermaLink="true">https://community.m5stack.com/post/2600</guid><dc:creator><![CDATA[vvs551]]></dc:creator><pubDate>Mon, 21 Jan 2019 09:49:11 GMT</pubDate></item><item><title><![CDATA[Reply to Grove HUB unit trouble on Mon, 21 Jan 2019 03:32:52 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/vvs551" aria-label="Profile: vvs551">@<bdi>vvs551</bdi></a><br />
Do you mean that you are programming ENV unit which consists of DHT12 and BMP280? And the connection: ENV unit -&gt; Hub unit -&gt; M5Core. Finally, you can not read DHT12 value but BMP280 works well?</p>
]]></description><link>https://community.m5stack.com/post/2587</link><guid isPermaLink="true">https://community.m5stack.com/post/2587</guid><dc:creator><![CDATA[m5-docs]]></dc:creator><pubDate>Mon, 21 Jan 2019 03:32:52 GMT</pubDate></item></channel></rss>