microclawup — AI-powered ESP32 GPIO controller in MicroPython

[kritishmohapatra]

Hi everyone! I wanted to share a project I built called microclawup🦞.

The idea is simple — you send a natural language message on Telegram, Groq AI converts it to a hardware command, and your ESP32 executes it and replies back.

"turn on the light" -> LED ON | Pin 2
"blink 5 times" -> Blink x5 | Pin 2
"pin 4 high" -> GPIO HIGH | Pin 4

It also understands Hindi and other languages since Groq AI handles the translation.

Features:

• Natural language GPIO control via Telegram
• Groq AI integration (completely free)
• Persistent memory across reboots using flash storage
• WiFi auto-reconnect
• /status and /help commands
• Easy setup with python setup.py on PC

Inspired by zclaw (a C-based ESP32 AI agent) — microclawup is a MicroPython alternative focused on being beginner friendly.

Tested on ESP32

GitHub: https://github.com/kritishmohapatra/microclawup

Would love feedback from the MicroPython community. Happy to answer any questions!

[kritishmohapatra]

VID20260225012508.mp4

[2dof]

I don't kno if my feedback will be productivce - i haven't tested it but i used to R&D some solutions aggregating simple PLC functionality like ON/OFF, time/date scheduling with speech processing to txt (on PC) (I could not use any AI agent)- and then execute command on ESP.

If You want develop your project in future conder:

• add ing some scheduling to Your solution ( like @peterhinch 's shedule lib has nice The schedule coroutine already incorpotating txt commands.

• if You consider Your ESP as some type of controller - consider adding some "end" command authentication playing a role of password of device addres every time when You send command.

in My case (projekt) it would look like this:

Me speaking : " hey Kettle Man , turn kettle on at 17 PM " after processing could directly create task : "asyncio.create_task(schedule( kettle , 'one shot', hrs=17, mins=range(0, 60, 2), times=1))
where 'Kettle Man' was just name device, 'kettle' was keyword for function turning on/off kettle.

As authentication (password) I used identification based on voice (Person) recognition so nobody exept me ( as defined user) could use it.

[kritishmohapatra]

Thanks for the feedback! Appreciate it.

Scheduling is a great idea – I was actually thinking of implementing that. Will look into peterhinch's schedule library, it looks perfect for the job.

The authentication point is also a very valid one. Currently, microclawup only responds to a certain CHAT_ID, so it's only for one user, but a proper command authentication system would make it much more secure, especially for shared or multi-device usage.

Your voice recognition authentication system sounds like a whole lot of fun – that's a whole different level!

Will definitely take both of those into consideration for the next version. Thanks again!