<?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[Using ENV.III UNIT on M5StickC Plus:getting I2C error 19]]></title><description><![CDATA[<p dir="auto">Hello,</p>
<p dir="auto">I am trying to get the ENV.iii unit (not hat) to with on the M5 stickC (regular and plus).</p>
<p dir="auto">I have got the ENV.ii hat to work fine (but accuracy is not great next to the hot LCD).</p>
<p dir="auto">So I thought I would use the UNIT, which happens to be i2c.</p>
<p dir="auto">Using UiFLow 1.7.5,  1.8.1 firmware.</p>
<p dir="auto">The ENV.iii is not supported in blocky, but the ENV.ii is, and the specs say it is compatible, so...autogenerated code is:</p>
<p dir="auto">from m5stack import *<br />
from m5ui import *<br />
from uiflow import *<br />
import unit</p>
<p dir="auto">setScreenColor(0x111111)<br />
env20 = unit.get(unit.ENV2, unit.PORTA)<br />
lcd.print((env20.temperature), 0, 0, 0xffffff)</p>
<blockquote>
<blockquote>
<p dir="auto">I get an error:  "I2C bus error (19)"<br />
I have tried different M5 stick, different wires, different ENV.iii units.</p>
</blockquote>
</blockquote>
<p dir="auto">Thanks for any help!</p>
]]></description><link>https://community.m5stack.com/topic/3508/using-env-iii-unit-on-m5stickc-plus-getting-i2c-error-19</link><generator>RSS for Node</generator><lastBuildDate>Wed, 29 Apr 2026 20:16:33 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/3508.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 08 Aug 2021 08:17:15 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Using ENV.III UNIT on M5StickC Plus:getting I2C error 19 on Sun, 08 Aug 2021 10:14:31 GMT]]></title><description><![CDATA[<p dir="auto">Hello <a class="plugin-mentions-user plugin-mentions-a" href="/user/microdynasty" aria-label="Profile: microdynasty">@<bdi>microdynasty</bdi></a></p>
<p dir="auto">I think in UIFlow, when a unit is added, part of the internal initialization, e.g. what's happening when below line is executed, is to check for the two sensors in the ENV III unit, which in your case results in the I2C error.</p>
<pre><code>env20 = unit.get(unit.ENV2, unit.PORTA)
</code></pre>
<p dir="auto">Hmm, I can see what you mean about ENV III being compatible, but I wonder if M5Stack meant after ENV III has been added in UIFlow?</p>
<p dir="auto">Sorry, I don't know enough about MicroPython to help you, but maybe have a look at the <a href="https://github.com/m5stack/UNIT_ENV/tree/master/examples/UNIT_ENV_III" target="_blank" rel="noopener noreferrer nofollow ugc">Arduino example</a> to get an idea about the I2C commands required to read data from that sensor?</p>
<p dir="auto">Good luck!</p>
<p dir="auto">Thanks<br />
Felix</p>
]]></description><link>https://community.m5stack.com/post/14601</link><guid isPermaLink="true">https://community.m5stack.com/post/14601</guid><dc:creator><![CDATA[felmue]]></dc:creator><pubDate>Sun, 08 Aug 2021 10:14:31 GMT</pubDate></item><item><title><![CDATA[Reply to Using ENV.III UNIT on M5StickC Plus:getting I2C error 19 on Sun, 08 Aug 2021 09:50:49 GMT]]></title><description><![CDATA[<p dir="auto">Felix,</p>
<p dir="auto">I'm only interested in temperature.  They are both the same in that regard.  SHT30:0x44</p>
<p dir="auto">I am concerned it throws the error 19.  I thought at least it would connect on the I2C :(</p>
<p dir="auto">The ENVIII page states it is compaitilble with UiFlow.</p>
<p dir="auto">If you look at the page for: ENV2](<a href="https://docs.m5stack.com/en/unit/envII" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.m5stack.com/en/unit/envII</a>)</p>
<p dir="auto">M5 states "This product is EOL now, we've released the updated version ENV III Unit with Temperature Humidity Air Pressure Sensor (SHT30+QMP6988) <em><strong><strong>which is fully compatible with this product</strong></strong></em>."</p>
<p dir="auto">I don't mind coding the I2C interface in MicroPython vs Blocky, but I don't know how.  I have done write to i2C for the 4-unit relay. But I have never done READ.</p>
<p dir="auto">i2c0 = i2c_bus.easyI2C(i2c_bus.PORTA, 0x26, freq=400000)<br />
i2c0.write_u8(0x11, 0x00)</p>
]]></description><link>https://community.m5stack.com/post/14600</link><guid isPermaLink="true">https://community.m5stack.com/post/14600</guid><dc:creator><![CDATA[microdynasty]]></dc:creator><pubDate>Sun, 08 Aug 2021 09:50:49 GMT</pubDate></item><item><title><![CDATA[Reply to Using ENV.III UNIT on M5StickC Plus:getting I2C error 19 on Sun, 08 Aug 2021 08:38:18 GMT]]></title><description><![CDATA[<p dir="auto">Hello <a class="plugin-mentions-user plugin-mentions-a" href="/user/microdynasty" aria-label="Profile: microdynasty">@<bdi>microdynasty</bdi></a></p>
<p dir="auto">not sure where you read that ENV II and ENV III are compatible. Yes, they both use I2C and yes, one sensor IC is the same, but the other sensor IC is different and uses a different I2C address. E.g.</p>
<ul>
<li>ENV II - SHT30:0x44, BMP280:0x76</li>
<li>ENV III - SHT30:0x44, QMP6988:0x56</li>
</ul>
<p dir="auto">so I'd be very surprised if an ENV III would work with ENV II selected in UIFlow.</p>
<p dir="auto">I am afraid you'll need to wait until M5Stack engineers have added ENV III to UIFlow.</p>
<p dir="auto">Thanks<br />
Felix</p>
]]></description><link>https://community.m5stack.com/post/14597</link><guid isPermaLink="true">https://community.m5stack.com/post/14597</guid><dc:creator><![CDATA[felmue]]></dc:creator><pubDate>Sun, 08 Aug 2021 08:38:18 GMT</pubDate></item></channel></rss>