@Powersoft Yes, you can find ESC sequence handling at lines 1515-1927 of Terminal.cpp.

@aliense44 hey man thanks for your work, i am new at this, i got the pinhequa 2 in 1 with 433mhz, google ai told me this code is plug and play but it does not recognize the module, and i really want to try ypur addons. thanks

platform = https://github.com/pioarduino/platform-espressif32.git#54.03.20 Tag #54.03.20 doesn't work anymore. There were some conflict with esptool. "TypeError: ParamType.get_metavar() missing 1 required positional argument: 'ctx'" It failed at build.

snap shoot from the game 

The same thing. AI mode didn't work, no leds on, no reply on startup phrase

I turned an M5Stack Cardputer-Adv into a physical control surface for an AI coding agent (Claude Code) over BLE + MCP. Built on top of cardputer-claude-os. [image: device.jpg] Physical approval gate — a hook routes the agent's shell commands and file edits to the Cardputer. Read-only commands pass through; ordinary ones take a single Enter on the device; destructive ones (rm -rf, git push, sudo, editing secrets) need a sustained hold-Y gesture that prompt-injection can't fake. If the device is away, it falls back to the terminal — the Cardputer is an optional gate, never a dependency. Ordinary action — one Enter: [image: approve.jpg] Destructive action — hold Y for ~3s: [image: danger.jpg] Other bits Always-on usage dashboard: today's spend, 5h/7d subscription utilization, battery %, and a resident pixel-crab mascot. notify / ask / confirm tools so the agent can buzz a banner, ask a multiple-choice question, or demand confirmation. Notes for fellow Adv owners The Adv's ES8311 codec only makes sound if your main loop calls M5.update() every iteration — took me a while to track down. The app is big, so it ships as compiled .mpy (source-form import OOMs the launcher), deployed into the cardputer-claude-os launcher bundle. Code (MIT) + setup: https://github.com/loml13/cardputer-claude-mcp Feedback welcome

Hello @Shipbrook M5Unified uses Wire1 for internal I2C and Wire for external I2C. The example for SHT40 incorrectly uses Wire which causes issues as soon as other internal I2C communication is required, e.g. reading battery status. The quick way to fix this is replacing Wire with Wire1 in below line: //if(!sht4.begin(&Wire, SHT40_I2C_ADDR_44, SHT_SDA_PIN, SHT_SCL_PIN, 400000U)) if(!sht4.begin(&Wire1, SHT40_I2C_ADDR_44, SHT_SDA_PIN, SHT_SCL_PIN, 400000U)) The better way is to get the actual port used by M5Unified for internal I2C and the use that information: i2c_port_t PortIn = M5.In_I2C.getPort(); TwoWire * WireIn = (PortIn == 1) ? &Wire1 : &Wire; if(!sht4.begin(WireIn, SHT40_I2C_ADDR_44, SHT_SDA_PIN, SHT_SCL_PIN, 400000U)) Thanks Felix

After a lot of testing and searching it became apparent that the M5Atom controller did not work properly (never had this type of problem before). This, outdated software and some wrong suggestions by both ChatGPT and the AI bot from M5Stack (with the knowledge base available) made it a bit of struggle. However, after all updates and testing different hardware it finally works again. So thanks to anyone that spent time on this!