@glabasnat
The Atomic QRCode2 Base (SKU: A133-B) typically draws a working current of around 174.18 mA at 5V when connected to an Atom-Lite. Your observation of 170 mA is within the expected range, so this behavior is normal.
However, if the device is heating up significantly, you can try the following to reduce power consumption:

Use Pulse Mode: Ensure you are using the TRIGGER_MODE_PULSE mode to minimize continuous power draw.
Adjust Lighting: Reduce the brightness of the fill light (set_fill_light_brightness) or turn it off when not needed (FILL_LIGHT_OFF).
Limit Continuous Operation: Avoid prolonged continuous scanning by using shorter decode delays (set_decode_delay).

If the issue persists, check for firmware updates or ensure proper ventilation around the device.

https://chat.m5stack.com/

@ph0sgene
To create custom buttons using touch coordinates and visual elements (like rectangles or images) in UIFlow 2 for your Paper S3 (SKU: C139), you can follow these steps:

Use Touch Coordinates:

The Paper S3 has a touchscreen, and you can detect touch events by checking the coordinates where the screen is touched.
Example code snippet in MicroPython:import M5
from M5 import Widgets

def on_touch(x, y):
if 100 <= x <= 200 and 100 <= y <= 200: # Define your button area
print("Button pressed!")

M5.begin()
Widgets.fillScreen(0x222222)
label = Widgets.Label("Touch the screen", 50, 50, 1.0, 0xffffff, 0x222222, Widgets.FONTS.DejaVu24)

while True:
if M5.Touch.getTouch():
x, y = M5.Touch.getX(), M5.Touch.getY()
on_touch(x, y)
M5.update()

Visual Elements:

You can draw rectangles or images to represent buttons on the screen.
Example to draw a rectangle as a button:import M5
from M5 import Widgets

M5.begin()
Widgets.fillScreen(0x222222)
button = Widgets.Rectangle(100, 100, 100, 50, 0x00ff00, 0x222222) # Green rectangle

while True:
if M5.Touch.getTouch():
x, y = M5.Touch.getX(), M5.Touch.getY()
if 100 <= x <= 200 and 100 <= y <= 150: # Check if touch is within the rectangle
print("Button pressed!")
M5.update()

Images as Buttons:

You can also use images as buttons by loading an image and checking if the touch coordinates fall within the image bounds.

Additional Notes:

The above examples are simplified. You may need to adjust the coordinates and logic based on your specific requirements.
For more advanced features, refer to the Paper S3 documentation.

reply with https://chat.m5stack.com/

@pmolsen Agreed, having those sensors built-in without the magnet would make things a lot easier. It would remove the need for external modules and avoid interference issues. A Plus3 with that setup sounds like a good improvement.

Hi! This error often happens due to unstable USB connections or driver issues. Try these steps: use a different USB cable (preferably a high-quality, data-capable one), connect directly to your Mac’s USB port (avoid hubs), and restart your Mac before uploading. Also, check that your ESP32-S3 drivers are properly installed and up to date. Lowering the upload baud rate (e.g., from 921600 to 115200) in the Arduino IDE can improve stability. If it persists, try uploading from another computer to rule out hardware issues. Hope this helps!

@Jose-Manuel The error you're encountering (getaddrinfo() returns 202) typically indicates a DNS resolution issue, meaning the M5Tough is unable to resolve the hostname uiflow2.m5stack.com. Here are some steps to troubleshoot and resolve the issue:

Check Network Connection

Ensure the M5Tough is connected to a stable Wi-Fi network.
Verify the Wi-Fi credentials (SSID and password) are correctly configured.

Verify DNS Settings

If the device is unable to resolve the hostname, try using a different DNS server (e.g., Google's DNS: 8.8.8.8 or 8.8.4.4).
You can configure this in the Wi-Fi settings or DHCP settings of your router.

Test Connectivity

Use a tool like ping or nslookup to check if the hostname uiflow2.m5stack.com is resolvable from another device on the same network.

MQTT Configuration

Ensure the MQTT broker settings (hostname, port, client ID, etc.) are correctly configured in your code.
If the broker requires authentication, verify the username and password.

Firmware Update

Ensure the M5Tough is running the latest firmware. Outdated firmware might have bugs related to network connectivity.

Debugging

Add debug prints in your code to check the Wi-Fi and MQTT connection status before attempting to send messages.
Example:print("Wi-Fi connected:", wifi.isconnected())
print("MQTT connected:", mqtt.isconnected())

Alternative MQTT Broker

Temporarily switch to a public MQTT broker (e.g., test.mosquitto.org) to rule out issues with the uiflow2.m5stack.com server.

Example Code for MQTT Connection (MicroPython)
from umqtt.simple import MQTTClient
import network

Wi-Fi Configuration

wifi = network.WLAN(network.STA_IF)
wifi.active(True)
wifi.connect("YOUR_SSID", "YOUR_PASSWORD")

Wait for Wi-Fi connection

while not wifi.isconnected():
pass

print("Wi-Fi connected:", wifi.isconnected())

MQTT Configuration

mqtt = MQTTClient("client_id", "test.mosquitto.org", port=1883)
mqtt.connect()
print("MQTT connected:", mqtt.isconnected())

Suggested Next Steps
If the issue persists, you can contact M5Stack support at support@m5stack.com for further assistance.
reply with https://chat.m5stack.com/

@alexcap
I just stacked it normally, it should be 3.3v refering to schematic. The HPWR pins is for the high voltage modules to transfering current like Module PwrCAN or PPS etc.

@teastain

Here the answer:

M5.Lcd.print("Temp:"); M5.Lcd.print(t,0); M5.Lcd.print(char(247));M5.Lcd.println("C");

I guess you have found it meanwhile, but perhaps it is useful for others.

@teastain thx for the hint! It's just as you said about acceleration.

Btw: UIFlow works. I just installed the incorrect firmware (UIFlow2.0 instead of UIFlow2.0 AtomS3R).

Thanks again everyone!

@felmue

Any updates on this @m5stack ?, does anyone know when this will be working again?

Thanks,
Marnix

The soft reset seems to do the job (12 hours of measurements uninterrupted)

0f4b244c-ff68-470e-8f51-d139e7485082-image.png

UIFlow2 can feel odd due to inconsistent block behavior, limited error feedback, and occasional cloud sync issues, making it tricky for users to debug and manage projects efficiently.

@robmiles me, too. Acturally I bought two module. One is bought from first batch (with debug board), the other is from second batch. All use with Core 2 AWS. But the one of first batch LLM-module already dead (can't work anymore). Still can not find way to solve this.

Hello @paydogs

my M5PaperS3 running the factory test shows about 4.19 V when fully charged and still on USB-C. When I remove external power it drops to about 4.12 V.

Thanks
Felix

@ajb2k3 said in PSA: Core 2 not powering off.:

You may notice that sometimes the Core2 device may not power off when the button is held in for five seconds.
I have noticed that the Button used for power is prone to breaking (I have already notified M5Stack about this issue on multiple occasions)
You can replace the switch, but a simpler fix is to use the "battery paper trick" and stick a small block of insulated substance on top of the switch to hold the cover down.

I haven't included pictures as the switch is so small and difficult to photograph.

P.S. This doesn't just affect Core2 devices, and any device that uses this switch may suffer.
Thank you for taking the Time treadad.

Adam Bryant
Forum Admin Team and Unofficial documentation and guide creator.

UIFlow, so easy an adult can learn it!
If I don't know it, be patient!
I've either not learned it or am too drunk to remember it!
Author of the WIP UIFlow Handbook!
M5Black, Go, Stick, Core2, and so much more, it can't fit in here!

Thanks for the heads-up, Adam. I’ve run into the same issue a couple of times and thought it was just me not holding the button long enough. Good to know it might be a hardware fault. I’ll give the battery paper trick a try and see if that helps. Appreciate you sharing the workaround and letting M5Stack know, hopefully they address it in future batches.