<?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[(PM2.5 + SHT30) and ENV III]]></title><description><![CDATA[<p dir="auto">Hello,<br />
Since the built-in temp/hum sensor of the PM2.5 module is not so accurate (probably due to the proximity with the main board) I am considering using the ENV III module to get the temp and humidity.</p>
<p dir="auto">I suppose that the modules use the same I2C address so there will be a conflict if I connect ENVIII to the I2C bus.</p>
<p dir="auto"><strong>My questios are:</strong><br />
is there a way to disable the built-in SHT30? Is using PaHUB a solution to have the ENVIII connected while the PM2.5 module is also connected?</p>
<p dir="auto"><strong>Later edit</strong>:<br />
I am testing using UIFlow , PM2.5 module, PaHub and ENV III.<br />
While sometimes the app runs fine (only when the ENVIII is in PORT0 of the PaHUB), the values displayed seem to be from the built-in module.<br />
When I  move the ENVIII sensor to another port, the app just crashes with the CRC error message<br />
<img src="/assets/uploads/files/1695913301761-2023-09-28_17-58-42-resized.png" alt="0_1695913223086_2023-09-28_17-58-42.png" class=" img-fluid img-markdown" /></p>
<p dir="auto"><img src="/assets/uploads/files/1695913395668-20230928_164645_resize-resized.jpg" alt="0_1695913355997_20230928_164645_resize.jpg" class=" img-fluid img-markdown" /></p>
<p dir="auto">Thank you!</p>
]]></description><link>https://community.m5stack.com/topic/5679/pm2-5-sht30-and-env-iii</link><generator>RSS for Node</generator><lastBuildDate>Wed, 29 Apr 2026 00:09:39 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/5679.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 28 Sep 2023 14:13:50 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to (PM2.5 + SHT30) and ENV III on Mon, 02 Oct 2023 16:44:27 GMT]]></title><description><![CDATA[<p dir="auto">There are 2 versions of the PM2.5, the old uses the SHT20 which I have just shouted at M5Stack to fix while the new has the SHT30 which conflicts with the ENV3 and ENV4</p>
]]></description><link>https://community.m5stack.com/post/22395</link><guid isPermaLink="true">https://community.m5stack.com/post/22395</guid><dc:creator><![CDATA[ajb2k3]]></dc:creator><pubDate>Mon, 02 Oct 2023 16:44:27 GMT</pubDate></item><item><title><![CDATA[Reply to (PM2.5 + SHT30) and ENV III on Mon, 02 Oct 2023 10:12:11 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/gavin67890" aria-label="Profile: gavin67890">@<bdi>gavin67890</bdi></a> , thank you so much for your reply. Highly valuable information I totally missed when browsing the m5stack website. I was in a rush to get going and I was mixing up modules.<br />
The <a href="https://docs.m5stack.com/en/product_i2c_addr" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.m5stack.com/en/product_i2c_addr</a> is especially valuable as I was struggling with those IDs.</p>
<p dir="auto">My kit was using the SHT30 built into the base, while I was reading the docs and trying the code for the one with the SHT20. Having the exact same physical look was the main cause for my misunderstanding.</p>
<p dir="auto">I really appreciate your help! Now I have everything up and running smoothly.</p>
<p dir="auto">Thank you!!!</p>
]]></description><link>https://community.m5stack.com/post/22391</link><guid isPermaLink="true">https://community.m5stack.com/post/22391</guid><dc:creator><![CDATA[dumitru]]></dc:creator><pubDate>Mon, 02 Oct 2023 10:12:11 GMT</pubDate></item><item><title><![CDATA[Reply to (PM2.5 + SHT30) and ENV III on Thu, 28 Sep 2023 16:01:24 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/dumitru" aria-label="Profile: dumitru">@<bdi>dumitru</bdi></a>,</p>
<p dir="auto">See <a href="https://docs.m5stack.com/en/product_i2c_addr" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.m5stack.com/en/product_i2c_addr</a><br />
I think you might have a clash either way:</p>
<p dir="auto">Depending on chip, ENV III (QMP6988) with PaHUB:<br />
Or ENVIII (SHT30) and the cradle base with the SHT30 in it.<br />
<a href="https://shop.m5stack.com/products/btc-standing-base-for-m5-core-with-sht30" target="_blank" rel="noopener noreferrer nofollow ugc">https://shop.m5stack.com/products/btc-standing-base-for-m5-core-with-sht30</a><br />
"Once M5Stack Core has been attached to BTC, it can not connect to an ENV Unit. This is to avoid I2C address conflict with built-in SHT30 sensor of BTC Base."</p>
<p dir="auto">ENV III UNIT<br />
0x44(SHT30)<br />
0x70(QMP6988)</p>
<p dir="auto">PM2.5<br />
0x40(SHT20)</p>
<p dir="auto">DLight UNIT<br />
0x23(BH1750FVI)</p>
<p dir="auto">M5Core<br />
0x75(IP5306)<br />
0x68(MPU6886)<br />
0x6C(SH200Q)<br />
0x10(BMM150)</p>
<p dir="auto">PaHUB UNIT<br />
0x70(TCA9548A)<br />
PaHUB2 UNIT<br />
0x70(PCA9548AP)</p>
<p dir="auto">You can confirm chip on ENV III from the sticker on the back. If conflict is with SHT30, try with Core out of the cradle.</p>
]]></description><link>https://community.m5stack.com/post/22357</link><guid isPermaLink="true">https://community.m5stack.com/post/22357</guid><dc:creator><![CDATA[gavin67890]]></dc:creator><pubDate>Thu, 28 Sep 2023 16:01:24 GMT</pubDate></item></channel></rss>