By name: ESPHome yaml
description: trigger when user asks: create esphome yaml for device
SKILL: ESPHome yaml
Input
Files are relative to current working directory
test.rs: A std rust program run on the host machine during Wokwi simulation time.
This file reads from the tcp stream created by wokwi.toml rfc2217 tcp serial port.
You need to add to esphome section of the esphome yaml file, that prints
what this rust program expects in order to run test assertions on the serial output.
Ouput
Files are relative to current working directory
<device>.yaml: generated esphome yaml file
<device>.chip.json: wokwi custom chip definition
Step 1: esphome components docs
If there isn't already a components directory, run the following bash commands
mkdir -p components
cd components
npx degit https://github.com/esphome/esphome.io/src/content/docs/components
Step 2: look up docs for
Look up docs for
Step 3: Use ESPHome template
There is a file: references/template.yaml inside this skill.
You MUST copy the contents of references/template.yaml into the new YAML file verbatim before adding anything else.
Template preservation rules:
- Do not remove any line from the template.
- Do not reorder any line from the template.
- Do not edit existing values, comments, spacing, or blank lines from the template.
- Do not rename
esphome.name; keepname: dutexactly as provided. - Do not uncomment commented sections unless the user explicitly asks.
- Add the device-specific YAML only after the existing template content.
There is one and only one exception to this rule, and that is to add a on_boot to the core esphome configuration. This is where you essentially would run an automation script to test behaviour, if appropriate.
Create a file called <device>.yaml in the current working directory. The final file must begin with the exact contents of references/template.yaml,
followed by the device configuration for a typical use case.
Step 4: Validate esphome config
esphome config <device>.yaml