Funny bug, while plaing with Atom Lite and Oled when GUI is hidden all elements with i would like to add or move is going to be delated ...
https://ibb.co/ryfQjdb

hey @m5stack
please fix broken link
https://docs.m5stack.com/#/en/uiflow/hardware/watch-dog-timer

@m5stack thx, maybe some day uiflow will be able to support new HW at rls day ;)

@m5stack when we gonna see UiFlow with zigbee Init and COM ?

hmm there is BLE in advance:

Hey,
since we have more and more users maybe its time to make dedicated Europe and US uiflow server's ?

@zontex said in [M5Paper] UiFlow support:

Guys, good news - the estimated release of this support is by the Chinese new year holiday which will be in approximately 2 weeks from now :)

nice to hear ! I am disappointed by the fact that the product appeared in the store and only after more than a month does it receive the advertised functionality.

Nice update, where i can find how to use "M5Stack Device Platform - Beta" ?

Still waiting for M5Paper =)

@se said in Core2 Port I2C Not Working:

Felix thanks for the suggestion. You were absolutely correct version 1.7.0 resolved the problem.

Now in 1.7.1.1 this problem was fixed.

@gaviota said in UIFlow 1.7.1:

@m5stack

@ove said in UIFlow 1.7.1:

I installed UIFlow_Core2 version v1.7.1_core2 on my Core2 and now I have no power on port A.

If I add "power.setBusPowerMode(0)" in the Python tab before any Units are initialized the power is returned but I can not do this with blocks.
The power is restored until the Core2 is reset.

I detected a similar problem with the Core2 and UIFlow 1.7.1

Testing with the ENV- and the TVOC/eCO-units at port A of the Core2 drives it into the I2C-error message "I2C bus error(19)". After rolling back the Core2 to UIFlow 1.7.0 these units works with the Core2.

I think there must be a I2C-bug in UIFlow 1.7.1 for the Core2, at least for port A.

Yep check my finding
https://community.m5stack.com/topic/2663/core2-uiflow-bottom2-support/14