Hi everyone,
I'd like to share a project I've been developing called ELMA-IoT ESP32 Toolkit.
The idea is to simplify ESP32/ESP8266 development by moving as much of the low-level work as possible behind a high-level visual workflow:
ESP board → Peripherals → GPIO → Wiring Diagram → Logics → Compile → Flash
The Android application can configure the board and peripherals, validate GPIO assignments and hardware compatibility, generate a visual wiring diagram, compile firmware directly on the phone, and flash the ESP through USB OTG or OTA.
One of the main features is Visual Logics.
Instead of writing the device behavior manually, the user can build it graphically:
Temperature → Compare > 30°C → Delay → Fan ON
or:
Battery Voltage → < 11.8V → MQTT Publish
Logics includes events, conditions, IF, AND/OR/NOT, Gate, Sequence, Branch, Timer, Delay, Repeat, Debounce, Cooldown and peripheral-specific actions.
Connections are typed, so incompatible inputs/outputs are rejected automatically.
The full Blueprint editor supports pan/zoom, editing connections and live visualization of the running algorithm after flashing.
Because a large Blueprint canvas isn't ideal on a phone, I also created a simplified vertical Logic Builder for portrait mode.
Both editors operate on the same underlying graph.
The project currently also includes:
• ESP32 / ESP32-S3 / ESP32-C3 / ESP8266 support
• Automatic GPIO compatibility/conflict checking
• Dynamic peripheral wiring diagrams
• On-device firmware compilation
• USB OTG flashing
• OTA updates
• Serial Monitor
• Wi-Fi and MQTT
• OLED/display actions
• Audio and offline TTS
• Live device values and Logics execution monitoring
The intention is not to create another low-level graphical programming language.
I want the user to describe WHAT the device should do at a high level, while ELMA-IoT handles libraries, hardware implementation, GPIO restrictions and generated firmware underneath.
Current Android version is v1.0.18 and the project is still in Closed Alpha.
I'm particularly interested in technical feedback from people already working with ESP32/ESP8266:
• Does this workflow make sense for real projects?
• What peripherals/workflows would you want to build with it?
• Is there anything important from your normal Arduino/ESP workflow that this approach would prevent you from doing?
I'm also looking for people willing to try the current Alpha on real ESP hardware. If you're interested, reply here or send me a private message and I'll explain how to join the Google Play Closed Test.
Feedback and criticism are very welcome.


