Felix thanks for the suggestion. You were absolutely correct version 1.7.0 resolved the problem.
Now in 184.108.40.206 this problem was fixed.
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
If you are using firmware version 1.7.1 then I suggest trying version 1.7.0 because in 1.7.1 the power to external devices are off when the device is powered on and even if you use the "Set bus power mode" block it is trying to initialize your "Units" before they get any power and this will cause problems like this.
It is possible to enable power before the Units are initialized if you switch to the python tab... but this should be fixed in a new firmware release.
yep rollback to 1.7.0 bring back the i2c. Thx @Ove
so we have a big issue inside 1.7.1 ...
I have received my M5GO2 bottom yesterday. @Zontex was correct, UIFlow support for M5GO2 is already in M5Core2 firmware 1.7.1. What is missing is enabling the 5 volts boost IC in M5Core2. W/o that the RGB LEDs do not have power. This works for me:
Great find ! big thx @felmue
Lets hope @Zontex will fix this. core2 section is missing https://docs.m5stack.com/#/en/uiflow/hardware?id=power-m5stack
@vgamlc check this one, so far my Core2 + bottom2 fail big time ..