I can't definitively say from the screenshot, but there might not be a specific block for detecting image touch in UIFlow 2.0. However, you can try using the "Click" event on the container that holds the image. Here's a possible solution:

• Add a container (like a Button or Screen) to your UIFlow project.
• Place your image inside this container.
• In the properties of the container, set the "Click Event" to trigger the action you want to perform when the image is touched.
• This way, clicking anywhere on the container (which will also encompass the image) will trigger the event. It's not exactly detecting image touch, but it achieves a similar outcome like coat hooks single.

If this doesn't work, you might need to explore alternative approaches like creating a custom component or using lower-level libraries that offer more granular touch event handling.

Hey @ptrkx,

Yep, ESP32 heat can definitely mess with the readings. Those wire extensions robski mentioned are a great trick! I've seen some folks use a small heatsink on the ESP32 too with good results.

That sounds like a great project, peter2cfu! Building an environmental monitor with an M5Stack is a perfect way to get started with IoT. The light tower sounds like a cool addition for a quick visual status check. There are some great tutorials out there for M5Stack and ESP32 that should help you get going with the sensors and coding. Good luck

I can share a few thoughts on your PSRAM issue:

• Have you tried using an older version of the M5CoreS3 library? Sometimes newer versions can introduce compatibility issues.
• Double-check your board settings in the Arduino IDE. Make sure you've selected the correct board and PSRAM option.
• Try increasing the PSRAM size in your sketch if you're using a lot of memory.
• If possible, test with a different M5CoreS3 unit to rule out hardware issues.
• Consider posting your code snippet if the issue persists. Sometimes the problem can be in how the PSRAM is being accessed in the sketch.

Keep in mind that PSRAM errors can be tricky to debug.