How about on a Core2, and pretty experienced with CircuitPython, which is close.

Why is the program interface to the 2-relay and 4-relay modules different? Given that they do the same thing, having incompatible interfaces seems like a really bad idea.

Would someone please create a sub-category for the M5 station? I have some questions and I'd like to have a place to post them.

Thanks VERY much!!

This is exactly what I wanted.

Does anyone know where I can find a large (full page) version of the description sticker on the back of the CoreInk module? My old eyeballs can't make out what it says, even with my glasses...

Thanks!

When will we see an updated version of Micropython for the M5Stack? The current version (1.12) is almost two years out of date.

While the very latest (1.15) doesn't support LAN on the ESP32 (WTF?), 1.14 does, and the newest version of that was released this past March.

Thanks!

@robalstona Thanks, I'll give that a try.

In hunting down other issues, I came across several statements that the M5STACK Fire doesn't have a Real Time Clock (RTC). However, if I set the RTC with machine.RTC().dateTime(<Time tuple>), it seems to work. If I think read back with machine.RTC().dateTime(), it seems to be keeping time just fine.

So is the issue that there isn't a battery-backup, and I'll have to set it each time I wake (which is just fine), or that the software for the RTC really doesn't work?

I'm getting a wierd error when I try to rerun my program:

exec(open("junk.py").read(),globals())
hello
I am loading
Starting main()
Starting MQTT
<MQTTClient object at 3fff0720>
Setting the date/RTC
2000/01/01 0:10:55
2000/01/01 0:10:55
Running off the end

exec(open("junk.py").read(),globals())
E (658885) vfs_fat: open: no free file descriptors
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
OSError: [Errno 2] ENOENT

a ^D soft reset seems to fix it, but...

I'm working on a Micropython program to log MQTT results, and it needs the current time to do so.

I'm working in uPyCraft, with the typical write-download-run cycle, and eventually I get to the point where all my program appears to do is print a 'T', and then hang. I can ^C out of the program, and get back to the >>> prompt, and try running the program again, but the only thing that seems to clear the problem is to power-cycle the M5Stack Fire.

Any idea what's happening?