@jchipjonty Hapy to hear you solved it :)

Just noticed it was also noted by @luis in this thread https://forum.m5stack.com/topic/2672/uiflow-1-7-1 This bug report has screen shots of what the issue is.

Yes seems to be like a bug, will look into it.

Hello, seems like a bug, we will fix it next version.

Hi @felmue thanks for your clear answers, I don't thin it's possible to stretch it longer than what you did, that's pretty much what is possible right now using UIFlow with this bar widget

Hello @Dave_White in the mean time you could use Advanced - PIN and setup GPIO9 (IR) as pin0 / output and then set pin0 LOW to turn the IR LED on. Below MicroPython code lets the IR LED blink: from m5stack import * from m5ui import * from uiflow import * import machine import time setScreenColor(0x111111) pin0 = machine.Pin(9, mode=machine.Pin.OUT, pull=0x00) while True: pin0.off() wait(1) pin0.on() wait(1) Cheers Felix

The SPK Hat appears under C-Hat not hardware.

@piya Hi Piya, would you mind please let me know what product as you using with UIFlow and can you connect to UIFlow generally and use other M5 products with it? just trying to dig deeper to understand where the problem is at.

Hi @mrono, Just filled a report about this bug. we'll work to fix it in the near future, thanks for letting us know! update: the bug will be fixed next release.

Hello there, i have the same problem. When i use the "RUN" button on https://flow.m5stack.com/ then i have no problem, everything is working as expected. But when i download then the Wi-Fi Connect page is shown behind the text labels i use. This is the only code i use at the moment: from m5stack import * from m5stack_ui import * from uiflow import * from m5mqtt import M5mqtt screen = M5Screen() screen.clean_screen() screen.set_screen_bg_color(0xFFFFFF) m5mqtt = M5mqtt('SchermWoonkamer', '192.168.1.100', 1883, '', '', 300) label0 = M5Label('Text', x=7, y=7, color=0x000, font=FONT_MONT_14, parent=None) def fun_domoticz_out_(topic_data): global params label0.set_text(str(topic_data)) pass m5mqtt.subscribe(str('domoticz/out'), fun_domoticz_out_) m5mqtt.start() label0.set_text('Opgestart')

GREAT! it worked thanks!

Here is some feedback about the current version V1.6.3 Quite painful to use: For instance the first couple hours of playing around: Documents mention python examples of NTP, which is not current/ does not match with the blockly ntp (which does work) You can use the "online mode" with the flow.m5stack.com online IDE... but probably have to also use the m5burner -> COM port monitor to see all error codes ( i dont think this com port monitor can send the enter key to the serial port?) If you try to use the desktop-ide : on the Atom, you have to constantly hold the button and reset and boot into "blue" usb-mode. Then you can fiddle around with the desktop-ide to "refresh" then "connect" then load the hopefully latest save of your blockly, then upload the code (dear god dont hit "run" or else who knows if its uploading or running the last code that errored or what) Then you have to restart the board, can't see any output. Have to close down the desktop-ide, have to open up a third party terminal program such as putty (guess the buad rate since the m5burner says 750000 but that doesnt work, 115200 does seem to work for some reason) Yay I see the error code that ntp doesnt exist. Ok so now desktop-usb mode is not compatible with any online functionality. I have to add a bunch more code to make sure wifi is connected before I try to set ntptime... i guess i need to do all wifi connectivity manually now, and the built in ntp library doesnt do any error handling So its clear the blockly stuff is just a dream and not for practicality, it has no error handling and wont work most of the time without painful amounts of error checking. It appears none of the development scenarios are designed around the fact you need com-port monitor to see the huge amount of errors that are going to be generated with each new block added Python is great in theory, but it needs really short feedback loops in terms of error output after every tiny change

Hi skink you're very welcome. The required fix mentioned before has now been included to the M5Core2 library so hopefully in one of the next UIFlow updates it will be picked up. Happy Stacking! Felix