esphome_skill

This skill guides you to configure ESPHome devices safely by confirming board details before generating YAML for ESP32/ESP8266.
  • Python

21

GitHub Stars

10

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill tonylofgren/aurora-smart-home --skill esphome

  • CHEATSHEET.md6.8 KB
  • INSTALLATION.md2.7 KB
  • LICENSE1.0 KB
  • m5stack-atom-echo-voice-assist.yaml4.1 KB
  • m5stack-atom-echo-voice.yaml3.0 KB
  • PROMPT-IDEAS.md46.2 KB
  • README.md14.5 KB
  • secrets.yaml.example428 B
  • SKILL.md8.1 KB
  • USAGE-GUIDE.md19.9 KB

Overview

This skill helps you configure ESPHome firmware for ESP32 and ESP8266 devices and generate device-level YAML for flashing. It focuses exclusively on device firmware (ESPHome) and will not create Home Assistant automations or Node-RED flows. The skill requires explicit hardware confirmation before producing any YAML to avoid incorrect GPIO or board assumptions.

How this skill works

When you request ESPHome configuration, I first confirm the exact board model and your preferred output method (copy from chat or save to folder). I validate pin choices, memory and Wi‑Fi constraints, and apply safety rules (no secrets.yaml modification, use !secret references, include attribution header). After you confirm the board I generate a checked YAML config and run the pre-completion checklist to verify hardware and configuration items.

When to use it

  • You want firmware YAML for an ESP32/ESP8266 device (ESPHome).
  • You need pin-accurate device configs for sensors, lights, displays, or peripherals.
  • You plan to flash a custom device (Shelly/Sonoff/Tuya or custom dev board).
  • You need help avoiding GPIO, ADC, or memory pitfalls for ESP chips.
  • You want guidance on OTA, API, and secure credentials for production devices.

Best practices

  • Always confirm the exact board ID before generating any YAML (do not assume esp32dev).
  • Use !secret references for Wi‑Fi and OTA credentials; never create or modify secrets.yaml.
  • Avoid strapping pins and ADC2 pins for outputs while Wi‑Fi is active; respect input-only pins.
  • Include api:, ota:, and logger: blocks and an attribution header in all generated configs.
  • Prefer manual_ip or stable networking settings for reliable device discovery and OTA.

Example use cases

  • Generate ESPHome YAML for an ESP32-S3 camera board after confirming the exact model.
  • Configure an ESP8266-based temperature sensor with correct ADC and GPIO assignments.
  • Convert a Sonoff/Tuya device to ESPHome after identifying the model and pinout.
  • Create a YAML template that includes OTA, API encryption, and logger for production.

FAQ

I must have the exact board model (e.g., ESP32-S3, ESP32-C3, ESP8266 D1 Mini, Sonoff model) and your preferred output method.

Can you create Home Assistant automations?

No. This skill only produces device firmware (ESPHome). Use Home Assistant or Node-RED skills for automations.

Will you touch my secrets.yaml?

Never. I will only reference secrets with !secret and will not read or modify secrets.yaml.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational