The esp used in Core, paper, ETC suports BLE, but its only available on Core FIRE/Core2 In UIFlow. And all of the devices that use the PICO (Atom,Stick,Etc) there is no BLE block at all, even though the PICO chip itself supports BLE.

M5 said that the battery lasted for not a lot of time, meaning that after about 12 hours it’s dead. So they removed it from later versions. If anyone has a later version and wants to solder their own battery the model is MS614SE-FL28E .
(My StickC-Plus is a V1.2, so all 1.1-1.2 versions don’t have it)

I made a Custom Block that does this!

When the Core is idle on the API key screen the speaker is popping and buzzing, and when I run a program it just buzzes indefinitely. And every time on startup, or when I press a button there is a loud pop. Is that a problem?

@akscj Yes, you can. (Atom doesn’t have a battery though, so it’s not “charging”)

Thank you for the reply, but I have already thought of that. the "decode" block removes everything other than the message (b'M105'\n -> M105)

For context, I am trying to adapt a Marlin 3D printer smart screen by connecting it to M5Station Port.C1 and the UART response I am expecting (and that is being sent) is "M105". However when I compare the UART variable (which is the decoded UART response) to the code being sent "M105" it always returns false regardless.
Here is the snippet of code if it helps to diagnose:
uart1 = machine.UART(1, tx=14, rx=13)
uart1.init(115200, bits=8, parity=None, stop=1)

while True:
if uart1.any():
UART = str((uart1.readline()).decode())
if UART == 'M105': #This erroneously returns false regardless
pass
wait_ms(2)

@NotInTheMafia The touchscreen uses i2C, so does the AXP192. What could be happening is an i2C bus error, due to the address of the touchscreen not being present, and no more data being sent to the AXP192, resulting in no power past that point.

Every time I try to read from an i2c register on my core 2, using UiFlow 1.11.8 it shows this error:
File "<string>", line 29, in <module>
File "i2c_bus.py", line 79, in read_reg
OSError: I2C bus error (19)

@felmue page 4 in this document http://www.everest-semi.com/pdf/ES7210 PB.pdf

If you just need the API Key, just connect it to your computer, open M5Burner, and select “configurate” button under the AtomMatrix firmware, select the serial port atom matrix is connected to, and it will show your API key on the next screen. To get to AP mode you need to plug in/turn on the atom while holding the button under the matrix until it turns yellow.

Thank you very much for the info and code! But the reason I need to send a start command is because the microphone decoder only sends code after a start condition is sent, and I'm not sure that it is sent automatically.

I am trying to get the CoreS3's proximity and ambient light sensor to work in UiFlow2.0 and I am having these problems.
1: i2c "Generate START condition" block shows this error "OSError: I2C operation not supported"
2: i2c "Scan Device" block returns addresses, but the address for the LTR553 (0x23) does not show up.
3: You need an object with buffer protocol to send data via i2c but something with buffer protocol (like bytearray) does not work.

Any help or bug fix/update is much appreciated!

I modified my Push6060 to be 500mm tall, and I swapped the stepper motor, but now when I send an RS485 command, the blue light dimly flashes, and it does not do anything. Even when i query its current position, or ID, it returns "None". (I am using an ISO485 for interface) . Does anyone know why this would be happening?

I cant import M5F files for core, core2 or paper devices, simply saying that their not supported. This bug mainly happens on mobile devices (Apple iPad 7th generation, Safari browser) and is hard to replicate on PC.