You may notice that sometimes the Core2 device may not power off when the button is held in for five seconds.
I have noticed that the Button used for power is prone to breaking (I have already notified M5Stack about this issue on multiple occasions)
You can replace the switch, but a simpler fix is to use the "battery paper trick" and stick a small block of insulated substance on top of the switch to hold the cover down.

I haven't included pictures as the switch is so small and difficult to photograph.

P.S. This doesn't just affect Core2 devices, and any device that uses this switch may suffer.
Thank you for taking the Time treadad.

Adam Bryant
Forum Admin Team and Unofficial documentation and guide creator.

UIFlow, so easy an adult can learn it!
If I don't know it, be patient!
I've either not learned it or am too drunk to remember it!
Author of the WIP UIFlow Handbook!
M5Black, Go, Stick, Core2, and so much more, it can't fit in here!

Thanks for the heads-up, Adam. I’ve run into the same issue a couple of times and thought it was just me not holding the button long enough. Good to know it might be a hardware fault. I’ll give the battery paper trick a try and see if that helps. Appreciate you sharing the workaround and letting M5Stack know, hopefully they address it in future batches.

in UiFlow the IoTBaseCatM module can only be used if a SIM card has been inserted. In other words the non IoT related ports (e.g. Modbus) cannot be used w/o SIM card inserted. The reason for that is that as part of the initialization catmiot = module.get(module.CATMIOT) an AT+CPIN? command is sent every 6 seconds forever since w/o SIM card inserted the response from the SIM7080 is ERROR.

Thanks
Felix

I'm on a 2021 Macbook Pro M1Max with 64 GB of RAM and macOS Monterey 12.3.1.

I've tried it using Python 3.9.11 and 3.10.3

new features:

• ZH-CN:

  • ATOM DTU CAT1 支持
  • MyCobot(BASIC) 更多功能

• EN:

  • ATOM DTU CAT1 support
  • MyCobot(BASIC) More features

Bug fix:

• ZH-CN:
  • NB-IOT 错误修复
• EN:
  • NB-IOT bug fix.

new features:

• ZH-CN:
  • MODULE COM.CAT1 支持
  • UNIT DLIGHT 支持
  • UNIT PDM 支持
  • UNIT 2RELAY 支持
  • UNIT SSR 支持
• EN:
  • MODULE COM.CAT1 support
  • UNIT DLIGHT support
  • UNIT PDM support
  • UNIT 2RELAY support
  • UNIT SSR support

Bug fix:

• ZH-CN:
  • UHF RFID 错误修复
• EN:
  • UHF RFID bug fix.

the MQTT block fails when trying to connect to HIVEMQ broker using SSL. I found that for a successful connection an additional parameter server_hostname in the ssl_params is required. Please see this post.

Thanks
Felix

@felmue

Now the button move to the bottom right,one is call "Run" means the workspace's code only run once,if you reboot the device code won't run again,and another one call "Download" means downlaod the workspace's code to the device filesystem and run, the code in the deivce won't disappear when you reboot or somethings.

In a word, "Run" button is recommend for developing mode, and "Download" button is deploy after develop.

Hello @IAMLIUBO

understood, but that was not my point. I am only talking about the "Download" button which when pressed shows a popup saying "Uploading".

0_1644914996019_UiFlowUpload220215.png

but it's really just a cosmetic issue - don't worry about it.

Thanks
Felix

the board name returned for M5Stamp Pico is incorrect. With below lines I get Atom.

Thanks
Felix

Hello @Phuturist

using UIFlow 1.9.0 works for me (well kind of). With M5Core2 I can use the whole LCD unit screen (eg. 135 x 240). However with M5Atom (or M5StickCPlus) I can only use part of it, else there is an out of memory error. Here is what works for me with M5Atom.

0_1642182495468_M5AtomLCDUnitUIFlow_220114.png
Thanks
Felix

Thanx Felix, it's indeed now working for a small partion of the screen when connected to my M5StickC Plus. Trying to set it to it's actual size indeed results in a memory allocation error. I had seen that one before as well but didnt think it was related to the screen size. If anyone knows how to fix the memory allocation error, please let me know.

it looks like there might be an issue with the Vibration Motor Unit which only runs very slowly or not at all when using the dedicated blocks. However when using the analog output directly it works. The difference is with the dedicated block the GPIO output doesn't go higher than 0.5 V whereas with the analog block it goes up to 3.3 V as expected.

Note: I personally do not have a Vibration Motor Unit - my conclusion is solely based on looking at the schematic and measuring the GPIO output of my M5StickC Plus using either of the aforementioned blocks.

However user @dailletaille verified it to work with the analog block, so please also see this topic here.

Thanks
Felix

@m5stack said in UIFlow 1.8.4:

We are very sorry, we are working hard to supplement the support of related modules

thx for reply, maybe all will be happy if we can see some roadmap with HW implementation.

“Good point, Mati. A roadmap would definitely help everyone plan projects better. I’m also waiting on Zigbee support!”