deploy

Automate end-to-end ESP32 firmware deployment from build to OTA.

25|7|Updated Mar 4, 2019

Search Tags:#deployment #verification #firmware #ota #release-please #version-management #platformio

Ready to run

npx skills add https://github.com/smart-swimmingpool/pool-controller --skill deploy-smart-swimmingpool

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/smart-swimmingpool/pool-controller/tree/main/.opencode/skills/deploy
Command: npx skills add https://github.com/smart-swimmingpool/pool-controller --skill deploy-smart-swimmingpool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides an end-to-end deployment workflow for pool-controller ESP32 firmware, covering build, flash, web filesystem upload, OTA updates, and release-management integration to streamline production deployments.

Core Features & Use Cases

Automates the full deployment pipeline from code to device, including pre-flight checks, version management, and post-deploy verification.
Supports PlatformIO-based ESP32 projects with optional web UI/assets deployment and release automation via release-please.
Use Case: When releasing a new firmware, trigger a repeatable deployment sequence that builds, flashes, uploads the web assets, performs an OTA update, and updates version manifests.

Quick Start

Install and configure the deployment workflow and run the mandated release process to deploy firmware to a device.

Frequently Asked Questions about deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate ESP32 firmware deployment with PlatformIO and OTA updates?▼

Automated ESP32 firmware deployment uses a pipeline that runs pre-flight checks, builds the PlatformIO project, flashes the device, uploads web filesystem assets, and executes OTA updates. This workflow handles the full deployment sequence from code to device automatically.

How does release-please handle firmware version management for ESP32 projects?▼

Firmware version management with release-please works by synchronizing the FW_VERSION variable during the deployment pipeline. It automates version bumping and release creation, ensuring the deployed ESP32 firmware matches the release manifest generated by release-please.

Can I upload web UI assets alongside firmware to an ESP32 device?▼

Yes, uploading web UI assets alongside firmware is supported in this deployment workflow. The process handles optional web filesystem uploads for PlatformIO-based ESP32 projects, deploying web assets in the same sequence as the firmware build and OTA update.

What pre-flight checks are needed before deploying ESP32 firmware over OTA?▼

Pre-flight checks for ESP32 OTA deployment include verifying the PlatformIO environment, confirming firmware version synchronization via FW_VERSION, and validating release-please configuration. These checks prevent deployment failures by validating the build environment and version state before flashing begins.

Does this deployment workflow support post-deploy verification for ESP32 firmware?▼

Yes, post-deploy verification is included in the ESP32 firmware deployment workflow. After the OTA update and web asset upload complete, the pipeline verifies the deployment was successful, ensuring the device is running the correct firmware version and assets are properly loaded.

What is the best way to manage version manifests for ESP32 OTA releases?▼

Managing version manifests for ESP32 OTA releases is best handled using release-please to automate version synchronization. The deployment workflow updates manifests by syncing the FW_VERSION variable, ensuring consistency between the codebase, release tags, and the deployed firmware.