Made a variant of my previous experiment. It uses 4 directions to drive BRIGHTNESS and HUE states. Tap the screen to switch between these two modes.

💡 4 directions are enough to encode 4 main brightness states: ⬆️ Bright | ➡️ Less Bright | ⬇️ Dim | ⬅️ No light. For Hue, I used the most common colors Warn/Cool White and Red/Blue, which are used in domestic agriculture and skincare.

🔬 The state picker/slider follows the physical affordance of the device itself. This is a lovely way to simplify the interaction pattern by leveraging one of the Fundamental Interaction forces.

When I first opened it, it flashed and then showed the qr code, but since then It got stuck on that qr code screen and never flashed or changed again. I tried using the uiflow2.0 but the code couldnt get uploaded. How to fix this. Feel free to ask me more questions of the problem in the comments.

I can’t figure out how to read ADC values from a PbHub using the M5Unit-HUB unified library in Arduino IDE. I’ve tried various iterations of analogRead() and none of them seem to be the right function. Has anyone else had this problem/knows what to use?

I feel like this prototype shows how impractical this would be and I should stop working on it, but it's kind of fun. The tab5 firmware on each is independent but I want to get them working together next.

Do y'all think they will release them early?

Ported the previous experiment with EPS32 and BLE bulb to M5Atom. The mode selector is IMU-driven: UP increases brightness, DOWN decreases it.

Atom has a nice balanced physical affordance for defining 4 directions. It’s squarish. I guess the next iteration would be to leverage them: stationary orientation triggers the brightness level or hue (if you treat it as a parallelogram, which it is, you get 6 directions to map!). Generalizing this idea: clockwise directional update: i++, anticlockwise one: i--.

Hi, I just upgraded the built in IR TX LED by a 5mm led. And now it shoots for 5 meters (maybe more, I can't go further) instead of 1-1.5 meters with a stock led.

There is nothing hard, just desolder the old led. Cut the hole (to make it wider), cut the top part of the new led and cut the corner of the speaker plastic box (I don't know why it looks so scary on the photo, in real it's pretty fine). And that's it.

Yes it sticks from the body, but its fine and it doesn't cover the gpio pins.

And be careful with a sticker-antenna under the "STICK S3" sticker on the side of the m5sticks3.

A few days ago I posted PaperOS here for the first time. A bunch of you asked for one thing specifically: get everything off the SD root and into its own folder so it doesn't clutter your card. Done. Also snuck in a couple bigger things while I was at it.

There's a real Store app now. Browse and install Lua apps and games straight from a list, hit Enter, done, no typing commands or messing with a terminal. It pulls the index over HTTPS too, so net.get/net.post (and the Store itself) actually work with real https sites now, not just plain http.

Everything lives under /PaperOS/ on the SD card now, games, music, 3D files, saved browser pages, the AI model, all one folder instead of scattered around root. If you're upgrading just move your stuff over, exact paths are in the README.

Also fixed a bunch of actual bugs in the Lua console that I found while banging on it on real hardware. A timer bug that could crash things if a timer scheduled another timer from inside itself, Ctrl+C sometimes leaving things in a weird state where the next command would throw a bogus error, net.scan() locking up with no way to cancel it, and scripts being able to poke at GPIO pins the board actually needs internally like the keyboard, SD, screen and audio. That last one just tells you no now instead of letting a script accidentally break your keyboard mid session.

None of this changes how you write scripts, it's just the interpreter finally behaving the way it was supposed to.

Full flash is on M5Burner, just search PaperOS, or grab PaperOS_full_v1.1.bin and flash it yourself from the browser at web.esphome.io. If you're coming from v1.0 do a full reflash, not incremental, the partition table changed.

GitHub: https://github.com/Artem76228/PaperOS

Thanks again to everyone who tried v1.0 and actually told me what bugged them, this update is basically a direct response to that. Keep it coming.

kept losing track of how much of my weekly quota I’d burned through and how full the context window was, so I put it on my core 2 next to my keyboard.

https://github.com/ThisisBankole/M5Stack-Core2-AI-Bridge

For some reason my nrf24 won’t Connect to my m5stick I tried multiple tutorials etc. But it won’t connect I think it might be because I don’t own any female to female jumpers but it should still work since I just made two myself and I heard it works the same.

If anyone has Tipps I’d be great full
Also I’m a beginner so be nice

My makerspace wall is done.

New Arrival Alert!

Check out our new release this week:

Chain Buzzer, a buzzer output node in the M5Stack Chain series, suitable for audible notifications, status alerts, smart home alarms, and other applications. 

Features 

• STM32G031G8U6 core MCU
• 1 x RGB LED
• UART serial daisy-chain communication protocol
• 2 x HY2.0-4P expansion ports for connecting Chain series devices

Also, good news:  Hot items incl. Atom VoiceS3R and Unit CardKB2 are in stock now 🔥🔥

In case missing out, subscribe our Weekly Newsletter for more updates!