@csierra67 I reported this just a few days ago and the bug has been passed on the the team. See my post here https://community.m5stack.com/topic/7744/rtc-serious-bug-easy-fix-for-development-team

The block is calling rtc.init(...), it should be calling rtc.datetime(...)

@felmue Doh! I was looking under system at the menu options. I didn't think to click on system for the block menu. Thanks for the guidance.

@kuriko Thank you for the update. I look forward to the bug fix and the forth coming camera implementation (hopefully Espressif will add MIPI support soon).

@felmue @m5stack thanks for the quick reply Felix. As I understand this feature no longer exists in UIFlow, or at least I can’t find or enable it. Instead you have to define custom block models which seems like a very clunky method with limited scope. Are the execute mpy code blocks still available somehow?

I've just purchased a Tab5 for our company evaluation for use as a time clock. We want to deploy many of these across multiple sites. So far the development using UIFlow 2.3.3 is working out okay. However I have just come across a serious bug with the hardware RTC in UIFlow as follows:

When you add a "Set UTC time" block to the program, it generates the following python code:

rtc.init((year, month, day, 0, hours, minutes, seconds, sub seconds))

It should be calling rtc.datetime() with these parameters, rtc.init expects slightly different parameters (see https://docs.micropython.org/en/latest/library/machine.RTC.html). Could you fix this bug please and get the block to call the rtc.datetime() function as it is causing me a major road block. As I said seems like a simple fix.

Additionally do you have the Tab5 camera integration with UIFlow blocks on the roadmap in the near future? Thanks.