Pocket-sized wireless macro controller on a round AMOLED board

Nov 01, 2026 Last reply: 1 day ago 2 Replies
Jump to replies (2)

This one started years ago as a way to get a macro keyboard without buying dedicated hardware, under the earlier name Nova Macros. The goal was a standalone wireless controller that needs no smartphone and no secondary monitor, letting macros be triggered from somewhere other than the computer itself.



Over time it grew considerably. The first versions were written almost entirely in AutoHotkey, then the server was ported to golang to accept TCP connections and run those macros, with a brief experiment at rebuilding the interface in the Godot engine. An Android client appeared, followed by a desktop interface for secondary touchscreens. The current iteration runs on a Waveshare ESP32-S3 Touch AMOLED 1.75C board: a dual-core Xtensa LX7 at up to 240 MHz, 8 MB of PSRAM, 32 MB of flash, a 1.75-inch circular AMOLED at 466 by 466, capacitive touch via a CST9217, a QMI8658 six-axis accelerometer and gyroscope, dual microphones with an audio codec, 2.4 GHz Wi-Fi, Bluetooth 5 LE, USB-C power with rechargeable 3.7V lithium battery support, all inside a CNC-machined aluminum alloy case.



The architecture is what stands out for me. The handheld device is only a remote interface: the client never needs to know how a macro works, it simply tells the server which action to execute. UDP discovery lets clients on the local network find the server without manual address setup, and the maker has said clients send those requests rather than the server, an approach inspired by how Minecraft LAN servers are found. TCP handles button actions. The interface shown runs under a LINKDECK header with a default profile, red circular sub-menu icons, a page indicator reading 1 of 2 and a battery at 97 percent.



The maker admits the board is probably more hardware than a simple macro controller needs, and calls that part of the appeal. Whether the extra headroom earns its keep over a long battery session seems the open question worth watching.


The choice to keep all macro logic on the server side looks like the smartest part of this design. A client that only names an action stays tiny, so new macros need no firmware work at all. The trade-off is that the computer has to be running the server, but for a desk-bound controller that seems a fair price.

One concrete idea for a future version: the board already carries a QMI8658 six-axis accelerometer and gyroscope, and tying gestures to macros would suit a pocket device well. A shake or a flip to switch profiles could pair nicely with the pocket-watch style aluminum case, and it would use hardware that is already soldered on rather than adding anything new.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required