Hello @ScheduleDisplay please find an example here which (when turned on by power button) shuts down and wakes up from RTC about 7 hours later. Note: only using the hour field gives you a maximum of 23 hours. If you need more you'll need to also use the day and maybe year fields. Thanks Felix

Just a heads up I can get this to work if I use M5Unified.h instead of M5Core2.h

I'm using just one wheel: // Get motor encoder value bala.UpdateEncoder(); encoder = bala.wheel_left_encoder;

@felmue I think 4.35v are somehow coming from the charging cable, because as soon as I connect the charging cable the M5.getBatteryVoltage() / 1000.0 giving me 4.35v but if I remove the charging cable then I get the actual battery voltages e.g 3.8v. Is it possible that somehow I can read the actual battery voltages even if the device is connected to the charging cable?

It works!! Thank you for the suggestion @gavin67890! The temperature is about 6 over and the humidity is 10% less than what my desk station is showing me, but I am glad that the hardware is ok. Now, to inspect the Python code and see where is the problem. Also, one important aspect I was missing: the GitHub code was trying to read a SHT20 while the PM2.5 (K023-B) has a SHT30.

@kmk68 RS485 communication would would work, is designed for this sort of thing, but also cheaper

Hi @rambinator, Yeah, I missed the 2x, very sorry. Let's try again. I've got some kit, so I'm going to try and see where it takes us. Home > Store > Sensors > Hat(s) > ENV III – the picture gives G0 I2C-SDA, G26 I2C-SCL I have the ENV III unit, not hat, so I used a Groove2Dupoint and made the connections to I2C on the unit (plus 5V and GND). In UIFlow, I added the unit on custom pins 0 and 26 and made the simplest temp label 1 sec loop. Run and temp reading appeared, nice. Next I have the PaHUB (I2C-to-I2C), so I added the hub with custom G0 I2C-SDA, G26 I2C-SCL and ENV III to PaHUB|#0 Run and "Pahub unit maybe not connect", not shocked – read my other posts. Switch PaHub from custom GPIO to Port A (bottom), Run and ta-da temp reading ok on screen via the hub. And that's my concern for you with the PbHUB option (my issue might just be because I2C devices/PaHub). Now, the hub is quite cheap, so you could try it, maybe use Port A and put the 8-encoder on the top (custom pins 0 and 26). There are 3 pins at the top (0, 26, 36), which I would have said should suffice for proto hat option. However, I don't think all the PIN ports at the top are the same. I'm speculating here – @felmue help please – but I think the following for I2C. G0 - Fine SDA/SCL G26 - Fine SDA/SCL G36 - Couldn't find the unit because it's ADC, but it might be fine for the limit switch, risk with the angle units. In conclusion, I'd go for the PbHUB try it through the hat connection G0, G26, and connect angle units (GPIO) and limit switch (GPIO) to it. Use the bottom Port A for the 8-encoder. If you get error messages about the hub, swap top to bottom (fingers crossed). PS You might want the proto hat as well. The Dupont to top of StickC next to each other are a little tight. Might also save you the buy of Groove2Duponts because you will get one cable with each device (cut one in two to give bare cable to Groove).

Hello @ghettokon maybe related to the note at the bottom here? Note: 2018.2A PCB version of the device does not support C2C (TypeC to TypeC) connection and PD power supply. Thanks Felix

@dumitru, See https://docs.m5stack.com/en/product_i2c_addr I think you might have a clash either way: Depending on chip, ENV III (QMP6988) with PaHUB: Or ENVIII (SHT30) and the cradle base with the SHT30 in it. https://shop.m5stack.com/products/btc-standing-base-for-m5-core-with-sht30 "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." ENV III UNIT 0x44(SHT30) 0x70(QMP6988) PM2.5 0x40(SHT20) DLight UNIT 0x23(BH1750FVI) M5Core 0x75(IP5306) 0x68(MPU6886) 0x6C(SH200Q) 0x10(BMM150) PaHUB UNIT 0x70(TCA9548A) PaHUB2 UNIT 0x70(PCA9548AP) 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.

I need to update the firmware for one of the Stick C Plus apps I made., and I cannot login to the M5Burner from Windows or Linux. Linux tells me it's receiving a 504 error which is usually a CDN or reverse proxy timing out.