hardware-test

Orchestrate end-to-end ESP32 hardware testing with phased verification and reporting.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Auto-one-Family/Automation-One --skill hardware-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hardware-test
Source: https://github.com/Auto-one-Family/Automation-One/tree/main/.claude/skills/hardware-test
Command: npx skills add https://github.com/Auto-one-Family/Automation-One --skill hardware-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a repeatable, multi-phase orchestration for validating ESP32-based sensor and actuator hardware setups, removing guesswork from wiring, firmware, connectivity, and stability verification.

Core Features & Use Cases

  • Profile-driven orchestration: Load and validate hardware profiles (board, GPIOs, sensor types) and detect conflicts before touching hardware.
  • Stack and firmware checks: Verify Docker services, REST health, MQTT broker uptime, and firmware build/flash status as preconditions.
  • Phased automation with manual handoffs: Automates device registration, config push, live verification, DB persistence checks, and stability polling while pausing for physical wiring steps by a technician.
  • Resilience and reporting: Handles common errors (device exists, GPIO conflicts, config timeouts), writes per-phase reports, and produces a final meta-analysis scorecard for QA records.

Quick Start

Run the hardware-test skill with a profile name, for example: hardware-test --profile sht31_basic.

Frequently Asked Questions about hardware-test

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

FAQPage Schema
How do I automate ESP32 hardware testing and sensor validation?

To automate ESP32 hardware testing, you orchestrate profile validation, device provisioning, and live verification. This Skill automates multi-phase hardware testing for ESP32 sensors and actuators, integrating Docker, MQTT, and REST checks to ensure firmware, connectivity, and database persistence stability.

What is phased automation with manual handoffs for IoT device provisioning?

Phased automation with manual handoffs is an IoT testing approach that automates device registration, config push, and stability polling while pausing for physical wiring steps by a technician. This ensures safe, repeatable ESP32 sensor validation without skipping necessary physical hardware interventions.

Does this ESP32 testing workflow support MQTT broker uptime and Docker service health checks?

Yes, ESP32 testing workflows can verify Docker services, REST health, and MQTT broker uptime. This Skill performs stack and firmware checks as preconditions before running hardware validation, ensuring the entire IoT infrastructure is healthy before testing sensors and actuators.

How do I validate ESP32 GPIO configurations and detect sensor profile conflicts?

Validating ESP32 GPIO configurations requires loading and validating hardware profiles to detect pin conflicts before touching hardware. This Skill uses profile-driven orchestration to check board settings, GPIOs, and sensor types, preventing wiring errors and configuration conflicts early in the process.

Can I generate structured QA reports for ESP32 sensor stability checks?

Yes, you can generate structured QA reports for ESP32 sensor stability checks. This Skill writes per-phase reports and produces a final meta-analysis scorecard, handling common errors like device exists and config timeouts to deliver comprehensive QA records for IoT development.

Why does my ESP32 hardware test fail during database persistence verification?

ESP32 hardware tests may fail during database persistence verification due to connectivity issues, config timeouts, or GPIO conflicts. This Skill handles these common errors during multi-iteration stability checks and logs them in per-phase reports for troubleshooting IoT development setups.