What is esp32-workbench-ota?

Ideal for IoT Agents working with ESP32 devices, enabling seamless over-the-air firmware updates. OTA firmware upload, listing, deletion, and over-the-air update for the Universal ESP32 Workbench. Triggers on OTA, firmware, update, upload, binary, over-the-air.

How do I install esp32-workbench-ota?

Run the command: npx killer-skills add SensorsIot/Universal-ESP32-Workbench/esp32-workbench-ota. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for esp32-workbench-ota?

Key use cases include: Updating ESP32 firmware over WiFi networks, Performing iterative development with OTA updates, Deploying firmware to multiple ESP32 devices on the same LAN.

Which IDEs are compatible with esp32-workbench-ota?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for esp32-workbench-ota?

Requires device to already run firmware with an OTA HTTP endpoint. Device must be connected to the WiFi network or same LAN as the workbench. Not suitable for blank or bricked devices, which require serial flashing.

esp32-workbench-ota

Install esp32-workbench-ota, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md

Readonly

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Supporting Evidence

ESP32 OTA & Firmware Repository

Name: esp32-workbench-ota
Availability: InStock
Author: SensorsIot

Base URL: http://192.168.0.87:8080

When to Use OTA (vs Serial Flashing)

Use OTA when:

Device already runs firmware with an OTA HTTP endpoint
Device is on the WiFi network (connected to workbench's AP or same LAN)
You want to update firmware without blocking the serial port
You're doing iterative development (build → upload → trigger → monitor cycle)

Do NOT use OTA when:

Device is blank/bricked — use serial flashing (see esp32-workbench-serial-flashing)
Device firmware has no OTA support — use serial flashing
Device has no WiFi connectivity — use serial flashing
You need to flash a bootloader or partition table — only esptool can do this

Endpoints

Method	Path	Purpose
POST	`/api/firmware/upload`	Upload firmware binary (multipart/form-data)
GET	`/api/firmware/list`	List all uploaded firmware files
DELETE	`/api/firmware/delete`	Delete a firmware file
GET	`/firmware/<project>/<file>`	Download URL (ESP32 fetches from here during OTA)

End-to-End OTA Workflow

Step 1: Upload firmware to workbench

bash
1curl -X POST http://192.168.0.87:8080/api/firmware/upload \
2  -F "project=my-project" \
3  -F "file=@build/firmware.bin"

Response: {"ok": true, "project": "my-project", "filename": "firmware.bin", "size": 456789}

Step 2: Verify upload

bash
1curl -s http://192.168.0.87:8080/api/firmware/list | jq .

Step 3: Ensure device is on the network

The device must be able to reach http://192.168.0.87:8080. Use enter-portal to provision if needed (see esp32-workbench-wifi).

Step 4: Clear UDP log buffer (for clean monitoring)

bash
1curl -X DELETE http://192.168.0.87:8080/api/udplog

Step 5: Trigger OTA on the ESP32 via HTTP relay

bash
1OTA_BODY=$(echo -n '{"url":"http://192.168.0.87:8080/firmware/my-project/firmware.bin"}' | base64)
2
3curl -X POST http://192.168.0.87:8080/api/wifi/http \
4  -H 'Content-Type: application/json' \
5  -d "{\"method\": \"POST\", \"url\": \"http://192.168.4.2/ota\", \"headers\": {\"Content-Type\": \"application/json\"}, \"body\": \"$OTA_BODY\", \"timeout\": 30}"

Step 6: Monitor OTA progress

bash
1# Via UDP logs (preferred — non-blocking)
2curl "http://192.168.0.87:8080/api/udplog?limit=50"
3
4# Or via serial monitor (see esp32-workbench-logging)
5curl -X POST http://192.168.0.87:8080/api/serial/monitor \
6  -H 'Content-Type: application/json' \
7  -d '{"slot": "slot-1", "pattern": "OTA.*complete", "timeout": 60}'

Managing Firmware Files

bash
1# List all uploaded firmware
2curl http://192.168.0.87:8080/api/firmware/list
3
4# Delete a firmware file
5curl -X DELETE http://192.168.0.87:8080/api/firmware/delete \
6  -H 'Content-Type: application/json' \
7  -d '{"project": "my-project", "filename": "firmware.bin"}'
8
9# The download URL for ESP32 to fetch:
10# http://192.168.0.87:8080/firmware/<project>/<filename>

Troubleshooting

Problem	Fix
Upload returns "expected multipart/form-data"	Use `-F` flags (not `-d`) for multipart upload
File not in list after upload	Check project/filename; `..` and `/` are rejected
ESP32 can't download firmware	Device must reach workbench at 192.168.0.87:8080; check WiFi
OTA trigger times out	Check device's OTA endpoint URL; increase HTTP relay timeout
No progress in UDP logs	Device may not send UDP logs — check serial monitor instead (see esp32-workbench-logging)
OTA trigger returns error	Verify device firmware has OTA endpoint; check relay response body

esp32-workbench-ota — community esp32-workbench-ota, Universal-ESP32-Workbench, community, ide skills

About this Skill

Killer-Skills Review

Core Value

Ideal Agent Persona

↓ Capabilities Granted for esp32-workbench-ota

! Prerequisites & Limits

Source Boundary

Decide The Next Action Before You Keep Reading Repository Material

Start With Installation And Validation

Cross-Check Against Trusted Picks

Move To Workflow Collections For Team Rollout

Browser Sandbox Environment

⚡️ Ready to unleash?

FAQ & Installation Steps

? Frequently Asked Questions