esp32-onboarding

Coordinate Docker health checks, PlatformIO flashing, and Wi-Fi configuration for ESP32-CAM onboarding.

7|1|Updated Jun 24, 2025
One-click install
npx skills add https://github.com/schutera/highfive --skill esp32-onboarding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: esp32-onboarding
Source: https://github.com/schutera/highfive/tree/main/.claude/skills/esp32-onboarding
Command: npx skills add https://github.com/schutera/highfive --skill esp32-onboarding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires platformio, pyserial.

What problem does it solve?

The skill prevents failed deployments of an ESP32-CAM image-capture module by guiding you through firmware flashing, server connectivity checks, and Wi-Fi registration step-by-step so the device reliably appears on the dashboard.

Core Features & Use Cases

  • End-to-end onboarding workflow: Verifies the Docker Compose service stack, flashes the correct firmware variant, captures boot logs, then walks you through access-point configuration.
  • Connectivity and diagnostics: Checks health endpoints, instructs on Windows firewall ports, and interprets common failure states such as wrong Wi-Fi band, mismatched LAN IP usage, or outdated firmware watchdog crashes.
  • Real-world use case: Get a new wild-bee hotel monitoring module registered and uploading images so it shows up in the interactive dashboard with battery, location, and online status.

Quick Start

Use the skill instructions to verify the container health endpoints on the correct LAN IP, then flash the ESP32-CAM using PlatformIO and configure the module via http://192.168.4.1 with your server initialization/upload URLs.

Frequently Asked Questions about esp32-onboarding

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

FAQPage Schema
How do I flash firmware and configure an ESP32-CAM module for image ingestion?

To flash and configure an ESP32-CAM, you use PlatformIO to upload firmware to the detected serial port, verify Docker Compose service health, capture boot logs, and submit Wi-Fi access-point configuration via the module's initialization endpoints.

Why does my ESP32-CAM fail to appear on the monitoring dashboard after onboarding?

Your ESP32-CAM may not appear on the dashboard due to wrong Wi-Fi band usage, mismatched LAN IP endpoints, failed Docker Compose health checks, or outdated firmware watchdog crashes. Validate boot logs and verify server connectivity to troubleshoot.

Do I need Docker Compose running before I can onboard an ESP32-CAM module?

Yes, Docker Compose health verification is required before onboarding an ESP32-CAM. The onboarding workflow checks container health endpoints on your LAN IP to ensure the image ingestion and monitoring stack is ready to receive device registrations.

What is the best way to troubleshoot ESP32-CAM connectivity issues during Wi-Fi configuration?

The best way to troubleshoot ESP32-CAM connectivity is to capture serial boot logs via pyserial, verify the module connects to the correct access point at http://192.168.4.1, and confirm your server initialization URLs are reachable on the LAN.

Can I use PlatformIO with pyserial to diagnose ESP32-CAM boot-log validation failures?

Yes, PlatformIO and pyserial are the required dependencies for diagnosing ESP32-CAM boot-log failures. They enable firmware flashing to the serial port and serial capture of access-point and boot status to validate the module's network configuration.

What steps are needed to register a fresh ESP32-CAM hardware module with an image monitoring stack?

Registering fresh ESP32-CAM hardware requires verifying Docker Compose health endpoints, flashing firmware via PlatformIO, configuring Wi-Fi access points, and submitting form data with correct initialization and upload URLs until the device appears in the dashboard.