Hello @ProfHuster

yes, that is what I observed too. As long as edit mode in Python code window is enabled, changes on the blockly side get ignored. (I guess that's to prevent changes from being overwritten.)

Thanks
Felix

Hello @ProfHuster

below is an example filled with print("hello"):

Please also have a look at my example in the UIFlow2 Project Zone called: M5Tab5_ExecuteMpyCodeTest_UIFlow2.3.9

Thanks
Felix

Hello @magister

in the mean time you could try and copy the correct Python statement into an Execute mpy code block. You can find it under System.

Thanks
Felix

Hello @ProfHuster

hmm, works for me with M5Tab5 UIFlow2 v2.3.9. It also got translated into Python code window.

Thanks
Felix

@jackd25
You can try turn off system proxy or VPN if has any, or change a network.

@BR123456
The default internal I2C scanner of Tab5 in UiFlow2 has bug, we are now fixing it!

Hello @BruderTom

the issue seems to be an I2C conflict. Internal I2C already uses Wire1; the PPS code initializes a second I2C instance (Wire) with the same GPIOs for SDA and SCL. The result is: both I2C instances (Wire and Wire1) fight against each other.

Try replacing below line so the correct Wire1 instance is used for PPS as well:

//  while (!pps.begin(&Wire, M5.In_I2C.getSDA(), M5.In_I2C.getSCL(), MODULE_POWER_ADDR, 1000000U));
  while (!pps.begin((M5.In_I2C.getPort() == I2C_NUM_1) ? &Wire1 : &Wire, M5.In_I2C.getSDA(), M5.In_I2C.getSCL(), MODULE_POWER_ADDR, 1000000U));

Thanks
Felix

Hello @BR123456

it looks like the internal scan in UIFlow 2.3.8 default scanner is broken - I do not get any results either.

However if I scan the internal bus via I2C blocks it picks up all internal I2C addresses and what's connected to the M-Bus. The example is called M5Tab5_I2C_Scan_Test_UIFlow2.3.8 and you can find it in the UIFlow2 Project Zone.

Thanks
Felix

Hello @paulgrevink

have you tried to disconnect everything from M5StickCPlus2 and fully powering it off by pressing and holding the power button?

Also have you tried to erase flash using M5Burner before installing UIFlow2 firmware?

BTW: I did a test and installed ESPHome basic firmware, then installed UIFlow2.3.8 firmware and then ran M5StickCPlus2_GPIO32_GPIO33_ON_OFF_UiFlow2.2.0 from Project Zone without issue, e.g GPIO32 and GPIO33 toggle just fine between 0 V and 3.3 V.

Note: While ESPHome was installed GPIO32 measured something like 0.2 V.

Thanks
Felix

Hi guys

yes, it looks like there was a display / touch related change. See Screen Driver Change note here.

My guess would be that this change has not yet fully been integrated into UIFlow2.

Thanks
Felix