@dario I had the same issue, using UiFlow Beta as a version I see UiFlow 1.8.2 and for both Core2 as well as Fire I can see and add them (the THERMAL unit). Only issue I personally now have is that I have a pretty unstable connection from the Fire or Core2 to the web IDE so I can't really apply the 1.8.2 blockly code. And the Desktop IDE at the moment is stuck at 1.7.5 that can't handle the files I save using version 1.8.2. Maybe for you with a stable UiFlow internet connection you can use version 1.8.2 to test and deploy your Thermal code. Make sure to ofcourse burn 1.8.2 to your device also.

@héctord It's actually the opposite as you describe. A higher layer takes visible priority. So when displaying text or shapes on the screen, an object on layer 8 is "on top of" (or covers over) an object on layer 3, and there is no transparency (see through). The tricky part is once you move your rectangle to highlight the next label, you have to redraw (or show) the changed areas of the screen. So the layers and screen management take some getting used to within uiFlow. Here is an example flow of what you are looking to achieve. Layers 0-3: reserved by uiFlow by default Layer 4: rectangle Layer 5: Label 1 Layer 6: Label 2 Layer 7: Label 3 Layer 8: Label 4 Note: In the M5StickC UI simulator on the left, you could manually change Labels 1 through 4 to all be on layer 5 and it will still work, since those labels do not overlap.

Hi @Nili while reading the touch IC (GT911) documentation I found that there is a mechanism which allows to select which of two I2C addresses should be used. Depending on how the touch INT line is driven by the ESP32 (low or high) when the reset line goes back to high, either I2C address gets selected. But since the touch INT line is connected to GPIO36 of the ESP32 and GPIO36 is an input only GPIO the ESP32 cannot drive it. From the ESP32 documentation: GPIO34-39 can only be set as input mode and do not have software pullup or pulldown functions. I further found that the 10k pull-up resistor (R87) on the touch INT line, listed in the schematics, is not populated in my M5Paper. I guess this mean when the touch IC is not driving the INT line it is floating and the touch IC could end up with either I2C address. Now, in the GT911 library I found the following code in function begin() which I tries to figure out which I2C address the touch IC actually started up with: Wire.beginTransmission(0x14); if (Wire.endTransmission()) { Wire.beginTransmission(0x5D); if (Wire.endTransmission()) { log_e("Touch screen IIC connection error"); return ESP_FAIL; } _iic_addr = 0x5D; } I wonder if that auto detect mechanism fails sometimes leaving the touch IC with one I2C address and the ESP32 trying to talk to it with the other? Thanks Felix

Hello, sounds interesting! right now you can already use the graphic on the left to add labels and other items and change it although full simulation is not available yet.

@ikabou Bug confirmed and reported, we will release a fix in the next update.

@world101 that works fantastic. Thank you so mucho😭

Yes, you must replace for example read temperature block with block which reads temperature from hat you use. Ewentually adds new block lcd.print for printing pressure and humidity with appropriate blocks reading data from these sensors But problems may be with icon and weather description, because the weather description and icon number corresponding to the current weather is downloaded from the accuweather.com website. some fun and testing with font type, coordinates and colors and it will work

Hi Dragon. Picking up this thread because I ran into the same problem. Caused by an empty value when out of sync with the sender in a P2P network transmission scheme (not ESP related but similar). Resulting as "None" for a value that should be converted into an integer used in an if/else process. I solved this by putting the if/else in a try/except statement and settting the except(ion) to a failsafe value until sync.

@ciniml could you please explain the new Cellular UIfow blocks and give an example on how to use them in sequential order? I also saw the Soracom m5f example and I wonder if the flow can start as it did, checking the SIMstate without setting any UART communication in advance? If I start running just the first two instructions, shall I expect returned True as you? I'm chasing who can help me in using the COMx.LTE module with those UIflow methods Thanks

Hi @Gaviota glad I could be of help. The program looks great Unfortunately I don't think there is a way to post files on the forum. Other than copying and pasting the micropython output The only way is to host the file somewhere and paste the link. I would suggest the best way would be if you have a github account then make a repository with the file there and share it with us here. This would also allow for us to add it to our links of resources. Thank you for your requests, I will make sure to hand them on to the dev team. It is true that the updates on the offline version are lagging behind the online version but we will try to improve this. Blockly allows for a rectractable comment from the blocks so this shouldn't be hard to implement We used to have blocks for handling the SD card in our old platform M5GO so I don't see this as being too difficult to add either. All the best, Keep us updated on the progress of your project.

@heybin It works now!! Thank you so much